sslvserver_binding
Binding object which returns the resources bound to sslvserver.
Properties
(click to see Operations)
Name | Data Type | Permissions | Description |
---|---|---|---|
vservername | <String> | Read-write | Name of the SSL virtual server for which to show detailed information.<br>Minimum length = 1 |
sslvserver_sslpolicy_binding | <sslvserver_sslpolicy_binding[]> | Read-only | sslpolicy that can be bound to sslvserver. |
sslvserver_sslcipher_binding | <sslvserver_sslcipher_binding[]> | Read-only | sslcipher that can be bound to sslvserver. |
sslvserver_ecccurve_binding | <sslvserver_ecccurve_binding[]> | Read-only | ecccurve that can be bound to sslvserver. |
sslvserver_sslcertkey_binding | <sslvserver_sslcertkey_binding[]> | Read-only | sslcertkey that can be bound to sslvserver. |
sslvserver_sslciphersuite_binding | <sslvserver_sslciphersuite_binding[]> | Read-only | sslciphersuite that can be bound to sslvserver. |
Operations
(click to see Properties)
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/sslvserver_binding/vservername_value<String>
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 errorResponse Headers:
Content-Type:application/json
Response Payload:
{ "sslvserver_binding": [ { "vservername":<String_value>, "sslvserver_sslpolicy_binding":<sslvserver_sslpolicy_binding[]_value>, "sslvserver_sslcertkey_binding":<sslvserver_sslcertkey_binding[]_value>, "sslvserver_sslciphersuite_binding":<sslvserver_sslciphersuite_binding[]_value>, "sslvserver_ecccurve_binding":<sslvserver_ecccurve_binding[]_value>, "sslvserver_sslcipher_binding":<sslvserver_sslcipher_binding[]_value> }]}
get (all)
URL: http://<netscaler-ip-address>/nitro/v1/config/sslvserver_binding
Query-parameters:
bulkbindings
http://<netscaler-ip-address>/nitro/v1/config/sslvserver_binding?bulkbindings=yes
NITRO allows you to fetch bindings in bulk.
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 errorResponse Headers:
Content-Type:application/json
Response Payload:
{ "sslvserver_binding": [ { "vservername":<String_value>, "sslvserver_sslpolicy_binding":<sslvserver_sslpolicy_binding[]_value>, "sslvserver_sslcertkey_binding":<sslvserver_sslcertkey_binding[]_value>, "sslvserver_sslciphersuite_binding":<sslvserver_sslciphersuite_binding[]_value>, "sslvserver_ecccurve_binding":<sslvserver_ecccurve_binding[]_value>, "sslvserver_sslcipher_binding":<sslvserver_sslcipher_binding[]_value> }]}