Download full document:

sslcipher_sslprofile_binding

Binding object showing the sslprofile that can be bound to sslcipher.

Properties

(click to see Operations)

Name Data Type PermissionsDescription
cipherpriority<Double>Read-writePriority of the cipher to be added.<br>Minimum value = 1<br>Maximum value = 1000
ciphgrpals<String>Read-writeA cipher-suite can consist of an individual cipher name, the system predefined cipher-alias name, or user defined cipher-group name.<br>Minimum length = 1
description<String>Read-writeCipher suite description.
sslprofile<String>Read-writeName of the profile to which cipher is attached.
ciphergroupname<String>Read-writeName of the user-defined cipher group.<br>Minimum length = 1
cipheroperation<String>Read-writeThe operation that is performed when adding the cipher-suite. Possible cipher operations are: ADD - Appends the given cipher-suite to the existing one configured for the virtual server. REM - Removes the given cipher-suite from the existing one configured for the virtual server. ORD - Overrides the current configured cipher-suite for the virtual server with the given cipher-suite.<br>Default value: 0<br>Possible values = ADD, REM, ORD
__count<Double>Read-writecount parameter

Operations

(click to see Properties)

GET | COUNT

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

URL: http://<netscaler-ip-address>/nitro/v1/config/sslcipher_sslprofile_binding/ciphergroupname_value<String>

Query-parameters:

filter

http://<netscaler-ip-address>/nitro/v1/config/sslcipher_sslprofile_binding/ciphergroupname_value<String>?filter=property-name1:property-value1,property-name2:property-value2

Use this query-parameter to get the filtered set of sslcipher_sslprofile_binding resources configured on NetScaler.Filtering can be done on any of the properties of the resource.

pagesize=#no;pageno=#no

http://<netscaler-ip-address>/nitro/v1/config/sslcipher_sslprofile_binding/ciphergroupname_value<String>?pagesize=#no;pageno=#no

Use this query-parameter to get the sslcipher_sslprofile_binding resources in chunks.

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 (for general HTTP errors) or 5xx (for NetScaler-specific errors). The response payload provides details of the error Response Headers:

Content-Type:application/json

Response Payload:

{ "sslcipher_sslprofile_binding": [ {
      "cipherpriority":<Double_value>,
      "ciphgrpals":<String_value>,
      "description":<String_value>,
      "sslprofile":<String_value>,
      "ciphergroupname":<String_value>,
      "cipheroperation":<String_value>
}]}

count

URL: http://<netscaler-ip-address>/nitro/v1/config/sslcipher_sslprofile_binding/ciphergroupname_value<String>?count=yes

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 (for general HTTP errors) or 5xx (for NetScaler-specific errors). The response payload provides details of the error Response Headers:

Content-Type:application/json

Response Payload:

{"sslcipher_sslprofile_binding": [ { "__count": "#no"} ] }