Skip to content

Commit b29d186

Browse files
authored
Update secure-rest-api.md
1 parent f303e2b commit b29d186

File tree

1 file changed

+30
-1
lines changed

1 file changed

+30
-1
lines changed

articles/active-directory-b2c/secure-rest-api.md

Lines changed: 30 additions & 1 deletion
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: how-to
12-
ms.date: 10/25/2021
12+
ms.date: 04/05/2022
1313
ms.author: kengaderdus
1414
ms.subservice: B2C
1515
zone_pivot_groups: b2c-policy-type
@@ -397,6 +397,35 @@ After you add the above snippets, your technical profile should look like the fo
397397
</ClaimsProvider>
398398
```
399399

400+
### Call the REST technical profile
401+
402+
To call the `REST-GetProfile` technical profile, you first need to acquire an Azure AD access token using the `REST-AcquireAccessToken` technical profile. The following example shows how to call the `REST-GetProfile` technical profile from a [validation technical profile](validation-technical-profile.md):
403+
404+
```xml
405+
<ValidationTechnicalProfiles>
406+
<ValidationTechnicalProfile ReferenceId="REST-AcquireAccessToken" />
407+
<ValidationTechnicalProfile ReferenceId="REST-GetProfile" />
408+
</ValidationTechnicalProfiles>
409+
```
410+
411+
The following example shows how to call the `REST-GetProfile` technical profile from a [user journey](userjourneys.md), or a [sub journey](subjourneys.md):
412+
413+
```xml
414+
<OrchestrationSteps>
415+
<OrchestrationStep Order="2" Type="ClaimsExchange">
416+
<ClaimsExchanges>
417+
<ClaimsExchange Id="REST-AcquireAccessTokens" TechnicalProfileReferenceId="REST-AcquireAccessToken" />
418+
</ClaimsExchanges>
419+
</OrchestrationStep>
420+
421+
<OrchestrationStep Order="3" Type="ClaimsExchange">
422+
<ClaimsExchanges>
423+
<ClaimsExchange Id="REST-GetProfile" TechnicalProfileReferenceId="REST-GetProfile" />
424+
</ClaimsExchanges>
425+
</OrchestrationStep>
426+
</OrchestrationSteps>
427+
```
428+
400429
## Using a static OAuth2 bearer
401430

402431
### Add the OAuth2 bearer token policy key

0 commit comments

Comments
 (0)