Cisco Cisco 3365 Mobility Services Engine White Paper

Page 50 of 55

Credentials are created on Cisco MSE through Cisco Prime Infrastructure:

●

Requests are sent, after authentication, using GET and the resource needed.

●

Authentication can be sent from the client side before the request, using the Authorization header.

●

The username and password are combined into the string username: password.

●

The resulting string literal is then encoded using Base64.

●

The authorization method, a space, and the string Basic is then inserted before the encoded string.

For example, if the user agent uses Aladin as the username and sesame open as the password, the header is

formed as follows:

Authorization: Basic QxhZGluOnNlc2FtIG9wZW4=

●

Authentication can be requested from the server, using the HTTP 401 Not Authorized response code

containing a WWW-Authenticate HTTP header.

●

The header for basic authentication is constructed as follows:

WWW-Authenticate: Basic realm=“MSE API Service”

●

Authentication is sent to the root URI to be reached (for example, https://<mseip>/api/contextaware).

●

From the main URI, GET is used to obtain information about a specific object: network design, location, or

notification resources.

●

In this release, CAS resources start with v1; for example:

GET /v1/location/{deviceType}/{id}

Tip: Joining the Cisco Developer Network will give you the best support for creating applications that access the

Cisco MSE REST API. Check out

http://developer.cisco.com/web/mobility-services

Troubleshooting the Analytics Environment

To accurate produce results in Cisco CMX Location Analytics, a valid chain of processes has to be set up to

deliver the right data to the analytics engine to generate results. Every part of the chain needs to be set up

correctly to work (see

Cisco Location Analytics Service Configuration Guide