Skip to main content
  • EN

Hello Forum. I'm trying to help a colleague to setup an Oauth2 service (Tools->WebConnections->+->Oauth2Service) but we're struggling. We have the parameters from the data-owner, and the "Preview" window in the setup dialog presents an acceptable URL (see attached image), but when the connection is made to the server, the URL is malformed. The problem is that the URL received on the server is terminated (prior to the parameters) with ampersand thus:

 

  • /realms/fdir-dev/protocol/openid-connect/auth&redirect_uri=https://localhost/&client_id=yggdrasil-sa

 

 instead of question-mark as reported in the setup-dialog Preview (see image) The question-mark is required by the server and html convention. Has anyone had success with the OAuth2 server connector, who might be able to guide us, or is this simply a bug?

The trick here, as we found out from a helpful reseller-support, is that one must provide the question-mark as part of the authorization url.  Either as terminator, or with an initial parameter, thus our re-formed URL looks like so:

https://.../realms/fdir-dev/protocol/openid-connect/auth?response_type=code

 

Reply


Community Stats

30,133
Posts
114,389
Replies
37,772
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.