Skip to content

Commit cb3467f

Browse files
authored
Merge pull request #122135 from tusharka1/patch-6
Update self-asserted-technical-profile.md
2 parents e855120 + 02570d9 commit cb3467f

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

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

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -176,7 +176,8 @@ The following example demonstrates the use of a self-asserted technical profile
176176
<UseTechnicalProfileForSessionManagement ReferenceId="SM-AAD" />
177177
</TechnicalProfile>
178178
```
179-
179+
> [!NOTE]
180+
> When you collect the password claim value in the self-asserted technical profile, that value is only available within the same technical profile or within a validation technical profiles that are referenced by that same self-asserted technical profile. When execution of that self-asserted technical profile completes, and moves to another technical profile, the password's value is lost. Consequently, password claim can only be stored in the orchestration step in which it is collected.
180181
### Output claims sign-up or sign-in page
181182

182183
In a combined sign-up and sign-in page, note the following when using a content definition [DataUri](contentdefinitions.md#datauri) element that specifies a `unifiedssp` or `unifiedssd` page type:

0 commit comments

Comments
 (0)