You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whimsical.apache.org by "Sebb (Jira)" <ji...@apache.org> on 2020/05/28 12:43:00 UTC

[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)