Hide Forgot
This bug is created as a clone of upstream ticket: https://fedorahosted.org/sssd/ticket/1123 When using ldap authentication and with case_sensitive set to FALSE you ARE able to log in with lower case usernames but in the background the username is still upper case. I have a user 'User' in our ldap tree (novell eDirectory) i can log in with 'user' 'getent passwd user' will show 'User:*:###:###:User:/home/User:/bin/bash' whoami will return User as well when you su - user.
Please add steps to reproduce/verify this issue without eDirectory. thanks
I'm not sure if this bug made it into any of the released versions, so you might not be able to reproduce the issue, but verifying it is fixed should be rather easy: Create a user with mixed-case name. Run getent passwd SomeUser. With the default settings (which is case-sensitive), getent should return the name as stored on the server (SomeUser). Configure the SSSD domain to be case-insensitive (case_sensitive = false), remove the cache, restart SSSD and run getent again. The name should be returned lowercased in the case-insensitive domain (someuser)
Verified in version: # rpm -qi sssd | head Name : sssd Relocations: (not relocatable) Version : 1.8.0 Vendor: Red Hat, Inc. Release : 20.el6 Build Date: Fri 30 Mar 2012 06:45:57 PM IST Install Date: Mon 02 Apr 2012 05:36:37 PM IST Build Host: x86-002.build.bos.redhat.com Group : Applications/System Source RPM: sssd-1.8.0-20.el6.src.rpm Size : 7865577 License: GPLv3+ Signature : (none) Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> URL : http://fedorahosted.org/sssd/ Summary : System Security Services Daemon
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No documentation needed
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0747.html