Skip to main content
Solved

FME Client sending incorrect URL to Oauth2 Service (Keycloak) authenticator. Is this a bug?

  • October 27, 2022
  • 1 reply
  • 50 views

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?

Best answer by williamm

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

 

View original
Did this help you find an answer to your question?

1 reply

  • Author
  • Best Answer
  • November 3, 2022

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

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings