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
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.
21
21
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:
23
23
24
-
1. Define a 'city' claim.
24
+
1. Define a "city" claim.
25
25
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.
27
27
1. Read the city claim from the user profile on each sign-in.
28
-
1. Return the city to your relying party application after signin or signup.
28
+
1. Return the city to your relying party application after sign-in or sign-up.
29
29
30
30
## Prerequisites
31
31
@@ -38,7 +38,7 @@ A claim provides a temporary storage of data during an Azure AD B2C policy execu
38
38
-**DisplayName** - A string that defines the user-facing label.
39
39
-[DataType](claimsschema.md#datatype) - The type of the claim.
40
40
-**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.
42
42
43
43
Open the extensions file of your policy. For example, <em>`SocialAndLocalAccounts/`**`TrustFrameworkExtensions.xml`**</em>.
44
44
@@ -67,7 +67,7 @@ The following technical profiles are [self-asserted](self-asserted-technical-pro
67
67
-**SelfAsserted-Social** - Federated account first-time user sign-in.
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:
71
71
72
72
```xml
73
73
<ClaimsProvider>
@@ -90,7 +90,8 @@ To collect the City claim during sign-up, it must be added as an output claim to
90
90
<ClaimsProvider>
91
91
```
92
92
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
+
94
95
```xml
95
96
<DisplayName>Self Asserted</DisplayName>
96
97
<TechnicalProfiles>
@@ -118,7 +119,7 @@ To collect the City claim after initial sign in with Social Account, it must be
118
119
119
120
## Read and write a claim
120
121
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.
122
123
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.
123
124
124
125
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.
228
229
229
230
## Next steps
230
231
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