> On Apr 4, 2017, at 4:38 PM, sebb <[email protected]> wrote:
> 
> There are some other issues with the sn field:


I don’t see any issues in your output. To improve LDAP tooling and 
functionality as we bring more LDAP-based services online, I fixed the 
ap-adduser script to add a valid givenName and sn to new accounts based on 
extracted values of $FULLNAME (cn.) This only affects accounts created after 
the script change. I’m in the process of verifying that there are no unexpected 
consequences, then will re-populate the remaining sn attributes for older 
accounts with their valid surname. Prior to my change, the script inserted the 
uid as the sn for unknown reasons.

I am aware of one case of a user with no apparent surname. The adduser changes 
will not affect old accounts. New accounts which arrive with a single name will 
be rejected and will need to be manually processed.

Users in LDAP with no valid surname will not have their sn field modified (i.e. 
they will remain $uid.)

-Chris

Attachment: signature.asc
Description: Message signed with OpenPGP

Reply via email to