Previously Alberto Lopes wrote: > So, what I think it should be the solution is to make the "username > matching" case insensitive, when Plone tries to decide whether the username > matches against the other. Hopefully, maybe it is just a matter of changing > somewhere something like "if username = currentUsername" by "if > upper_case(username) = upper_case(currentUsername)" > > I know this will break Plone in terms of not allowing the occurrence of > Plone users with same characters but different cases, but that does not > bothers me for two reasons: first, we are only using LDAP users and second, > I think it would be too messy anyway to allow logins JohnDoe and johndoe as > different users. > > Can anyone give me a hint on which .py to change, and where?
Many, many, many python files in lots of places. You're better of always lowercasing the userid on PAS extraction. Wichert. -- Wichert Akkerman <[EMAIL PROTECTED]> It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
