Last modified: 2014-09-02 17:16:47 UTC
When adding members to a project, the interface adds the user's input as the group member, rather than the CN value of the user's account. Though we ensure the value being added is valid, we aren't checking to ensure the case matches. The LDAP search for this attribute is case-insensitive, but we occasionally do case-sensitive checks in code, which leads to inconsistent behavior. When adding users or any other reference to other objects in LDAP, we should fetch the object from LDAP and use the attribute's value.
Seems this bug had been fixed quite a while back, but there is still an issue with usernames with all lowercase CNs. Retitling the bug.