Skip to content

Commit ea0b6bd

Browse files
author
gitName
committed
review feedback
1 parent 0391b98 commit ea0b6bd

File tree

1 file changed

+9
-6
lines changed

1 file changed

+9
-6
lines changed

articles/api-center/authorize-api-access.md

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to configure access to APIs in the Azure API Center inven
44
author: dlepow
55
ms.service: azure-api-center
66
ms.topic: how-to
7-
ms.date: 04/28/2025
7+
ms.date: 04/30/2025
88
ms.author: danlep
99
ms.custom:
1010
# Customer intent: As an API program manager, I want to store API authorization information in my API center and enable authorized users to test APIs in the API Center portal.
@@ -117,16 +117,19 @@ To manage the secret securely, store it in Azure Key Vault, and access the key v
117117
:::image type="content" source="media/authorize-api-access/configure-oauth.png" alt-text="Screenshot of configuring OAuth 2.0 in the portal.":::
118118

119119

120+
> [!NOTE]
121+
> Configure settings based on the app registration you created previously in your identity provider. If you're using Microsoft Entra ID, find the **Client ID** on the **Overview** page of the app registration, and find the URL endpoints on the **Overview** > **Endpoints** page.
122+
120123
| **Setting** | **Description** |
121124
|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|
122125
| **Title** | A name for the authorization. |
123126
| **Description** | Optional description for the authorization. |
124127
| **Security scheme** | Select **OAuth2**. |
125-
| **Client ID** | Client ID of the app that you created in the previous section. |
126-
| **Client secret** | Secret identifier of the client secret in Azure Key Vault. Example: `https://<key-vault-name>.vault.azure.net/secrets/<secret-name>/<version>` |
127-
| **Authorization URL** | OAuth 2.0 authorization endpoint for the identity provider. |
128-
| **Token URL** | OAuth 2.0 token endpoint for the identity provider. |
129-
| **Refresh URL** | OAuth 2.0 refresh token endpoint for the identity provider. For most providers, same as the Token URL. |
128+
| **Client ID** | Client ID (GUID) of the app that you created in your identity provider. |
129+
| **Client secret** | Secret identifier of the client secret in Azure Key Vault.<br/><br/>Example: `https://<key-vault-name>.vault.azure.net/secrets/<secret-name>/<version>` |
130+
| **Authorization URL** | OAuth 2.0 authorization endpoint for the identity provider.<br/><br/>Example for Microsoft Entra ID: `https://login.microsoftonline.com/<tenant>/oauth2/v2.0/authorize` |
131+
| **Token URL** | OAuth 2.0 token endpoint for the identity provider.<br/><br/>Example for Microsoft Entra ID: `https://login.microsoftonline.com/<token>/oauth2/v2.0/token` |
132+
| **Refresh URL** | OAuth 2.0 token refresh endpoint for the identity provider. For most providers, same as the **Token URL**<br/><br/>Example for Microsoft Entra ID: `https://login.microsoftonline.com/<token>/oauth2/v2.0/token` |
130133
| **OAuth2 flow** | One or both of the OAuth 2.0 flows that you want to use. Available values are **Authorization code (PKCE)** and **Client credentials**. |
131134
| **Scopes** | One or more API scopes configured for your API, separated by spaces. If no scopes are configured, enter `.default`. |
132135

0 commit comments

Comments
 (0)