How to: Customize claims issued in the SAML token for enterprise applications
Today Azure Active Directory (Azure AD) supports single sign on with most enterprise applications, including both applications pre-integrated in the Azure AD app gallery as well as custom applications. When a user authenticates to an application through Azure AD using the SAML 2.0 protocol, Azure AD sends a token to the application (via an HTTP POST). And then, the application validates and uses the token to log the user in instead of prompting for a username and password. These SAML tokens contain pieces of information about the user known as "claims".
A claim is information that an identity provider states about a user inside the token they issue for that user. In SAML token, this data is typically contained in the SAML Attribute Statement. The user’s unique ID is typically represented in the SAML Subject also called as Name Identifier.
By default, Azure AD issues a SAML token to your application that contains a NameIdentifier claim, with a value of the user’s username (AKA user principal name) in Azure AD. this value can uniquely identify the user. The SAML token also contains additional claims containing the user’s email address, first name, and last name.
To view or edit the claims issued in the SAML token to the application, open the application in Azure portal. Then select the View and edit all other user attributes checkbox in the User Attributes section of the application.
There are two possible reasons why you might need to edit the claims issued in the SAML token:
- The application has been written to require a different set of claim URIs or claim values.
- The application has been deployed in a way that requires the NameIdentifier claim to be something other than the username (AKA user principal name) stored in Azure AD.
You can edit any of the default claim values. Select the claim row in the SAML token attributes table. This opens the Edit Attribute section and then you can edit claim name, value, and namespace associated with the claim.
You can also remove claims (other than NameIdentifier) using the context menu, which opens by clicking on the ... icon. You can also add new claims using the Add attribute button.
Editing the NameIdentifier claim
To solve the problem where the application has been deployed using a different username, select on the User Identifier drop down in the User Attributes section. This action provides a dialog with several different options:
Select the desired source for the
NameIdentifier (or NameID) claim. You can select from the following options.
|The email address of the user|
|userprincipalName||The user principal name (UPN) of the user|
|onpremisessamaccount||SAM account name that has been synced from on-premises Azure AD|
|objectID||The objectID of the user in Azure AD|
|EmployeeID||The EmployeeID of the user|
|Directory extensions||Directory extensions synced from on-premises Active Directory using Azure AD Connect Sync|
|Extension Attributes 1-15||On-premises extension attributes used to extend the Azure AD schema|
You can also use the special claims transformations functions.
|ExtractMailPrefix()||Removes the domain suffix from either the email address, SAM account name, or the user principal name. This extracts only the first part of the user name being passed through (for example, "joe_smith" instead of email@example.com).|
|join()||Joins an attribute with a verified domain. If the selected user identifier value has a domain, it will extract the username to append the selected verified domain. For example, if you select the email (firstname.lastname@example.org) as the user identifier value and select contoso.onmicrosoft.com as the verified domain, this will result in email@example.com.|
|ToLower()||Converts the characters of the selected attribute into lowercase characters.|
|ToUpper()||Converts the characters of the selected attribute into uppercase characters.|
When adding a claim, you can specify the attribute name (which doesn’t strictly need to follow a URI pattern as per the SAML spec). Set the value to any user attribute that is stored in the directory or use a constant value as an static entry for all users in your organization.
For example, you need to send the department that the user belongs to in their organization as a claim (such as, Sales). Enter the claim name as expected by the application, and then select user.department as the value.
If for a given user there is no value stored for a selected attribute, then that claim is not being issued in the token.
The user.onpremisesecurityidentifier and user.onpremisesamaccountname are only supported when synchronizing user data from on-premises Active Directory using the Azure AD Connect tool.
There are some restricted claims in SAML. If you add these claims, then Azure AD will not send these claims. Following are the SAML restricted claim set:
| Claim type (URI) | | ------------------- | | http://schemas.microsoft.com/ws/2008/06/identity/claims/expiration | | http://schemas.microsoft.com/ws/2008/06/identity/claims/expired | | http://schemas.microsoft.com/identity/claims/accesstoken | | http://schemas.microsoft.com/identity/claims/openid2_id | | http://schemas.microsoft.com/identity/claims/identityprovider | | http://schemas.microsoft.com/identity/claims/objectidentifier | | http://schemas.microsoft.com/identity/claims/puid | | http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier[MR1] | | http://schemas.microsoft.com/identity/claims/tenantid | | http://schemas.microsoft.com/ws/2008/06/identity/claims/authenticationinstant | | http://schemas.microsoft.com/ws/2008/06/identity/claims/authenticationmethod | | http://schemas.microsoft.com/accesscontrolservice/2010/07/claims/identityprovider | | http://schemas.microsoft.com/ws/2008/06/identity/claims/groups | | http://schemas.microsoft.com/claims/groups.link | | http://schemas.microsoft.com/ws/2008/06/identity/claims/role | | http://schemas.microsoft.com/ws/2008/06/identity/claims/wids | | http://schemas.microsoft.com/2014/09/devicecontext/claims/iscompliant | | http://schemas.microsoft.com/2014/02/devicecontext/claims/isknown | | http://schemas.microsoft.com/2012/01/devicecontext/claims/ismanaged | | http://schemas.microsoft.com/2014/03/psso | | http://schemas.microsoft.com/claims/authnmethodsreferences | | http://schemas.xmlsoap.org/ws/2009/09/identity/claims/actor | | http://schemas.microsoft.com/ws/2008/06/identity/claims/samlissuername | | http://schemas.microsoft.com/ws/2008/06/identity/claims/confirmationkey | | http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsaccountname | | http://schemas.microsoft.com/ws/2008/06/identity/claims/primarygroupsid | | http://schemas.microsoft.com/ws/2008/06/identity/claims/primarysid | | http://schemas.xmlsoap.org/ws/2005/05/identity/claims/authorizationdecision | | http://schemas.xmlsoap.org/ws/2005/05/identity/claims/authentication | | http://schemas.xmlsoap.org/ws/2005/05/identity/claims/sid | | http://schemas.microsoft.com/ws/2008/06/identity/claims/denyonlyprimarygroupsid | | http://schemas.microsoft.com/ws/2008/06/identity/claims/denyonlyprimarysid | | http://schemas.xmlsoap.org/ws/2005/05/identity/claims/denyonlysid | | http://schemas.microsoft.com/ws/2008/06/identity/claims/denyonlywindowsdevicegroup | | http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsdeviceclaim | | http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsdevicegroup | | http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsfqbnversion | | http://schemas.microsoft.com/ws/2008/06/identity/claims/windowssubauthority | | http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsuserclaim | | http://schemas.xmlsoap.org/ws/2005/05/identity/claims/x500distinguishedname | | http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn | | http://schemas.microsoft.com/ws/2008/06/identity/claims/groupsid | | http://schemas.xmlsoap.org/ws/2005/05/identity/claims/spn | | http://schemas.microsoft.com/ws/2008/06/identity/claims/ispersistent | | http://schemas.xmlsoap.org/ws/2005/05/identity/claims/privatepersonalidentifier | | http://schemas.microsoft.com/identity/claims/scope |
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.