AD FS configuration
This how-to guide describes how to configure Unit4 Identity Services with ADFS.
- Administrative access to AD FS
- U4IDS authority address (over the remainder of this document we use value of
https://<u4ids basepath>/identityas the address of U4IDS installation's identity endpoint)
- Decision ON which claim would be used to uniquely identify the user in the organisation (see "Unique claims" below.)
- access to U4IDS in order to create tenant
The list of official IDS environments can be found here
Add a new Relying Party Trust
Select Claims aware relying party.
You need to enable the WS-Federation Passive protocol.
Manually add the values of address of U4IDS installation.
Configure claims that would be sent to U4IDS
Configure mapping of claims and other AD values sent to U4IDS.
IMPORTANT NOTICE: Make sure you map to claim 'Name ID' using a unique claim (here User-Principal-Name as a first option or objectGUID on the next screen shot, could also be E-Mail-Addresses). Without a unique user's value mapped to this claim the configuration of U4IDS with AD FS will not work.
Configure tenant in U4IDS
See Identity providers in tenants for more information.
| AD claim | Value to be used as unit4IdClaimType | Description | |---|---|---|---|---| | Name ID | nameidentifier or sub | Can be mapped to email address, UPN or objectGUID (as on the screen shots above). | | User-Principal-Name | upn | Depends on the configuration in AD. Can be mapped to email address. | | Email Addresses | email | Email address of a user. | | Primary Security Identifier (SID) | primarysid | e.g. S-1-5-21-918238372-1567831296-1769025822-29564 | | Windows account name | winaccountname | e.g. MyDomain\MyAccountName |
One of the claims that gets sent from AD FS is sub claim. It is used as a default fallback to be placed in unit4_id in case the claim you have chosen in the tenant configuration is not working (for example was not delivered, or you chose a non-existing claim or made a typo).
When objectGUID is mapped to the Name ID claim then its value is the base64-encoded value of the GUID that uniquely identifies the given user object in the AD store. In this case the value of objectGUID being
4d6861cf-526a-4dee-b2f0-3e4a5cb3e36c is transferred as
z2FoTWpS7k2y8D5KXLPjbA== (encoded form).
In case you need to receive the decoded value of this claim, follow this sample article on how to create your own attribute store in AD FS that would decode the claim before sending: