Skip to content

Commit 0b749c8

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into az-api-mgt
2 parents ed4cda8 + fa63304 commit 0b749c8

File tree

1,484 files changed

+10849
-5541
lines changed

Some content is hidden

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

1,484 files changed

+10849
-5541
lines changed

.openpublishing.redirection.azure-monitor.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -216,6 +216,11 @@
216216
"redirect_url": "/azure/azure-monitor/visualize/workbooks-overview",
217217
"redirect_document_id": false
218218
},
219+
{
220+
"source_path_from_root": "/articles/azure-monitor/visualize/workbooks-sample-links.md",
221+
"redirect_url": "/azure/azure-monitor/visualize/workbooks-samples",
222+
"redirect_document_id": false
223+
},
219224
{
220225
"source_path_from_root": "/articles/azure-monitor/visualize/view-designer-conversion-access.md",
221226
"redirect_url": "/azure/azure-monitor/visualize/workbooks-overview",

articles/active-directory-b2c/TOC.yml

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -168,6 +168,14 @@
168168
href: enable-authentication-angular-spa-app.md
169169
- name: Authentication options
170170
href: enable-authentication-angular-spa-app-options.md
171+
- name: React single-page application
172+
items:
173+
- name: Configure a sample React app
174+
href: configure-authentication-sample-react-spa-app.md
175+
- name: Enable authentication in your React app
176+
href: enable-authentication-react-spa-app.md
177+
- name: Authentication options
178+
href: enable-authentication-react-spa-app-options.md
171179
- name: Android mobile app
172180
items:
173181
- name: Configure a sample Android app

articles/active-directory-b2c/configure-a-sample-node-web-app.md

Lines changed: 4 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ manager: CelesteDG
88
ms.service: active-directory
99
ms.workload: identity
1010
ms.topic: how-to
11-
ms.date: 06/08/2022
11+
ms.date: 07/07/2022
1212
ms.author: kengaderdus
1313
ms.subservice: B2C
1414
---
@@ -32,19 +32,13 @@ In this article, you’ll do the following tasks:
3232

3333
## Step 1: Configure your user flows
3434

35-
[!INCLUDE [active-directory-b2c-app-integration-add-user-flow](../../includes/active-directory-b2c-app-integration-add-user-flow.md)] Repeat the steps to create three separate user flows as follows:
36-
37-
- A combined **Sign in and sign up** user flow, such as `susi`. This user flow also supports the **Forgot your password** experience.
38-
- A **Profile editing** user flow, such as `edit_profile`.
39-
- A **Password reset** user flow, such as `reset_password`.
40-
41-
Azure AD B2C prepends `B2C_1_` to the user flow name. For example, `susi` becomes `B2C_1_susi`.
35+
[!INCLUDE [active-directory-b2c-app-integration-add-user-flow](../../includes/active-directory-b2c-app-integration-add-user-flow.md)]
4236

4337
## Step 2: Register a web application
4438

4539
To enable your application sign in with Azure AD B2C, register your app in the Azure AD B2C directory. The app registration establishes a trust relationship between the app and Azure AD B2C.
4640

47-
During app registration, you'll specify the *Redirect URI*. The redirect URI is the endpoint to which the user is redirected by Azure AD B2C after they authenticate with Azure AD B2C. The app registration process generates an *Application ID*, also known as the *client ID*, that uniquely identifies your app. After your app is registered, Azure AD B2C uses both the application ID and the redirect URI to create authentication requests.
41+
During app registration, you'll specify the *Redirect URI*. The redirect URI is the endpoint to which the user is redirected by Azure AD B2C after they authenticate with Azure AD B2C. The app registration process generates an *Application ID*, also known as the *client ID*, that uniquely identifies your app. After your app is registered, Azure AD B2C uses both the application ID, and the redirect URI to create authentication requests.
4842

4943
### Step 2.1: Register the app
5044

@@ -119,7 +113,7 @@ Open your web app in a code editor such as Visual Studio Code. Under the project
119113
|`EDIT_PROFILE_POLICY_AUTHORITY`|The **Profile editing** user flow authority such as `https://<your-tenant-name>.b2clogin.com/<your-tenant-name>.onmicrosoft.com/<profile-edit-user-flow-name>`. Replace `<your-tenant-name>` with the name of your tenant and `<reset-password-user-flow-name>` with the name of your reset password user flow such as `B2C_1_edit_profile_node_app`. |
120114
|`AUTHORITY_DOMAIN`| The Azure AD B2C authority domain such as `https://<your-tenant-name>.b2clogin.com`. Replace `<your-tenant-name>` with the name of your tenant.|
121115
|`APP_REDIRECT_URI`| The application redirect URI where Azure AD B2C will return authentication responses (tokens). It matches the **Redirect URI** you set while registering your app in Azure portal, and it must be publicly accessible. Leave the value as is.|
122-
|`LOGOUT_ENDPOINT`| The Azure AD B2C sign out endpoint such as `https://<your-tenant-name>.b2clogin.com/<your-tenant-name>.onmicrosoft.com/<sign-in-sign-up-user-flow-name>/oauth2/v2.0/logout?post_logout_redirect_uri=http://localhost:3000`. Replace `<your-tenant-name>` with the name of your tenant and `<sign-in-sign-up-user-flow-name>` with the name of your Sign in and Sign up user flow such as `B2C_1_susi`.|
116+
|`LOGOUT_ENDPOINT`| The Azure AD B2C sign-out endpoint such as `https://<your-tenant-name>.b2clogin.com/<your-tenant-name>.onmicrosoft.com/<sign-in-sign-up-user-flow-name>/oauth2/v2.0/logout?post_logout_redirect_uri=http://localhost:3000`. Replace `<your-tenant-name>` with the name of your tenant and `<sign-in-sign-up-user-flow-name>` with the name of your Sign in and Sign up user flow such as `B2C_1_susi`.|
123117

124118
Your final configuration file should look like the following sample:
125119

articles/active-directory-b2c/configure-authentication-in-sample-node-web-app-with-api.md

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ manager: CelesteDG
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: how-to
12-
ms.date: 06/08/2022
12+
ms.date: 07/07/2022
1313
ms.author: kengaderdus
1414
ms.subservice: B2C
1515
---
@@ -65,13 +65,7 @@ The application registrations and the application architecture are described in
6565

6666
## Step 1: Configure your user flow
6767

68-
[!INCLUDE [active-directory-b2c-app-integration-add-user-flow](../../includes/active-directory-b2c-app-integration-add-user-flow.md)] Repeat the steps to create three separate user flows as follows:
69-
70-
- A combined **Sign in and sign up** user flow, such as `susi`. This user flow also supports the **Forgot your password** experience.
71-
- A **Profile editing** user flow, such as `edit_profile`.
72-
- A **Password reset** user flow, such as `reset_password`.
73-
74-
Azure AD B2C prepends `B2C_1_` to the user flow name. For example, `susi` becomes `B2C_1_susi`.
68+
[!INCLUDE [active-directory-b2c-app-integration-add-user-flow](../../includes/active-directory-b2c-app-integration-add-user-flow.md)]
7569

7670
## Step 2: Register your web app and API
7771

0 commit comments

Comments
 (0)