[jira] [Commented] (WHIMSY-200) Public name from ICLA prioritized over Full Name
[ https://issues.apache.org/jira/browse/WHIMSY-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17118623#comment-17118623 ] Sebb commented on WHIMSY-200: - It turns out that givenName attribute can be deleted (but cannot be set to an empty string) So if a person's public name consists of a single word, a solution is to put: cn=public name sn=public name and delete givenName Whimsy already allows for a missing givenName in various places > 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 (v8.3.4#803005)
[jira] [Commented] (WHIMSY-200) Public name from ICLA prioritized over Full Name
[ 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)
[jira] [Commented] (WHIMSY-200) Public name from ICLA prioritized over Full Name
[ https://issues.apache.org/jira/browse/WHIMSY-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16577208#comment-16577208 ] Chris Thistlethwaite commented on WHIMSY-200: - Yes, the script does need to take into account single names. However, the issue isn't with publication but with LDAP needing first name and last name, which I thought was for legal reasons. My point being, if John Smith puts in a ICLA with public name Jimmy Shoe, then LDAP/etc would be created using that has his legal name instead of the more appropriate Full Name. I haven't combed through LDAP and ICLAs to find out if someone has a different Full Name than Public Name but both are First/Last names, so I have no clue if this particular case exists. > 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)
[jira] [Commented] (WHIMSY-200) Public name from ICLA prioritized over Full Name
[ https://issues.apache.org/jira/browse/WHIMSY-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16577199#comment-16577199 ] Sebb commented on WHIMSY-200: - I think the real problem is that the make-accounts.sh script does not handle single names. AIUI, the Full name is not intended for publication - that's why there is a Public Name. In any case, the full name may also be 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)
