Issue while openId connect configuration in Apache pulsar 3.2.x server #22394
Unanswered
ragaur-tibco
asked this question in
Q&A
Replies: 1 comment
-
The 401 can be caused by anything, from a bad OAuth2 cred, to bad OIDC setup (ex: mismatched issuer). If possible, you may want to run your OIDC setup in standalone mode, with the function workers off (bin/pulsar standalone -nfw -nss); I ran into issues setting this up, and the root cause for the 401 was hidden further up the log stream. The 401 stack traces were masking the real issue. You can also bind your OAuth2 config to your conf/client.conf, then run any authorized admin op (ex: admin tenants list) against the instance. Those requests also made the true cause pop out more for me... |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
After setting up the OAuth0 with openId configuration and providing the below configuration on standalone.conf file and issuer url and token issuers from OAuth0
Apache pulsar version 3.2.x
facing below error
Beta Was this translation helpful? Give feedback.
All reactions