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: articles/active-directory-b2c/custom-policies-series-call-rest-api.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ In this article, you'll learn how to:
31
31
32
32
## Scenario overview
33
33
34
-
In [Create branching in user journey by using Azure AD B2C custom policies](custom-policies-series-branch-user-journey.md), users who select *Personal Account* need to provide a valid invitation access code to proceed. We use a static access code, but real world apps don't work this way. If the service that issues the access codes is external to your custom policy, you must make a call to that service, and pass the access code input by the user for validation. If the access code is valid, the service returns an HTTP 200 (OK) response, and Azure AD B2C issues JWT token. Otherwise, the service returns an HTTP 409 (Conflict) response, and the use must re-enter an access code.
34
+
In [Create branching in user journey by using Azure AD B2C custom policies](custom-policies-series-branch-user-journey.md), users who select *Personal Account* need to provide a valid invitation access code to proceed. We use a static access code, but real world apps don't work this way. If the service that issues the access codes is external to your custom policy, you must make a call to that service, and pass the access code input by the user for validation. If the access code is valid, the service returns an HTTP 200 (OK) response, and Azure AD B2C issues JWT token. Otherwise, the service returns an HTTP 409 (Conflict) response, and the user must re-enter an access code.
35
35
36
36
:::image type="content" source="media/custom-policies-series-call-rest-api/screenshot-of-call-rest-api-call.png" alt-text="A flowchart of calling a R E S T A P I.":::
37
37
@@ -88,7 +88,7 @@ You need to deploy an app, which will serve as your external app. Your custom po
88
88
"code":"errorCode",
89
89
"requestId":"requestId",
90
90
"userMessage":"The access code you entered is incorrect. Please try again.",
91
-
"developerMessage":`The The provided code ${req.body.accessCode} does not match the expected code for user.`,
91
+
"developerMessage":`The provided code ${req.body.accessCode} does not match the expected code for user.`,
We've added a [UserJourney](userjourneys.md). The user journey specifies the business logic the end user goes through as Azure AD B2C processes a request. This user journey has only one step that issues a JTW token with the claims that you'll define in the next step.
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/index.yml
+2-2
Original file line number
Diff line number
Diff line change
@@ -7,8 +7,8 @@ summary: >
7
7
brand: azure
8
8
9
9
metadata:
10
-
title: Azure Active Directory B2C documentation# Required; page title displayed in search results. Include the brand. < 60 chars.
11
-
description: Learn how to use Azure Active Directory B2C to customize and control how customers sign up, sign in, and manage their profiles when using your applications.# Required; article description that is displayed in search results. < 160 chars.
10
+
title: Azure Active Directory B2C documentation
11
+
description: Learn how to use Azure Active Directory B2C to customize and control how customers sign up, sign in, and manage their profiles when using your applications.
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/quickstart-web-app-dotnet.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ In this quickstart, you use an ASP.NET application to sign in using a social ide
39
39
## Run the application in Visual Studio
40
40
41
41
1. In the sample application project folder, open the **B2C-WebAPI-DotNet.sln** solution in Visual Studio.
42
-
1. For this quickstart, you run both the **TaskWebApp** and **TaskService** projects at the same time. Right-click the **B2C-WebAPI-DotNet** solution in Solution Explorer, and then select **Set StartUp Projects**.
42
+
1. For this quickstart, you run both the **TaskWebApp** and **TaskService** projects at the same time. Right-click the **B2C-WebAPI-DotNet** solution in Solution Explorer, and then select **Configure StartUp Projects...**.
43
43
1. Select **Multiple startup projects** and change the **Action** for both projects to **Start**.
44
44
1. Select **OK**.
45
45
1. Press **F5** to debug both applications. Each application opens in its own browser tab:
The final step is to check that the flow works properly. To check this, try logging in with one of your AD users in Active Directory. We tried with a user called *ADUser*. If the configuration is correct, you will get the following result:
@@ -86,13 +86,13 @@ You can test the feature by triggering disable / deletion events by setting the
86
86
87
87
Let the provisioning job run (20 – 40 mins) and navigate back to the provisioning page. You'll see the provisioning job in quarantine and can choose to allow the deletions or review the provisioning logs to understand why the deletions occurred.
88
88
89
-
## Common de-provisioning scenarios to test
89
+
## Common deprovisioning scenarios to test
90
90
- Delete a user / put them into the recycle bin.
91
91
- Block sign in for a user.
92
92
- Unassign a user or group from the application (or configuration).
93
93
- Remove a user from a group that's providing them access to the application (or configuration).
94
94
95
-
To learn more about de-provisioning scenarios, see [How Application Provisioning Works](how-provisioning-works.md#de-provisioning).
95
+
To learn more about deprovisioning scenarios, see [How Application Provisioning Works](how-provisioning-works.md#deprovisioning).
0 commit comments