Skip to content

Commit 6ce8532

Browse files
authored
Merge pull request #107775 from yoelhor/patch-3
Update self-asserted-technical-profile.md
2 parents 50b4f4a + 17d8162 commit 6ce8532

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

articles/active-directory-b2c/self-asserted-technical-profile.md

Lines changed: 7 additions & 5 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: reference
12-
ms.date: 02/17/2020
12+
ms.date: 03/16/2020
1313
ms.author: mimart
1414
ms.subservice: B2C
1515
---
@@ -64,8 +64,8 @@ In the display claims collection, you can include a reference to a [DisplayContr
6464

6565
The following example `TechnicalProfile` illustrates the use of display claims with display controls.
6666

67-
* The first display claim makes a reference to the `emailVerificationControl` display control which collects and verifies the email address.
68-
* The fifth display claim makes a reference to the `phoneVerificationControl` display control which collects and verifies a phone number.
67+
* The first display claim makes a reference to the `emailVerificationControl` display control, which collects and verifies the email address.
68+
* The fifth display claim makes a reference to the `phoneVerificationControl` display control, which collects and verifies a phone number.
6969
* The other display claims are ClaimTypes to be collected from the user.
7070

7171
```XML
@@ -117,6 +117,8 @@ The `age` claim in the base policy is no longer presented on the screen to the u
117117

118118
The **OutputClaims** element contains a list of claims to be returned to the next orchestration step. The **DefaultValue** attribute takes effect only if the claim has never been set. If it was set in a previous orchestration step, the default value does not take effect even if the user leaves the value empty. To force the use of a default value, set the **AlwaysUseDefaultValue** attribute to `true`.
119119

120+
For security reasons, a password claim value (`UserInputType` set to `Password`) is available only to the self-asserted technical profile's validation technical profiles. You cannot use password claim in the next orchestration steps.
121+
120122
> [!NOTE]
121123
> In previous versions of the Identity Experience Framework (IEF), output claims were used to collect data from the user. To collect data from the user, use a **DisplayClaims** collection instead.
122124
@@ -126,7 +128,7 @@ The **OutputClaimsTransformations** element may contain a collection of **Output
126128

127129
In a self-asserted technical profile, the output claims collection returns the claims to the next orchestration step.
128130

129-
You should use output claims when:
131+
Use output claims when:
130132

131133
- **Claims are output by output claims transformation**.
132134
- **Setting a default value in an output claim** without collecting data from the user or returning the data from the validation technical profile. The `LocalAccountSignUpWithLogonEmail` self-asserted technical profile sets the **executed-SelfAsserted-Input** claim to `true`.
@@ -190,7 +192,7 @@ You can also call a REST API technical profile with your business logic, overwri
190192
| AllowGenerationOfClaimsWithNullValues| No| Allow to generate a claim with null value. For example, in a case user doesn't select a checkbox.|
191193
| ContentDefinitionReferenceId | Yes | The identifier of the [content definition](contentdefinitions.md) associated with this technical profile. |
192194
| EnforceEmailVerification | No | For sign-up or profile edit, enforces email verification. Possible values: `true` (default), or `false`. |
193-
| setting.retryLimit | No | Controls the number of times a user can try to provide the data that is checked against a validation technical profile . For example, a user tries to sign-up with an account that already exists and keeps trying until the limit reached.
195+
| setting.retryLimit | No | Controls the number of times a user can try to provide the data that is checked against a validation technical profile. For example, a user tries to sign-up with an account that already exists and keeps trying until the limit reached.
194196
| SignUpTarget <sup>1</sup>| No | The signup target exchange identifier. When the user clicks the sign-up button, Azure AD B2C executes the specified exchange identifier. |
195197
| setting.showCancelButton | No | Displays the cancel button. Possible values: `true` (default), or `false` |
196198
| setting.showContinueButton | No | Displays the continue button. Possible values: `true` (default), or `false` |

0 commit comments

Comments
 (0)