Cisco Cisco ASA 5580 Adaptive Security Appliance
About the ASA REST API v1.1.1
Limitations
Limitations
33
‘‘commands’’: [‘‘command-1’’, ‘‘command-2’’,…, ‘‘command-n’’]
}
Response:
{
‘‘response’’: [‘‘command-1 response’’, ‘‘command-2 response’’,…, ‘‘command-n response’’]
}
Limitations
The debug commands are not supported in CLI pass-through. All debug commands are per terminal session, and not a
global configuration. So, if debug commands are sent over CLI pass-through, either they might return error or success
response, but they do not have any effect on the device.
Token Authentication API
REST client needs to send a POST request to '/api/tokenservices', with user information in the basic authentication
header to get a token for that user. Subsequently REST client can use this token in a 'X-Auth-Token' request header for
header to get a token for that user. Subsequently REST client can use this token in a 'X-Auth-Token' request header for
any subsequent REST API calls. The 'token' will be valid until either it is explicitly invalidated by 'DELETE
/api/tokenservices/<token>' request using user information in the basic authentication header or session times out.
The details of request payload, response structure are as follows. POST URL: /api/tokenservices
Post request payload is empty. The user information should be in basic authentication header. The response could be as
follows.
Reason
HTTP Status Code
AAA validation failure/ Authorization
header not present
401 Unauthorized
Authentication success
204 No Content + X-Auth-Token <token id> (header
Can’t get username/password from the
header or any other sanity check failures
400 Bad Request.
Maximum sessions reached
503 Service unavailable
Note: The maximum sessions per context is 25.
To delete a token. DELETE URL: /pai/tokenservices/<token>