Skip to content

si_safety_signature

Configuration for AF Safety Data Report table resource.

(click to see Operations)

Properties

(click to see Operations)

NameData TypePermissionsDescription
sig_learn<Double>Read-writesig_learn..
sig_rule_id<Double>Read-writeSignature Rule Id.
__count<Double>Read-writecount..
sig_none<Double>Read-writesig_none..
configuration<String>Read-writeProfile Security configuration.
Maximum length = 255
id<String>Read-writeId is safety profile.
Maximum length = 255
sig_block_count<Double>Read-writesig_block_count..
sig_rule_category<String>Read-writeProfile sig_rule_category.
Maximum length = 2550
sig_sig_name<String>Read-writeProfile signature name.
Maximum length = 2550
sig_block<Double>Read-writesig_block..
sig_stat_count<Double>Read-writesig_stat_count..
sig_rule_logstring<String>Read-writeProfile sig_rule_logstring.
Maximum length = 2550
name<String>Read-writeProfile Name.
Maximum length = 255
sig_log<Double>Read-writesig_log..
profile_sig_disable_count<Double>Read-writeprofile_sig_disable_count..
profile_not_block_count<Double>Read-writeprofile_not_block_count..
sig_log_count<Double>Read-writesig_log_count..
sig_stat<Double>Read-writesig_stat..
si_app_unit_name<String>Read-writeAppName.
Maximum length = 255
sig_safety_index<Double>Read-writesig_safety_index..
profile_safety_index<Double>Read-writeprofile_safety_index..

Operations

(click to see Properties)

GET (ALL)

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>.

get (all)

URL: https://<MGMT-IP>/nitro/v1/config/si_safety_signature

HTTP Method: null

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value>, "si_safety_signature":[{
"sig_learn":<Double_value>,
"sig_rule_id":<Double_value>,
"__count":<Double_value>,
"sig_none":<Double_value>,
"configuration":<String_value>,
"id":<String_value>,
"sig_block_count":<Double_value>,
"sig_rule_category":<String_value>,
"sig_sig_name":<String_value>,
"sig_block":<Double_value>,
"sig_stat_count":<Double_value>,
"sig_rule_logstring":<String_value>,
"name":<String_value>,
"sig_log":<Double_value>,
"profile_sig_disable_count":<Double_value>,
"profile_not_block_count":<Double_value>,
"si_device_ip_address":<String_value>,
"sig_log_count":<Double_value>,
"sig_stat":<Double_value>,
"si_app_unit_name":<String_value>,
"sig_safety_index":<Double_value>,
"profile_safety_index":<Double_value>}]}