Skip to content

Entra ID Oauth broken after upgrading to 4.1.0 #13887

Closed Answered by Dutchy-
Dutchy- asked this question in Other
Discussion options

You must be logged in to vote

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

      auth_backends.1 = internal
      auth_backends.2 = rabbit_auth_backend_oauth2
      log.console = true
      log.console.level = info
      management.path_prefix = /rabbit
      management.di…

Replies: 4 comments 3 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@Dutchy-
Comment options

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
2 replies
@Dutchy-
Comment options

@michaelklishin
Comment options

Answer selected by Dutchy-
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #13887 on May 12, 2025 17:27.