oauth2 connection authenticated only once per resource server #11936
-
Describe the bugI can successfully connect to the broker with oauth2, but only once for each resource server. How can this be? Error message after first connection: "Authentication using an OAuth 2/JWT token failed: {error,no_key}" RabbitMQ is running local with this Dockerfile
rabbitmq.conf
definitions.conf
I appreciate any help. Reproduction stepsReproduced with management ui I have to restart the rabbitmq server to successfully authenticate again. Reproduced with PhpAmqpLib as producer client
Complete log
Expected behaviorI excepted oauth2 to accept every connection in attached examples. Additional contextContent of jwks_url endpoint:
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Please take the time to reproduce this issue using the latest version of RabbitMQ (3.13.6). We do not provide free community support for any version other than the latest. |
Beta Was this translation helpful? Give feedback.
-
There is only one place in the code where this specific error is returned: when no key for the resource server exists and no default key is configured. Why that might be, you will have to narrow down on your own using the doc guides above (and source code if necessary). |
Beta Was this translation helpful? Give feedback.
In fact, we do not provide any OAuth 2 troubleshooting support at all to non-paying users who are not regular contributors.
But there are three extensive documentation guides:
Plus enabling debug logging will reveal a lot of decisions made by the authN and authZ backends.