Skip to content

Commit 244867c

Browse files
authored
Update custom-policy-configure-user-input.md
Merging @msmimart changes
1 parent b020371 commit 244867c

File tree

1 file changed

+13
-12
lines changed

1 file changed

+13
-12
lines changed

articles/active-directory-b2c/custom-policy-configure-user-input.md

Lines changed: 13 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -9,23 +9,23 @@ manager: celestedg
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: conceptual
12-
ms.date: 03/09/2020
12+
ms.date: 03/10/2020
1313
ms.author: mimart
1414
ms.subservice: B2C
1515
---
1616
# Add claims and customize user input using custom policies in Azure Active Directory B2C
1717

1818
[!INCLUDE [active-directory-b2c-advanced-audience-warning](../../includes/active-directory-b2c-advanced-audience-warning.md)]
1919

20-
In this article, you will collect a new attribute during your sign-up journey in Azure Active Directory B2C (Azure AD B2C). You will obtain the users' City, configure it as a dropdown, and define whether it's required to be provided.
20+
In this article, you collect a new attribute during your sign-up journey in Azure Active Directory B2C (Azure AD B2C). You'll obtain the users' city, configure it as a drop-down, and define whether it's required to be provided.
2121

22-
Gathering initial data from your users is achieved using the sign-up or sign-in user journey. Additional claims can be gathered later by using a profile edit user journey. Anytime Azure AD B2C gathers information directly from the user interactively, the Identity Experience Framework uses its [self-asserted technical profile](self-asserted-technical-profile.md). In this sample, you:
22+
You can gather initial data from your users by using the sign-up or sign-in user journey. Additional claims can be gathered later by using a profile edit user journey. Anytime Azure AD B2C gathers information directly from the user interactively, the Identity Experience Framework uses its [self-asserted technical profile](self-asserted-technical-profile.md). In this sample, you:
2323

24-
1. Define a 'city' claim.
24+
1. Define a "city" claim.
2525
1. Ask the user for their city.
26-
1. Persist the city to the user profile in Azure AD B2C directory.
26+
1. Persist the city to the user profile in the Azure AD B2C directory.
2727
1. Read the city claim from the user profile on each sign-in.
28-
1. Return the city to your relying party application after sign in or sign up.
28+
1. Return the city to your relying party application after sign-in or sign-up.
2929

3030
## Prerequisites
3131

@@ -38,7 +38,7 @@ A claim provides a temporary storage of data during an Azure AD B2C policy execu
3838
- **DisplayName** - A string that defines the user-facing label.
3939
- [DataType](claimsschema.md#datatype) - The type of the claim.
4040
- **UserHelpText** - Helps the user understand what is required.
41-
- [UserInputType](claimsschema.md#userinputtype) - The type of input control, such as textbox, radio selection, drop-down list, or multiple selections.
41+
- [UserInputType](claimsschema.md#userinputtype) - The type of input control, such as text box, radio selection, drop-down list, or multiple selections.
4242

4343
Open the extensions file of your policy. For example, <em>`SocialAndLocalAccounts/`**`TrustFrameworkExtensions.xml`**</em>.
4444

@@ -67,7 +67,7 @@ The following technical profiles are [self-asserted](self-asserted-technical-pro
6767
- **SelfAsserted-Social** - Federated account first-time user sign-in.
6868
- **SelfAsserted-ProfileUpdate** - Edit profile flow.
6969

70-
To collect the City claim during sign-up, it must be added as an output claim to the `LocalAccountSignUpWithLogonEmail` technical profile. Override this technical profile in the extension file. Specify the entire list of output claims to control the order the claims are presented on the screen. Find the **ClaimsProviders** element. Add a new ClaimsProviders as follows:
70+
To collect the city claim during sign-up, it must be added as an output claim to the `LocalAccountSignUpWithLogonEmail` technical profile. Override this technical profile in the extension file. Specify the entire list of output claims to control the order the claims are presented on the screen. Find the **ClaimsProviders** element. Add a new ClaimsProviders as follows:
7171

7272
```xml
7373
<ClaimsProvider>
@@ -90,7 +90,8 @@ To collect the City claim during sign-up, it must be added as an output claim to
9090
<ClaimsProvider>
9191
```
9292

93-
To collect the City claim after initial sign in with Social Account, it must be added as an output claim to the `SelfAsserted-Social` technical profile. For Social Account users to be able to edit their profile data later, add the output claim to the `SelfAsserted-ProfileUpdate` technical profile. Override these technical profiles in the extension file. Specify the entire list of the output claims to control the order the claims are presented on the screen. Find the **ClaimsProviders** element. Add a new ClaimsProviders as follows:
93+
To collect the city claim after initial sign-in with a social account, it must be added as an output claim to the `SelfAsserted-Social` technical profile. For social account users to be able to edit their profile data later, add the output claim to the `SelfAsserted-ProfileUpdate` technical profile. Override these technical profiles in the extension file. Specify the entire list of the output claims to control the order the claims are presented on the screen. Find the **ClaimsProviders** element. Add a new ClaimsProviders as follows:
94+
9495
```xml
9596
<DisplayName>Self Asserted</DisplayName>
9697
<TechnicalProfiles>
@@ -118,7 +119,7 @@ To collect the City claim after initial sign in with Social Account, it must be
118119

119120
## Read and write a claim
120121

121-
The following technical profiles are [Active Directory technical profile](active-directory-technical-profile.md), which read and write data to the Azure Active Directory.
122+
The following technical profiles are [Active Directory technical profiles](active-directory-technical-profile.md), which read and write data to Azure Active Directory.
122123
Use `PersistedClaims` to write data to the user profile and `OutputClaims` to read data from the user profile within the respective Active Directory technical profiles.
123124

124125
Find the **ClaimsProviders** element. Add a new ClaimsProviders as follows:
@@ -228,5 +229,5 @@ The token sent back to your application includes the `city` claim.
228229

229230
## Next steps
230231

231-
- Learn more about [ClaimsSchema](claimsschema.md) element in the IEF reference.
232-
- Learn how to [Use custom attributes in a custom profile edit policy](custom-policy-custom-attributes.md).
232+
- Learn more about the [ClaimsSchema](claimsschema.md) element in the IEF reference.
233+
- Learn how to [use custom attributes in a custom profile edit policy](custom-policy-custom-attributes.md).

0 commit comments

Comments
 (0)