Skip to content

Commit f721a41

Browse files
authored
Merge pull request #99781 from FrankHu-MSFT/patch-75
(AzureCXP) Provided Clarification
2 parents 0fa81ad + c771db5 commit f721a41

File tree

1 file changed

+8
-2
lines changed

1 file changed

+8
-2
lines changed

articles/active-directory/develop/active-directory-claims-mapping.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -411,7 +411,13 @@ Based on the method chosen, a set of inputs and outputs is expected. Define the
411411

412412
### Custom signing key
413413

414-
A custom signing key must be assigned to the service principal object for a claims mapping policy to take effect. This ensures acknowledgment that tokens have been modified by the creator of the claims mapping policy and protects applications from claims mapping policies created by malicious actors. Apps that have claims mapping enabled must check a special URI for their token signing keys by appending `appid={client_id}` to their [OpenID Connect metadata requests](v2-protocols-oidc.md#fetch-the-openid-connect-metadata-document).
414+
A custom signing key must be assigned to the service principal object for a claims mapping policy to take effect. This ensures acknowledgment that tokens have been modified by the creator of the claims mapping policy and protects applications from claims mapping policies created by malicious actors. In order to add a custom signing key, you can use the Azure Powershell cmdlet `new-azureadapplicationkeycredential` to create a symmetric key credential for your Application object. For more information on this Azure Powershell cmdlet click [here](https://docs.microsoft.com/powershell/module/Azuread/New-AzureADApplicationKeyCredential?view=azureadps-2.0).
415+
416+
Apps that have claims mapping enabled must validate their token signing keys by appending `appid={client_id}` to their [OpenID Connect metadata requests](v2-protocols-oidc.md#fetch-the-openid-connect-metadata-document). Below is the format of the OpenID Connect metadata document you should use:
417+
418+
```
419+
https://login.microsoftonline.com/{tenant}/v2.0/.well-known/openid-configuration?appid={client-id}
420+
```
415421

416422
### Cross-tenant scenarios
417423

@@ -516,4 +522,4 @@ In this example, you create a policy that emits a custom claim “JoinedData”
516522
517523
## See also
518524
519-
To learn how to customize claims issued in the SAML token through the Azure portal, see [How to: Customize claims issued in the SAML token for enterprise applications](active-directory-saml-claims-customization.md)
525+
To learn how to customize claims issued in the SAML token through the Azure portal, see [How to: Customize claims issued in the SAML token for enterprise applications](active-directory-saml-claims-customization.md)

0 commit comments

Comments
 (0)