Skip to content

Commit f4005b5

Browse files
Remove obsolete section
1 parent 2012bcf commit f4005b5

File tree

1 file changed

+0
-6
lines changed

1 file changed

+0
-6
lines changed

site/management.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -349,12 +349,6 @@ curl -i --header "authorization: Bearer <token>" http://localhost:15672/ap
349349
This is true for all endpoints except `GET /definitions` and `POST /definitions`. Those
350350
endpoints require the token to be passed in the `token` query string parameter.
351351

352-
### Minimum scope required and how the UI determines the username from the token
353-
354-
At a minimum, RabbitMQ requires the the `openid` scope because it uses some claims in the *id token* to determine the username and to display this username on the top right corner of the management UI. The *id token* is returned by the Authorization server if the `openid` scope is included in the authorization request.
355-
356-
RabbitMQ reads the `user_name` claim from the *id_token*. If the token does not contain the `user_name`, RabbitMQ uses the `sub` claim.
357-
358352
### Configure which scopes RabbitMQ requests to the authorization server
359353

360354
It is possible to configure which OAuth 2.0 scopes RabbitMQ should claim when redirecting the user to the authorization server.

0 commit comments

Comments
 (0)