You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/oauth2-examples-entra-id/index.md
+17-4
Original file line number
Diff line number
Diff line change
@@ -75,14 +75,18 @@ When using **Entra ID as OAuth 2.0 server**, your client app (in our case Rabbit
75
75
Note the value of the `jwks_uri` key (ex: `https://login.microsoftonline.com/{TENANT_ID}/discovery/v2.0/keys`), as you will also need it later to configure the `rabbitmq_auth_backend_oauth2` on RabbitMQ side.
76
76
77
77
78
-
8. If the **Endpoints** tab is not visible,
78
+
8. If the **Endpoints** tab is not visible,
79
79
80
80
81
81
## Create OAuth 2.0 roles for your app
82
82
83
83
App roles are defined by using the [Entra ID portal](https://portal.azure.com) during the app registration process. When a user signs in to your application, Entra ID emits a `roles` claim for each role that the user or service principal has been granted (you will have a look at it at the end of this tutorial).
84
84
85
-
<g-emojiclass="g-emoji"alias="blue_book"fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4d8.png">📘</g-emoji> More details about roles in Entra ID are available [here](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-add-app-roles-in-azure-ad-apps).
85
+
:::info
86
+
87
+
To learn more about roles in Entra ID, see [Entra ID documentation](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-add-app-roles-in-azure-ad-apps)
88
+
89
+
:::
86
90
87
91
1. Still in [Entra ID Portal](https://portal.azure.com), go back to **Entra ID** home page.
88
92
@@ -94,7 +98,12 @@ App roles are defined by using the [Entra ID portal](https://portal.azure.com) d
94
98
95
99
2. Then, click on **Create App Role** to create an OAuth 2.0 role that will be used to give access to the RabbitMQ Management UI.
96
100
97
-
<g-emojiclass="g-emoji"alias="blue_book"fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4d8.png">📘</g-emoji> More details about how permissions are managed on RabbitMQ when using OAuth 2.0 are available [here](https://github.com/rabbitmq/rabbitmq-oauth2-tutorial#about-permissions).
101
+
:::info
102
+
103
+
To learn more about how permissions are managed when RabbitMQ is used together with OAuth 2.0,
104
+
see [this portion of the OAuth 2 tutorial](https://github.com/rabbitmq/rabbitmq-oauth2-tutorial#about-permissions)
105
+
106
+
:::
98
107
99
108
3. On the right menu that has just opened, provide the requested information:
100
109
@@ -141,7 +150,11 @@ Now that some roles have been created for your application, you still need to as
141
150
142
151
7. Back to the **Add assignment** pane, below **Select a Role**, click on *None Selected* and, on the **Select a role** pane that has just opened on the right, search and select the role you want to assign to the selected users.
143
152
144
-
<g-emojiclass="g-emoji"alias="bulb"fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4a1.png">💡</g-emoji> If only one role is available for your application, it would be automatically selected and greyed by default.
153
+
:::tip
154
+
155
+
If only one role is available for your application, it would be automatically selected and greyed by default.
156
+
157
+
:::
145
158
146
159
8. Choose a role (only a single role can be selected at a time), click on the **Select** button, and click on the **Assign** button to finalize the assignment of users and groups to the app.
Copy file name to clipboardExpand all lines: docs/oauth2-examples-okta.md
+2-1
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,8 @@ contains all the configuration files and scripts used on this example
38
38
39
39
When using **Okta as OAuth 2.0 server**, your client app (in our case RabbitMQ) needs a way to trust the security tokens issued to it by the **Okta OIDC Sign-In Widget**.
40
40
41
-
The first step in establishing that trust is by **creating your app** with the identity platform in Okta. More details about App registration in Okta are available [here](https://help.okta.com/en-us/Content/Topics/Apps/Apps_App_Integration_Wizard_OIDC.htm).
41
+
The first step in establishing that trust is by **creating your app** with the identity platform in Okta. To learn more about App registration in Okta,
42
+
please refer to [Okta documentation](https://help.okta.com/en-us/Content/Topics/Apps/Apps_App_Integration_Wizard_OIDC.htm).
42
43
43
44
Once you have logged onto your account in [Okta](https://www.okta.com), follow below steps:
Copy file name to clipboardExpand all lines: versioned_docs/version-3.13/oauth2-examples-entra-id/index.md
+16-3
Original file line number
Diff line number
Diff line change
@@ -82,7 +82,11 @@ When using **Entra ID as OAuth 2.0 server**, your client app (in our case Rabbit
82
82
83
83
App roles are defined by using the [Entra ID portal](https://portal.azure.com) during the app registration process. When a user signs in to your application, Entra ID emits a `roles` claim for each role that the user or service principal has been granted (you will have a look at it at the end of this tutorial).
84
84
85
-
<g-emojiclass="g-emoji"alias="blue_book"fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4d8.png">📘</g-emoji> More details about roles in Entra ID are available [here](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-add-app-roles-in-azure-ad-apps).
85
+
:::info
86
+
87
+
To learn more about roles in Entra ID, see [Entra ID documentation](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-add-app-roles-in-azure-ad-apps)
88
+
89
+
:::
86
90
87
91
1. Still in [Entra ID Portal](https://portal.azure.com), go back to **Entra ID** home page.
88
92
@@ -94,7 +98,12 @@ App roles are defined by using the [Entra ID portal](https://portal.azure.com) d
94
98
95
99
2. Then, click on **Create App Role** to create an OAuth 2.0 role that will be used to give access to the RabbitMQ Management UI.
96
100
97
-
<g-emojiclass="g-emoji"alias="blue_book"fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4d8.png">📘</g-emoji> More details about how permissions are managed on RabbitMQ when using OAuth 2.0 are available [here](https://github.com/rabbitmq/rabbitmq-oauth2-tutorial#about-permissions).
101
+
:::info
102
+
103
+
To learn more about how permissions are managed when RabbitMQ is used together with OAuth 2.0,
104
+
see [this portion of the OAuth 2 tutorial](https://github.com/rabbitmq/rabbitmq-oauth2-tutorial#about-permissions)
105
+
106
+
:::
98
107
99
108
3. On the right menu that has just opened, provide the requested information:
100
109
@@ -141,7 +150,11 @@ Now that some roles have been created for your application, you still need to as
141
150
142
151
7. Back to the **Add assignment** pane, below **Select a Role**, click on *None Selected* and, on the **Select a role** pane that has just opened on the right, search and select the role you want to assign to the selected users.
143
152
144
-
<g-emojiclass="g-emoji"alias="bulb"fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4a1.png">💡</g-emoji> If only one role is available for your application, it would be automatically selected and greyed by default.
153
+
:::tip
154
+
155
+
If only one role is available for your application, it would be automatically selected and greyed by default.
156
+
157
+
:::
145
158
146
159
8. Choose a role (only a single role can be selected at a time), click on the **Select** button, and click on the **Assign** button to finalize the assignment of users and groups to the app.
Copy file name to clipboardExpand all lines: versioned_docs/version-3.13/oauth2-examples-okta.md
+2-1
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,8 @@ contains all the configuration files and scripts used on this example
38
38
39
39
When using **Okta as OAuth 2.0 server**, your client app (in our case RabbitMQ) needs a way to trust the security tokens issued to it by the **Okta OIDC Sign-In Widget**.
40
40
41
-
The first step in establishing that trust is by **creating your app** with the identity platform in Okta. More details about App registration in Okta are available [here](https://help.okta.com/en-us/Content/Topics/Apps/Apps_App_Integration_Wizard_OIDC.htm).
41
+
The first step in establishing that trust is by **creating your app** with the identity platform in Okta. To learn more about App registration in Okta,
42
+
please refer to [Okta documentation](https://help.okta.com/en-us/Content/Topics/Apps/Apps_App_Integration_Wizard_OIDC.htm).
42
43
43
44
Once you have logged onto your account in [Okta](https://www.okta.com), follow below steps:
0 commit comments