Here you can find instructions how to configure TrivoreID authentication to work with Azure AD. Configuring Azure AD itself is out scope of this document (only general requirements provided here).
This configuration enables for using credentials at makes it possible to use existing Azure AD instance to be used to sign-in to Trivore ID.
Configure Trivore ID
...
Field | Description |
|---|---|
Name | Any name you want to choose for this directory. |
Tenant | Azure AD instance unique identifier. |
Domain hint | Login domain hint. This field can be used to auto redirect user to on-premises ADFS if all users belong to a domain that should use it. refer to Microsoft documentation for more information. |
Client ID | OpenID Connect |
Client secret | OpenID Connect |
Scope | Adjust scope if needed. Scope defines what user information/attributes can be imported. Refer to Microsoft documentation for more information about appropriate Scope values. |
Attribute names to fetch from GraphAPI (extra values) | Fetch these user attributes from GraphAPI on sign-in. This field is needed only on special cases where you have defined dot-separated mapping like “onPremisesExtensionAttributes.extensionAttribute12“. In this case, field value should contain “onPremisesExtensionAttributes“. |
User information
After you have configured necessary core settings, you may need to adjust user attribute mappings. Default mappings are suitable for most cases.
...
Azure AD uses common user attribute mappings documented at Common settings . Photo URL is not yet implemented.user directory settings.
Field | Description | Default value |
|---|---|---|
Import user’s photo | Import user’s profile photo from Azure AD. | True (checked) |