Download full document:

perf_ssl_be_rsa_dhkey_report

Configuration for SSL Back-end RSA vs. DH Key exchanges report resource.

(click to see Operations)

Properties

(click to see Operations)

NameData TypePermissionsDescription
sslbersa512keyexchangesrate<Double>Read-writesslbersa512keyexchangesrate Value.
sslbedh2048keyexchangesrate<Double>Read-writesslbedh2048keyexchangesrate Value .
sslbersa1024keyexchangesrate<Double>Read-writesslbersa1024keyexchangesrate Value .
device_ip_address<String>Read-writeDevice IP Address.
Minimum length = 1
Maximum length = 64
sslbersa2048keyexchangesrate<Double>Read-writesslbersa2048keyexchangesrate Value .
timestamp<Double>Read-writetimestamp in milliseconds.
sslbedh1024keyexchangesrate<Double>Read-writesslbedh1024keyexchangesrate Value .
sslbedh512keyexchangesrate<Double>Read-writesslbedh512keyexchangesrate Value .
id<String>Read-writeId is system generated key for all the entries in this perf table configuration.
Maximum length = 256
report_start_time<Double>Read-writereport_start_time in seconds.
report_end_time<Double>Read-writereport_end_time in seconds.

Operations

(click to see Properties)

GET

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: https://<MGMT-IP>/nitro/v1/config/perf_ssl_be_rsa_dhkey_report

HTTP Method: null

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value>, "perf_ssl_be_rsa_dhkey_report":[{
"sslbersa512keyexchangesrate":<Double_value>,
"sslbedh2048keyexchangesrate":<Double_value>,
"sslbersa1024keyexchangesrate":<Double_value>,
"device_ip_address":<String_value>,
"sslbersa2048keyexchangesrate":<Double_value>,
"timestamp":<Double_value>,
"sslbedh1024keyexchangesrate":<Double_value>,
"sslbedh512keyexchangesrate":<Double_value>,
"id":<String_value>,
"report_start_time":<Double_value>,
"report_end_time":<Double_value>}]}