[
https://issues.apache.org/jira/browse/WHIMSY-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16577582#comment-16577582
]
Sebb commented on WHIMSY-200:
-----------------------------
AFAIK the LDAP fields cn, sn and givenName are not a legal requirement.
As they are public, they should only contain data that the ICLA signer expects
to be public.
So my view is that if the Public Name exists, then the script should only use
that to populate the LDAP fields cn, sn and givenName.
If there is only a single word, then use that for all 3 fields.
If there is no Public Name, then we have to assume that the Full name intended
to be public, and use that as above.
I don't think we should override the public name if it is provided, even if it
is only a single word.
> Public name from ICLA prioritized over Full Name
> ------------------------------------------------
>
> Key: WHIMSY-200
> URL: https://issues.apache.org/jira/browse/WHIMSY-200
> Project: Whimsy
> Issue Type: Improvement
> Components: General
> Reporter: Chris Thistlethwaite
> Priority: Minor
>
> Recently there have been a few new accounts that made their way into
> new-account-reqs.txt that only have a single name in the full name field.
> While there are instances where single names are appropriate, it seems that
> if someone fills out "public name" and "full name", then "public name" gets
> submitted as their full name. Single names cause the make-accounts.sh script
> to fail (as LDAP is looking for first and last name).
> The work around is someone from Infra (me) has to look up their ICLA and find
> their actual full name, edit new-account-reqs.txt, then re-run the account
> creation script.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
