The following instructions refer to third-party software and are included for illustration purposes only. Detailed instructions on how to configure AD FS and use the Add Relying Party Trust Wizard are available from Microsoft.
The Hyland Identity Provider (IdP) does not support encrypted claims or tokens with AD FS. Configuring a Token Encryption Certificate on the Relying Party Trust for use with the Hyland IdP server is not supported.
- Access the Add Relying Party Trust Wizard on the AD FS server.
- Under data source configuration, select the option to enter data about the relying party manually.
- Name the trust with a specific name that clearly identifies what resource this trust is for.
- When prompted to choose an AD FS profile, select the latest available profile for your version of AD FS.
- Under URL configuration, select the option to enable support for the WS-Federation Passive protocol.
Enter the URL of the Hyland IdP server as the relying party WS-Federation Passive protocol URL. For example, if the Hyland IdP server is installed as the identityprovider application under the https://server-018.mydomain.net domain, then the passive protocol URL is:
Under identifiers configuration, add the same URL you configured as the relying party WS-Federation Passive protocol URL, but include the tenant in the path. For example, if the passive protocol URL is https://server-018.mydomain.net/identityprovider and the tenant is Company1, then the identifier URL is:
This value is case sensitive and must match exactly the URL value of the Realm configured for the provider on the Hyland IdP server.
Permit all users to access this relying party for the issuance authorization rules.
AD FS 3.0 includes multi-factor authentication. Multi-factor authentication is supported by OnBase and there are currently no additional configuration steps needed to integrate multi-factor authentication with OnBase.
After configuring the relying party you must add a claim rule.
All listed claims must be configured with a claim rule in order to enable proper authentication.
- Select Send LDAP Attributes as Claims rule template for the rule type.
- Give the claim rule a descriptive name.
- Select Active Directory as the attribute store.
Use the following table to map the LDAP attributes to outgoing claim types:
Outgoing Claim Type
Token-Groups - Unqualified Names