I was able to register a management and rest node with Context Service using one account but when I try to register the same custom app with an account that uses single sign on I get an internal server error caused by a failed access token call.
The steps to reproduce this are as follows:
1. Download the sample code from https://github.com/CiscoDevNet/context-service-sample-code/tree/master/Webapp_Sample_Project
2. Follow the instructions here to prepare the Tomcat Server and build the project
3. Browse to http://localhost:8082/management
4. Click Register, then accept redirect to callback url - From here, a number of calls are made to authorise/register the app
5. At this point a POST to "https://idbroker.webex.com/idb/oauth2/v1/access_token" with an access token returns a 400 bad request (see screenshot below)
Following these steps using the account which doesn't have SSO, registration completes successfully (step 5 returns 200 OK) and gives the following:
As you can see from the screenshots, some of these access token calls do fail with the non SSO account but this only happens further on in the process and does not prevent registration from completing successfully.
I can only assume that the SSO is causing this issue as it's the only difference I can see between the two accounts. Any ideas how to get around this problem? Or is there some other way of getting a connection data string? I've attached the HAR file for the problematic registration for further debugging (the failing call starts on line 12079). Any help would be greatly appreciated.
