This has come up a few times recently around how/when a users 'name' is updated on login via SAML specifically. On initial/first login, it is populated with contents of displayName, subsequent logins this is skipped. So if you onboard a lot of users for example, it will default the name field to their email address and leave it in this state until manual operations are performed.

Proposal:

On successful SAML assertion received:

* Check for attribute displayName in assertion

* Verify it is not null

* if != null, compare to current value in UI and update to new value if there is not a match.

This will reduce the amount of manual toil involved in writing scripts and editing user entries one at a time whenever displayName is not properly sent on the first user login for example. In this path, it will dump the users email address in the name field until manual intervention is taken.