You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a user sets name, profiles only updates cn, however cn is not the only reference to a user's name, so this leaves potentially outdated or dead names in the givenName, initals, sn, and gecos fields, or otherwise allow a user to see and update those fields.
The text was updated successfully, but these errors were encountered:
The right course of action here, imo, is to break first and last name (possibly also add a nickname option) into different fields and then compute the correct values for each of the LDAP attributes on submission.
That saves people from having to manually edit each field, but also gives them the flexibility to set their name to whatever they want.
The right course of action here, imo, is to break first and last name (possibly also add a nickname option) into different fields and then compute the correct values for each of the LDAP attributes on submission.
That saves people from having to manually edit each field, but also gives them the flexibility to set their name to whatever they want.
When a user sets name, profiles only updates
cn
, howevercn
is not the only reference to a user's name, so this leaves potentially outdated or dead names in thegivenName
,initals
,sn
, andgecos
fields, or otherwise allow a user to see and update those fields.The text was updated successfully, but these errors were encountered: