Thank you very much for your help, current state is perfect! FYI: it looks like Jira indeed uses cn as Full Name, field was updated as I wanted as well.
Thanks a lot, Gleb. On 2020/05/28 18:09:37, sebb <seb...@gmail.com> wrote: > On Thu, 28 May 2020 at 17:09, Gleb <ifr...@apache.org> wrote: > > > > Hi Sebb, > > > > Thanks for your reply, I have a good understanding now! > > > > > In the meantime, your Common Name (cn) can be updated to just 'Gleb' if > > > you so wish. > > That would be great if it wouldn't trouble you much. > > OK, done > > Do you want sn to be set to Gleb as well? > I should be able to delete givenName at the same time. > > > And the last question, would Full Name in Jira be updated accordingly? > > (Does it use cn from LDAT as Full Name?) > > I don't know how JIRA gets the name; if it does not get fixed in due > course then please raise the issue with Infra. > > > Regards, > > Gleb. > > > > On 2020/05/28 11:26:09, sebb <seb...@gmail.com> wrote: > > > On Thu, 28 May 2020 at 05:16, Gleb Zernov <ifr...@apache.org> wrote: > > > > > > > > Hi! > > > > > > > > I have a question about this issue, > > > > > > > > From the body of the issue (WHIMSY-200): > > > > > it seems that if someone fills out "public name" and "full name", > > > > > then "public name" gets submitted as their full name > > > > is a desirable behavior. > > > > > > > > And at the end of discussion Sebb wrote: > > > > > I don't think we should override the public name if it is provided, > > > > > even if it is only a single word. > > > > > If there is no Public Name, then we have to assume that the Full name > > > > > intended to be public, and use that as above. > > > > Concluding: Public name is used first, only if it is not present Legal > > > > Name should be used. > > > > > > > > Currently, I have public name (Just my first name), and legal name (aka > > > > Full Name from ICLA) (same as LDAP name): which is my name + surname. > > > > In all services I can see my public name, but in Jira I see my legal > > > > name as Full Name. > > > > From my point of view, this shows data which was desired to be private > > > > (Public name should be used as Full name in Jira) > > > > > > LDAP has several standard attributes: > > > cn - Common Name, i.e. public name > > > givenName - aka Christian name (where that applies) > > > sn - surname > > > > > > AFAIK, it's not possible to set sn or givenName to the empty string, > > > nor to drop either attribute. > > > Normally the cn equals givenName 'space' sn > > > Thus a public name that consists of a single word causes issues. > > > I think that is why Infra created the account as they did. > > > (AFAICT, the account request from Whimsy only used the public name) > > > > > > This is really a question for Infra as to how to handle persons who > > > have a single word as their public name - or indeed their full legal > > > name (such people do exist) > > > > > > Whimsy can then be updated accordingly. > > > > > > In the meantime, your Common Name (cn) can be updated to just 'Gleb' > > > if you so wish. > > > > > > > > > > Thanks, > > > > Gleb. (Ifropc) > > > > > > > > On 2020/04/29 15:05:00, "Sebb (Jira)" <j...@apache.org> wrote: > > > > > > > > > > [ > > > > > https://issues.apache.org/jira/browse/WHIMSY-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > > > > > ] > > > > > > > > > > Sebb resolved WHIMSY-200. > > > > > ------------------------- > > > > > Resolution: Not A Problem > > > > > > > > > > > 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) > > > > > > > > >
