InVision creates new accounts via auto-provisioning when a new user attempts to sign in to an Enterprise account that has SAML enabled.
If the needed name attributes aren't sent correctly, this can result in names for auto-provisioned accounts being populated incorrectly.
Why are users' first and last names appearing as "Unnamed User”?
This is the logic InVision uses to identify names for SAML auto-provisioned accounts:
- Our implementation searches the response from the identity provider for the SAML attribute name
cn. If set, we use that attribute’s value for the user's name.
cnisn’t set, our implementation will apply a hard-coded string value of “Unnamed User”.
We only support the LDAP short-form name for the
cn attribute. The ADFS long-form URI equivalent for
cn is not supported.
How can we correct the user's names?
Individual users can update their account name by following the steps in this article: Updating the name on an InVision V7 account
Why doesn’t the cn attribute appear in the Azure AD Source Attribute dropdown list despite all the attributes being in my on-premise AD?
You may need to add the missing attribute by synchronizing it from your on-premises Active Directory (AD) to Azure Active Directory (Azure AD).
You can learn more in this article: Sync an attribute from your on-premises Active Directory to Azure AD for provisioning to an application