The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
MSE APIs uses basic authentication scheme to authenticate the API request. Each API Request, contains the API access credentials in the Authorization header. The API credentials are generated by the MSE Administrator using the Prime Infrastructure user interface.
To access this page, log into Prime Infrastructure UI and choose Services > Mobility Services > choose the name of the mobility services engine > Systems > Users.
Note The user credentials have read and write permissions associated with it. User credentials without write permissions can only perform GET operations on the REST API resources. In addition, certain APIs will only return the configurations created by the requesting user.
The Authorization header is constructed as follows:
For example, if the username is 'Aladin' and the password is 'sesame open', then the header is formed as follows:
If the API request does not have the Authorization header or if the credentials are incorrect, then the MSE will send a HTTP 401 Not Authorized response code containing the authenticate header as below: