...
After you have configured necessary core settings, you may need to adjust user attribute mappings. Attribute mappings can take multiple values in order of preference, separated by comma.
...
Field
...
Description
...
Default value
...
Example value from ADFS
...
Allow creating new users
...
Allow or deny creating new users. If you want to allow every user from ADFS to sign in to TrivoreID you need to check this. If not checked, only existing users can link their accounts with ADFS accounts
...
False (not checked)
...
N/A
...
Use NameID based linking
...
Use SAML NameID field for user’s ID. Please note that this option can not be used if ADFS uses transient NameID values as those differ for every login attempt.
...
True (checked)
...
Link ID
...
Permanent, non-secretive user identifier from ADFS. Use this option if NameID based linking is not suitable.
...
None
...
Username import policy
...
How to handle usernames in TrivoreID. This option exist in order to guarantee username uniqueness within namespace, which is a technical requirement. You can choose to import usernames from ADFS but preferred method is to generate them automatically using default settings.
...
Automatic namespace username policy (actual value depends on the configured policy in namespace settings)
...
N/A
...
Username
...
Attribute from ADFS that provides user’s username
...
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress
...
john.doe@client.example.com
...
Username prefix
...
Add username prefix with this literal value
...
None
...
N/A
...
Username suffix
...
Add username suffix with this literal value
...
None
...
N/A
...
Update username if it does match given settings
...
Update user’s username on every successful login if it does not match given settings. Very rarely needed feature
...
False (not checked)
...
N/A
...
Friendly name
...
Friendly name for user’s ADFS account that helps s/he identify it. Only useful if users are given access to manage their account linkings (add, edit, remove links)
...
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress
...
“John Doe”
...
First name
...
Attribute from ADFS that provides user’s first name
...
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname
...
“John“
...
Last name
...
Attribute from ADFS that provides user’s last name
...
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname
...
“Doe“
...
Full name
...
Attribute from ADFS that provides user’s full name, including both first and last name and possible middle names. This is only useful if separate attributes for first and last name are not available.
...
None
...
“John Doe“
...
...
Attribute from ADFS that provides user’s email
...
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress
...
“john.doe@example.com“
...
Email verified
...
Attribute from ADFS that provides user’s email verification information. Boolean attribute. May not be available
...
None
...
true
...
Mobile
...
Attribute from ADFS that provides user’s mobile number
...
None
...
+358401234567
...
Mobile verified
...
Attribute from ADFS that provides user’s mobile number verification information. Boolean attribute. May not be available
...
None
...
false
...
Locale / language
...
Attribute from ADFS that provides user’s language or localisation information
...
None
...
“en_US”
...
Photo URL
...
Attribute from ADFS that provides user’s photo URL.
...
ADFS uses common user attribute mappings documented at Common settings . Photo URL is not yet implemented. Some default values are available when creating new ADFS directory.