-
Describe the bugAfter upgrading from 4.0.7 to 4.1.0, I can no longer login with Oauth/Entra ID because it fails with "Not Authorized". Reproduction stepsThis is my config for the cluster operator:
What happens in 4.1.0 is that the login process walks through the whole flow correctly, e.g.
In the server logs, I see this error:
I've redacted the token because I do not know what information is in there. I would like to restate that this was working fine in 4.0.7. I do not see any changes regarding oauth in the changelog, but in the commit history I see many changes to the oauth backend and management plugin on this front. Expected behaviorA successful login. Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 3 replies
-
@Dutchy- per our community support policy, we will not be troubleshooting OAuth 2 for non-paying users. There is a dedicated doc guide that covers a number of common scenarios. Entra specifically deviates from the spec and requires custom configuration #13788. The exception contains a |
Beta Was this translation helpful? Give feedback.
-
Thank you for your response. I am not very satisfied with the answer because the configuration broke after a minor update (4.0.7 to 4.1.0) and it is not a troubleshooting issue per se - the configuration was proven to be working before. However, I respect your right to not give support on oauth. I hope there are other people here who can share if they had a similar experience with 4.1.0. I'll try the configuration for the |
Beta Was this translation helpful? Give feedback.
-
@MarcialRosales do you have other observations from this config snippet and the stack trace? |
Beta Was this translation helpful? Give feedback.
-
Ok, I did some more digging, and I have some news. Apparently, this section in your guide is new: https://www.rabbitmq.com/docs/oauth2-examples-entra-id#create-a-scope-for-management-ui-access Apparently, the old config worked fine up until 4.1.0 My new config on the rabbitmq side now looks like this
When I check my |
Beta Was this translation helpful? Give feedback.
Ok, I did some more digging, and I have some news.
Apparently, this section in your guide is new: https://www.rabbitmq.com/docs/oauth2-examples-entra-id#create-a-scope-for-management-ui-access
It was added somewhere in the last year (I configured oauth for rabbitmq in the summer of last year).
I updated the config on the MS side and I updated the rabbitmq configuration and now it works.
Apparently, the old config worked fine up until 4.1.0
My new config on the rabbitmq side now looks like this