You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2020/09/03 12:14:06 UTC

[GitHub] [pulsar] harissecic edited a comment on issue #7952: OAuth2 url .well-known not parsed correctly

harissecic edited a comment on issue #7952:
URL: https://github.com/apache/pulsar/issues/7952#issuecomment-686447346


   > Hi, @harissecic By this error `java.io.IOException: Cannot obtain authorization metadata from https://***/.well-known/openid-configuration`, it seems the client can not access the configuration URL. Have you tried to using curl to get it directly?
   
   I'm afraid you didn't read it entirely.
   
   1. https://***/.well-known/openid-configuration is incorrect and that's on Pulsar side 100%
   2. https://*****/auth/realms/*** is passed in and is quite clear and pointed out that /auth/realms/*realmId* is being stripped inside Pulsar code and /.well-known/openid-configuration is being appended at the base URL when my realms are stripped as I stated in the issue as first sentence after the log.
   > So it appears that extra path after the base URL is ignored and stripped
   3. Endpoint I provide i 100% correct and working. My APIs are using that same URL.
   
   Please not that stars are used to hide the actual BASE URL and REALM part is left to be pointed out.
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org