Developer Documentation
ADC NITRO APIs
Current Release 13.1 13

appfwsignatures

August 17, 2023
Contributed by: 
C

Configuration for application firewall signatures XML configuration resource.

Properties

(click to see Operations )

Name Data Type Permissions Description
name Read-write Name of the signature object.

Minimum length = 1

Maximum length = 31
src Read-write URL (protocol, host, path, and file name) for the location at which to store the imported signatures object.

NOTE: The import fails if the object to be imported is on an HTTPS server that requires client certificate authentication for access.

Minimum length = 1

Maximum length = 2047
xslt Read-write XSLT file source.

Maximum length = 2047
comment Read-write Any comments to preserve information about the signatures object.

Maximum length = 128
overwrite Read-write Overwrite any existing signatures object of the same name.
merge Read-write Merges the existing Signature with new signature rules.
preservedefactions Read-write preserves def actions of signature rules.
sha1 Read-write File path for sha1 file to validate signature file.

Minimum length = 1

Maximum length = 2047
vendortype Read-write Third party vendor type for which WAF signatures has to be generated.

Possible values = Snort
mergedefault Read-write Merges signature file with default signature file.
response Read-only .

Operations

(click to see Properties )

  • DELETE
  • GET (ALL)
  • GET
  • IMPORT
  • CHANGE

Some options that you can use for each operations:

  • Getting warnings in response: NITRO allows you to get warnings in an operation by specifying the 'warning' query parameter as 'yes'. For example, to get warnings while connecting to the NetScaler appliance, the URL is as follows:

    http:// <netscaler-ip-address> /nitro/v1/config/login?warning=yes

    If any, the warnings are displayed in the response payload with the HTTP code '209 X-NITRO-WARNING'.

  • Authenticated access for individual NITRO operations: NITRO allows you to logon to the NetScaler appliance to perform individual operations. You can use this option instead of creating a NITRO session (using the login object) and then using that session to perform all operations,

    To do this, you must specify the username and password in the request header of the NITRO request as follows:

    X-NITRO-USER: <username>

    X-NITRO-PASS: <password>

    Note: In such cases, make sure that the request header DOES not include the following:

    Cookie:NITRO_AUTH_TOKEN= <tokenvalue>

*Note: *

Mandatory parameters are marked in red and placeholder content is marked in green

delete

URL: http:// <netscaler-ip-address> /nitro/v1/config/appfwsignatures/ name_value<String>

HTTP Method: DELETE

Request Headers:

Cookie:NITRO_AUTH_TOKEN= <tokenvalue>

Response:

HTTP Status Code on Success: 200 OK

HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error

Import

URL: http:// <netscaler-ip-address> /nitro/v1/config/appfwsignatures? action=Import

HTTP Method: POST

Request Headers:

Cookie:NITRO_AUTH_TOKEN= <tokenvalue>

Content-Type:application/json

Request Payload: 


{"appfwsignatures":{
<b>      "src":<String_value>,
</b><b>      "name":<String_value>,
</b>      "xslt":<String_value>,
      "comment":<String_value>,
      "overwrite":<Boolean_value>,
      "merge":<Boolean_value>,
      "preservedefactions":<Boolean_value>,
      "sha1":<String_value>,
      "vendortype":<String_value>
}}

<!--NeedCopy-->

Response:

HTTP Status Code on Success: 200 OK

HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error

change

URL: http:// <netscaler-ip-address> /nitro/v1/config/appfwsignatures? action=update

HTTP Method: POST

Request Headers:

Cookie:NITRO_AUTH_TOKEN= <tokenvalue>

Content-Type:application/json

Request Payload: 


{"appfwsignatures":{
<b>      "name":<String_value>,
</b>      "mergedefault":<Boolean_value>
}}

<!--NeedCopy-->

Response:

HTTP Status Code on Success: 200 OK

HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error

get (all)

URL: http:// <netscaler-ip-address> /nitro/v1/config/appfwsignatures

HTTP Method: GET

Request Headers:

Cookie:NITRO_AUTH_TOKEN= <tokenvalue>

Accept:application/json

Response:

HTTP Status Code on Success: 200 OK

HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error

Response Header:

Content-Type:application/json

Response Payload: 


{ "appfwsignatures": [ {
      "name":<String_value>,
      "response":<String_value>,
      "src":<String_value>
}]}

<!--NeedCopy-->

get

URL: http:// <netscaler-ip-address> /nitro/v1/config/appfwsignatures/ name_value<String>

Query-parameters:

attrs

http:// <netscaler-ip-address> /nitro/v1/config/appfwsignatures/ name_value<String> ? attrs=property-name1,property-name2

Use this query parameter to specify the resource details that you want to retrieve.

view

http:// <netscaler-ip-address> /nitro/v1/config/appfwsignatures/ name_value<String> ? view=summary

Use this query-parameter to get the summary output of appfwsignatures resources configured on NetScaler.

Note: By default, the retrieved results are displayed in detail view (?view=detail).

HTTP Method: GET

Request Headers:

Cookie:NITRO_AUTH_TOKEN= <tokenvalue>

Accept:application/json

Response:

HTTP Status Code on Success: 200 OK

HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error

Response Header:

Content-Type:application/json

Response Payload: 


{  "appfwsignatures": [ {
      "name":<String_value>,
      "response":<String_value>,
      "src":<String_value>
}]}

<!--NeedCopy-->
appfwsignatures
August 17, 2023
Contributed by: 
C
August 17, 2023
Contributed by: 
C

In this article

Site feedback | Your privacy choices footer linkYour Privacy Choices | Privacy and legal terms | Cookie preferences | Consent settings | docs.cloud.com
© 1999- Cloud Software Group, Inc. All rights reserved.