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-sign-up-or-sign-in-federation.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -452,7 +452,7 @@ When the custom policy runs:
452
452
453
453
-**Orchestration Step 5** - This step runs if the user doesn't already exist (`objectId` doesn't exist), so the `AAD-UserWriteUsingAlternativeSecurityId` Technical Profile executes to write the social account into Microsoft Entra ID.
454
454
455
-
-**Orchestration Step 6** - Finally, step 6 assembles and returns the JWT token at the end of the policy’s execution.
455
+
-**Orchestration Step 6** - Finally, step 6 assembles and returns the JWT at the end of the policy’s execution.
456
456
457
457
## Step 5 - Update relying party output claims
458
458
@@ -466,7 +466,7 @@ In the `ContosoCustomPolicy.XML` file, locate the `RelyingParty` element, and th
We've added the identity provider (*identityProvider*) as an output claim, so it will be included in the JWT token returned to the relying party application.
469
+
We've added the identity provider (*identityProvider*) as an output claim, so it will be included in the JWT returned to the relying party application.
470
470
471
471
## Step 6 - Upload policy
472
472
@@ -485,7 +485,7 @@ If it's the first time running this policy (social account doesn't already exist
485
485
486
486
Enter or update **Display Name**, **Given Name** and the **Surname**, and then select **Continue** button.
487
487
488
-
After the policy finishes execution, you're redirected to https://jwt.ms, and you see a decoded JWT token. It looks similar to the following JWT token snippet:
488
+
After the policy finishes execution, you're redirected to https://jwt.ms, and you see a decoded JWT. It looks similar to the following JWT snippet:
489
489
490
490
```json
491
491
{
@@ -504,7 +504,7 @@ After the policy finishes execution, you're redirected to https://jwt.ms, and yo
504
504
}.[Signature]
505
505
```
506
506
507
-
Notice the identity provider, `"idp": "facebook.com"`, has been included in the JWT token.
507
+
Notice the identity provider, `"idp": "facebook.com"`, has been included in the JWT.
0 commit comments