GitHub user slawrencemd added a comment to the discussion: Issue while openId connect configuration in Apache pulsar 3.2.x server
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... GitHub link: https://github.com/apache/pulsar/discussions/22394#discussioncomment-9009298 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
