Question

From the provided samples I got this URL that is supposed to provide an authorization code to the provide callBack URL

https://CONNECTIONSHOSTNAME/oauth2/endpoint/connectionsProvider/authorize?response_type=code&client_id=SocialDMS&callback_uri=http%3A%2F%2F_DEVELOPMENTHOSTNAME_%3A_DEVELOPMENTPORT_%2F_DEVELOPMENTServletPath_

The socialdms is registered as an application, but nothing happens. The callback_uri is accessible from the connections machine.

What logging can I switch on on the Connections Server to troubleshoot this ?

Should the callback_uri be SSL enabled ?

Was it helpful?

Solution 2

The callback url should be SSL enabled.

To do this you might have to re register your application with Connection server. This might help : http://www-10.lotus.com/ldd/lcwiki.nsf/xpDocViewer.xsp?lookupName=IBM+Connections+4.0+documentation#action=openDocument&res_title=Registering_an_OAuth_client_with_a_provider_ic40&content=pdcontent

OTHER TIPS

That URL should return an authorization form to the end user.

Does the callback_uri match the value provided when registering the application with Connections?

Please enable logging for com.ibm.ws.security.oauth20.*=all and check the trace.log file.

Yes.. the callback_uri should be SSL enabled.

HTTPS in the callback-uri seemed to do the trick

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top