OAuth authentication with CCM in RTC 3.0
I have a question related to OAuth authentication in CCM/JTS. Similar to http://jazz.net/forums/viewtopic.php?t=15572&highlight=ccm+consumer
I wish to invoke services on the CCM application (hosted in RTC 3.0) from my application, which is already registered as an OAuth consumer of CCM. The JFS3.0 SDK tutorials show how to consume JFS services from consumers from JFS. The starting point is the JTS discovery services URL from which you create an OAuth provider used to kick-off the OAuth process with a consumer. I find the discovery service for CCM as "https://localhost:9443/ccm/discovery" in the CCM root services document, but I cannot successfully recover a discovery service object using the DiscoveryHelper initialized with the above URL. Could you please point where I am going wrong? Here is the code snippet, I have been using.
I wish to invoke services on the CCM application (hosted in RTC 3.0) from my application, which is already registered as an OAuth consumer of CCM. The JFS3.0 SDK tutorials show how to consume JFS services from consumers from JFS. The starting point is the JTS discovery services URL from which you create an OAuth provider used to kick-off the OAuth process with a consumer. I find the discovery service for CCM as "https://localhost:9443/ccm/discovery" in the CCM root services document, but I cannot successfully recover a discovery service object using the DiscoveryHelper initialized with the above URL. Could you please point where I am going wrong? Here is the code snippet, I have been using.
//Configure the discovery service
Discovery.setDiscoveryServiceUriForAppGroup("https://localhost:9443/ccm/discovery");
..........
..........
IDiscoveryHelper discoveryHelper = Discovery.getHelperForAppGroup();
IServiceResource oauthservice = discoveryHelper.getService(
DiscoveryConstants.SERVICE_TYPE_OAUTH, null);
}
One answer
CCM (and QM) does not really have a discovery service. They have a stub service that just returns a redirect for the JTS discovery service.
As I mentioned in our private chat, you could use the RootServicesUtil class in the SDK to fetch and parse the /ccm/rootservices resource, and get the OAuth service URLs that way instead.
As I mentioned in our private chat, you could use the RootServicesUtil class in the SDK to fetch and parse the /ccm/rootservices resource, and get the OAuth service URLs that way instead.