NetScaler SDX 14.1 NITRO API Reference

tacacs_server

Configuration for TACACS Server configuration resource.

Properties

(click to see Operations )

Name Data Type Permissions Description
tacacs_key Read-write Key shared between the TACACS+ server and clients.

Minimum length = 1

Maximum length = 64
auth_timeout Read-write The maximum number of seconds the system will wait for a response from the TACACS server.

Minimum value = 1

Maximum value =
name Read-write Name of TACACS server.

Minimum length = 1

Maximum length = 128
group_attr_name Read-write The Attribute name for group extraction from the ACS server. If not passed, then groups will not be extracted. No other harm.

Maximum length = 64
port Read-write port number of TACACS server.

Minimum value = 1

Maximum value =
id Read-write Id is system generated key for all the TACACS servers.
ip_address Read-write IP Address of TACACS server.

Minimum length = 1

Maximum length = 64
accounting Read-write Enable accounting in the tacacs server.
address_type Read-only Configuration Type. Values: 0: IPv4, 1: IPv6.

Operations

(click to see Properties )

  • ADD
  • DELETE
  • GET (ALL)
  • GET
  • UPDATE

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

The following parameters can be used in the nitro request : onerror <String_value>

Use this parameter to set the onerror status for nitro request. Applicable only for bulk requests.

Default value: EXIT

Possible values = EXIT, CONTINUE

add

URL: https://<MGMT-IP>/nitro/v2/config/tacacs_server?onerror=<String_value> HTTPS Method: POST

Request Headers: Content-Type: application/json

X-NITRO-USER:username_value<String>

X-NITRO-PASS:password_value<String>

or

Cookie:NITRO_AUTH_TOKEN=token_value<String>

Request Payload:

{"tacacs_server": {
<b>"tacacs_key":<String_value></b>,
<b>"name":<String_value></b>,
<b>"ip_address":<String_value></b>,
"auth_timeout":<Integer_value>,
"id":<String_value>,
"port":<Integer_value>,
"accounting":<Boolean_value>,
"group_attr_name":<String_value>}}

<!--NeedCopy-->

Response: HTTPS Status Code on Success: 200 OK HTTPS Status Code on Failure: 4xx (for general HTTPS errors) or 5xx (for NetScaler-MAS-specific errors). The response payload provides details of the error

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value;gt, "tacacs_server":[{
"tacacs_key":<String_value>,
"auth_timeout":<Integer_value>,
"name":<String_value>,
"group_attr_name":<String_value>,
"port":<Integer_value>,
"id":<String_value>,
"ip_address":<String_value>,
"accounting":<Boolean_value>,
"address_type":<Integer_value>}]}

<!--NeedCopy-->

delete

URL: https://<MGMT-IP>/nitro/v2/config/tacacs_server/id_value<String> HTTPS Method: DELETE

Request Headers: X-NITRO-USER:username_value<String>

X-NITRO-PASS:password_value<String>

or

Cookie:NITRO_AUTH_TOKEN=token_value<String>

Response: HTTPS Status Code on Success: 200 OK HTTPS Status Code on Failure: 4xx (for general HTTPS errors) or 5xx (for NetScaler-MAS-specific errors). The response payload provides details of the error

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value;gt }

<!--NeedCopy-->

get (all)

URL: https://<MGMT-IP>/nitro/v2/config/tacacs_server Query-parameters:

filter https://<MGMT-IP>/nitro/v2/config/tacacs_server ?filter=property-name1:property-value1,property-name2:property-value2 Use this query-parameter to get the filtered set of tacacs_server resources configured on the system. You can set a filter on any property of the resource.

pagesize=#no;pageno=#no https://<MGMT-IP>/nitro/v2/config/tacacs_server ?pagesize=#no;pageno=#no Use this query-parameter to get the tacacs_server resources in chunks.

count https://<MGMT-IP>/nitro/v2/config/tacacs_server ?count=yes Use this query-parameter to get the count of tacacs_server resources.

HTTPS Method: GET

Request Headers: Accept: application/json

X-NITRO-USER:username_value<String>

X-NITRO-PASS:password_value<String>

or

Cookie:NITRO_AUTH_TOKEN=token_value<String>

Response: HTTPS Status Code on Success: 200 OK HTTPS Status Code on Failure: 4xx (for general HTTPS errors) or 5xx (for NetScaler-MAS-specific errors). The response payload provides details of the error

Response Headers:

Content-Type:application/json

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value;gt, "tacacs_server":[{
"tacacs_key":<String_value>,
"auth_timeout":<Integer_value>,
"name":<String_value>,
"group_attr_name":<String_value>,
"port":<Integer_value>,
"id":<String_value>,
"ip_address":<String_value>,
"accounting":<Boolean_value>,
"address_type":<Integer_value>}]}

<!--NeedCopy-->

get

URL: https://<MGMT-IP>/nitro/v2/config/tacacs_server/id_value<String> HTTPS Method: GET

Request Headers: Accept: application/json

X-NITRO-USER:username_value<String>

X-NITRO-PASS:password_value<String>

or

Cookie:NITRO_AUTH_TOKEN=token_value<String>

Response: HTTPS Status Code on Success: 200 OK HTTPS Status Code on Failure: 4xx (for general HTTPS errors) or 5xx (for NetScaler-MAS-specific errors). The response payload provides details of the error

Response Headers:

Content-Type:application/json

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value;gt, "tacacs_server":[{
"tacacs_key":<String_value>,
"auth_timeout":<Integer_value>,
"name":<String_value>,
"group_attr_name":<String_value>,
"port":<Integer_value>,
"id":<String_value>,
"ip_address":<String_value>,
"accounting":<Boolean_value>,
"address_type":<Integer_value>}]}

<!--NeedCopy-->

update

URL: https://<MGMT-IP>/nitro/v2/config/tacacs_server/id_value<String> HTTPS Method: PUT

Request Headers: Content-Type: application/json

X-NITRO-USER:username_value<String>

X-NITRO-PASS:password_value<String>

or

Cookie:NITRO_AUTH_TOKEN=token_value<String>

Request Payload:

{"tacacs_server":{
<b>"name":<String_value></b>,
<b>"id":<String_value></b>,
<b>"ip_address":<String_value></b>,
"auth_timeout":<Integer_value>,
"tacacs_key":<String_value>,
"port":<Integer_value>,
"accounting":<Boolean_value>,
"group_attr_name":<String_value>}}

<!--NeedCopy-->

Response: HTTPS Status Code on Success: 200 OK HTTPS Status Code on Failure: 4xx (for general HTTPS errors) or 5xx (for NetScaler-MAS-specific errors). The response payload provides details of the error

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value;gt, "tacacs_server":[{
"tacacs_key":<String_value>,
"auth_timeout":<Integer_value>,
"name":<String_value>,
"group_attr_name":<String_value>,
"port":<Integer_value>,
"id":<String_value>,
"ip_address":<String_value>,
"accounting":<Boolean_value>,
"address_type":<Integer_value>}]}

<!--NeedCopy-->
tacacs_server