[
https://issues.apache.org/jira/browse/WHIMSY-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14717852#comment-14717852
]
Craig L Russell commented on WHIMSY-11:
---------------------------------------
The iclas.txt full name (what you call legal name) should not affect filtering.
We are only interested in matching the iclas.txt public name with the LDAP cn.
If there is a mismatch, both iclas.txt full name and iclas.txt public name
should be printed along with LDAP cn.
As far as I care, there is nothing wrong with multiple folks having the same
iclas.txt public name. Confusing, but not an issue. But the full name (as
originally recorded on the ICLA, going back to 199?) must be unique, and tools
already guarantee that.
Once I am certain that the LDAP cn names are either identical to the icla.txt
public name or the LDAP cn has been changed by the user, I can manually
synchronize the icla.txt public name. I'm still not clear on how the LDAP cn is
changed. [I changed my name via chfn and verified that the change took place on
minotaur by doing chfn and also getent passwd.] But LDAP cn is still the old
value according to id.apache.org and according to public_names script.
> add both icla.txt names to public_names script
> ----------------------------------------------
>
> Key: WHIMSY-11
> URL: https://issues.apache.org/jira/browse/WHIMSY-11
> Project: Whimsy
> Issue Type: Improvement
> Reporter: Craig L Russell
> Priority: Minor
>
> public_names script could be more useful if both icla.txt names were shown:
> legal name, public name, ldap full name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
