Authentication - Cisco CRS-1 - Carrier Routing System Router Api Manual

Chapter 11 XML Transport and Event Notifications
*
* IN - internally generated context for a given valid login session.
* Clients pass this as it is obtained in login method.
*
* Argument: request
*
* IN - XML request string. Passed to XML Infra for processing
*
* Argument: response
*
* OUT - contain response obtained from XML Infra or error code
* and error message string in case of response failure from XML Infra.
*
*/
/*
* edt: * * XMLAgent::logout
*
* Provides the definition for the logout() method for the XMLAgent idl
*
* Return: None
*
* Argument: session_context
*
* IN - internally generated context for a given valid login session.
* Clients will pass as it is obtained in login method.
*
* Argument: response
*
* OUT - contain error code and error message string in case of failure.
*
*/
};

Authentication

Client applications must authenticate with the CORBA XML agent before sending any requests. The
authentication is done via the "login()" method of the CORBA XML agent IDL. The username and
password supplied are used to contact and call authentication, authorization, and accounting (AAA)
server APIs for authentication on the router. Only after successful authentication is the client application
able to send XML encode requests to the router using the "invoke()" method.
The "login()" implementation in the CORBA XML agent uses the following AAA options as part of the
Authentication API:
•
•
OL-4596-01
void invoke (in long session_context,
in string request,
out string response);
void logout (in long session_context,
out string response);
};
"default" is used as the authentication method.
ASCII authentication is used for the username and password. As a result, the username and
password supplied in the "login()" method call should be unencrypted ASCII text. Any security for
transport should use Secure Socket Layer (SSL).
Cisco CRS-1 Series XML Transport and CORBA IDL
Cisco CRS-1 Series Carrier Routing System XML API Guide
11-105