Solution
Check whether the required attribute mappings are configured in IdP correctly, such as
firstname,
lastname,
email,
SAML_SUBJECT, or
Name_ID. Pay special attention to the Name_ID and
SAML_SUBJECT settings. Some IdP configurations use
Name_ID and others use
SAML_SUBJECT. We recommend that you configure all accounts so
Name_ID has the same value as
SAML_SUBJECT.
TC1 (Tracking Code 1), ……, TC10 (Tracking Code 10) are special attributes. If the tracking code is configured as required in the Administration at
Users >
Tracking Codes, they are required attribute mappings.
 Note |
If the input mode of a tracking code is dropdown menu, then the following applies: - Solution
If the tracking code is configured as Required, the attribute value must be one of the active values in the dropdown menu.
- Solution
If current tracking code is configured as not Required, the attribute value can be empty or one of the active values in dropdown menu.
|
Solution
For example, if IdP is ADFS 2 and you have not configured Tracking Codes (
SAML_SUBJECT is not required in ADFS 2), the following mapping is required:
LDAP Attribute |
Outgoing Claim Type |
E-Mail-Addresses |
Name_ID |
E-Mail-Addresses |
email |
Given-Name |
firstname |
Surname |
lastname |
 Note |
- Solution
We recommend that you map the Name_ID to the email address.
- Solution
The attribute name is case sensitive. Make sure the user's attribute value is not empty.
- Solution
We recommend that you do not configure your tracking codes as Required.
- Solution
We recommend that you do not configure the input mode of your tracking codes as dropdown menu.
Solution
Then make sure the user's attribute value is not empty.
|