Skip to content

Commit df35de1

Browse files
committed
address local accounts sign in review comments - DONW
1 parent b5c05b2 commit df35de1

File tree

1 file changed

+4
-9
lines changed

1 file changed

+4
-9
lines changed

articles/active-directory-b2c/custom-policies-series-sign-up-or-sign-in.md

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -214,15 +214,10 @@ In the `ContosoCustomPolicy.XML` file, locate the *ContentDefinitions* section,
214214
</ContentDefinition>
215215
<!--</ContentDefinitions>-->
216216
```
217-
We've configured a content definition for our self-asserted technical profile, `SignupOrSigninContentDefinition`. We can specify it in the technical profile using the metadata element or specify it when we reference the technical profile in the orchestration steps. Previously, we learnt how to specify a content definition directly in the self-asserted technical profile, so in this article, we'll learn how to specify it when we reference the technical profile in the orchestration steps, [step 5](#step-5---update-the-user-journey-orchestration-steps).
217+
We've configured a content definition for our self-asserted technical profile, `SignupOrSigninContentDefinition`. We can specify it in the technical profile using the metadata element or specify it when we reference the technical profile in the orchestration steps. Previously, we learnt how to specify a content definition directly in the self-asserted technical profile, so in this article, we'll learn how to specify it when we reference the technical profile in the orchestration steps, [step 3](#step-3---update-the-user-journey-orchestration-steps).
218218

219-
## Step 3 - Update the ClaimGenerator Technical Profile
220219

221-
222-
## Step 4 - Update AAD-UserRead Technical Profile
223-
224-
225-
## Step 5 - Update the User Journey Orchestration Steps
220+
## Step 3 - Update the User Journey Orchestration Steps
226221

227222
In the `ContosoCustomPolicy.XML` file, locate the *HelloWorldJourney* user journey and replace all its orchestration steps with the following code:
228223

@@ -314,11 +309,11 @@ When the custom policy runs:
314309

315310
- **Orchestration Step 7** - Finally, step 8 assembles and returns the JWT token at the end of the policy’s execution
316311

317-
## Step 6 - Upload policy
312+
## Step 4 - Upload policy
318313

319314
Follow the steps in [Upload custom policy file](custom-policies-series-hello-world.md#step-3---upload-custom-policy-file) to upload your policy file. If you're uploading a file with same name as the one already in the portal, make sure you select **Overwrite the custom policy if it already exists**.
320315

321-
## Step 7 - Test policy
316+
## Step 5 - Test policy
322317

323318
Follow the steps in [Test the custom policy](custom-policies-series-validate-user-input.md#step-6---test-the-custom-policy) to test your custom policy. Once the policy runs, you'll see an interface similar to the screenshot below:
324319

0 commit comments

Comments
 (0)