Skip to content

Commit 594f1f8

Browse files
committed
merge from master
2 parents ef23294 + 303b3af commit 594f1f8

File tree

753 files changed

+9150
-6814
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

753 files changed

+9150
-6814
lines changed

.openpublishing.redirection.json

Lines changed: 271 additions & 51 deletions
Large diffs are not rendered by default.

articles/active-directory-b2c/active-directory-b2c-how-to-enable-billing.md

Lines changed: 85 additions & 45 deletions
Large diffs are not rendered by default.

articles/active-directory-b2c/active-directory-b2c-reference-oidc.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -145,7 +145,7 @@ grant_type=authorization_code&client_id=90c0fe63-bcf2-44d5-8fb7-b8bbc0b29dc6&sco
145145
| {tenant} | Yes | Name of your Azure AD B2C tenant |
146146
| {policy} | Yes | The user flow that was used to acquire the authorization code. You can't use a different user flow in this request. Add this parameter to the query string, not to the POST body. |
147147
| client_id | Yes | The application ID that the [Azure portal](https://portal.azure.com/) assigned to your application. |
148-
| client_secret | Yes | The application secret that was generated in the [Azure portal](https://portal.azure.com/). This application secret is an important security artifact. You should store it securely on your server. Change this client secret on a periodic basis. |
148+
| client_secret | Yes, in Web Apps | The application secret that was generated in the [Azure portal](https://portal.azure.com/). Client secrets are used in this flow for Web App scenarios, where the client can securely store a client secret. For Native App (public client) scenarios, client secrets cannot be securely stored, threfore not used on this flow. If using a client secret, please change it on a periodic basis. |
149149
| code | Yes | The authorization code that you acquired in the beginning of the user flow. |
150150
| grant_type | Yes | The type of grant, which must be `authorization_code` for the authorization code flow. |
151151
| redirect_uri | Yes | The `redirect_uri` parameter of the application where you received the authorization code. |
@@ -214,7 +214,7 @@ grant_type=refresh_token&client_id=90c0fe63-bcf2-44d5-8fb7-b8bbc0b29dc6&scope=op
214214
| {tenant} | Yes | Name of your Azure AD B2C tenant |
215215
| {policy} | Yes | The user flow that was used to acquire the original refresh token. You can't use a different user flow in this request. Add this parameter to the query string, not to the POST body. |
216216
| client_id | Yes | The application ID that the [Azure portal](https://portal.azure.com/) assigned to your application. |
217-
| client_secret | Yes | The application secret that was generated in the [Azure portal](https://portal.azure.com/). This application secret is an important security artifact. You should store it securely on your server. Change this client secret on a periodic basis. |
217+
| client_secret | Yes, in Web Apps | The application secret that was generated in the [Azure portal](https://portal.azure.com/). Client secrets are used in this flow for Web App scenarios, where the client can securely store a client secret. For Native App (public client) scenarios, client secrets cannot be securely stored, threfore not used on this call. If using a client secret, please change it on a periodic basis. |
218218
| grant_type | Yes | The type of grant, which must be a refresh token for this part of the authorization code flow. |
219219
| refresh_token | Yes | The original refresh token that was acquired in the second part of the flow. The `offline_access` scope must be used in both the authorization and token requests in order to receive a refresh token. |
220220
| redirect_uri | No | The `redirect_uri` parameter of the application where you received the authorization code. |
Loading
49.3 KB
Loading
Loading
33.4 KB
Loading

0 commit comments

Comments
 (0)