Cisco 300-550 - Questions & Answers

Authentication to the REST API for username/password-based authentication uses a special subset of request URIs, including aaaLogin, aaaLogout and aaaRefresh as the Dn target of a POST operation. Their payloads contain a simple XML or JSON payload containing the MO representation of an aaaUser object with attributes name and pwd defining the username and password, for example: <aaaUser name='admin'
pwd='insieme'/>. The response to the POSTs will contain an authentication token as both a Set-Cookie header as well as an attribute to the aaaLogin object in the response named token, for which the XPath is / imdata/aaaLogin/@token if encoded as XML. Subsequent operations on the REST API can use this token value as a Cookie named "APIC-cookie" to have future requests authenticated.

References:
http://aci-troubleshooting-book.readthedocs.io/en/latest/rest.html

JSON-RPC is an RPC protocol built on JSON, as a replacement for XML-RPC or SOAP. It is a simple protocol that defines only a handful of data types and commands. JSON-RPC lets a system send notifications (information to the server that does not require a response) and multiple calls to the server that can be answered out of order. Example of a JSON-RPC 2.0 request and response using positional parameters.

References:
https://tools.ietf.org/html/draft-ietf-netconf-restconf-13#section-1.1.1
5.3.2 (https://tools.ietf.org/html/draft-box-http-soap-00)
XML payload format in SOAP

The "include" statement is used to make content from a submodule available to that submodule's parent module, or to another submodule of that parent module.

References:
https://tools.ietf.org/html/rfc6020