From baa2b3c2552c1e3a29e0f60b534e528488b2b4bf Mon Sep 17 00:00:00 2001 From: Marcial Rosales Date: Wed, 2 Oct 2024 13:22:50 +0200 Subject: [PATCH] Minor correction --- docs/management/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/management/index.md b/docs/management/index.md index 082fa701c..17ada2ed9 100644 --- a/docs/management/index.md +++ b/docs/management/index.md @@ -411,7 +411,7 @@ Given above configuration, when a user visits the management UI, the following t ::: :::tip - If you used to configure `auth_oauth2.metadata_url` because your provider did not use the standard path OpenId Discovery endpoint's path, since RabbitMQ 4.1 you should instead configure the correct path and/or include any additional parameters as it is explained [here](./oauth2#discovery-endpoint-params). + If you used to configure `management.oauth_metadata_url` because your provider did not use the standard OpenId Discovery endpoint's path, since RabbitMQ 4.1 you should instead configure the correct path as it is explained [here](./oauth2#discovery-endpoint-params). ::: 2. RabbitMQ displays a button with the label "Click here to login". When the user clicks on the button, the management UI initiates the OAuth 2.0 Authorization Code Flow, which redirects the user to the identity provider to authenticate and get a token.