Bug 706860

Summary: 2 digits login names no seen after upgrading to nss-pam-ldapd-0.7.5-7
Product: Red Hat Enterprise Linux 6 Reporter: Francois Marabelle <francois.marabelle>
Component: nss-pam-ldapdAssignee: Nalin Dahyabhai <nalin>
Status: CLOSED ERRATA QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.1CC: cww, dash, david.donn, dpal, jhrozek, luke, mpoole, omoris, pasteur, prc, rdassen
Target Milestone: rcKeywords: Regression, ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: nss-pam-ldapd-0.7.5-8.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 17:36:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 726309    

Description Francois Marabelle 2011-05-23 09:37:00 UTC 
Description of problem:

After upgrading from 0.7.5-3 to  0.7.5-7  login names with only 2 digits
are not seen anymore

Version-Release number of selected component (if applicable):
0.7.5-7

How reproducible:
Always

Steps to Reproduce:
1. create a 2 digits account on ldap server
2. try to login
3.
  
Actual results:

unknown user

Expected results:
login...

Additional info:
downgrading to nss-pam-ldapd-0.7.5-3 solve the problem.
Comment 2 Nalin Dahyabhai 2011-05-23 15:25:02 UTC 
The default value for the "validnames" setting as we added it expects names to be at least three characters long, though this is relaxed a bit in subsequent versions to a minimum of two.  Setting
  validnames /^[a-z0-9._@$()][a-z0-9._@$() \~-]*[a-z0-9._@$()~-]$/i
in /etc/nslcd.conf should work around this until we catch up with it.
Comment 3 Francois Marabelle 2011-05-24 06:53:14 UTC 
It works. Thanks
(In reply to comment #2)
Comment 5 Nalin Dahyabhai 2011-05-31 14:10:15 UTC 
*** Bug 709094 has been marked as a duplicate of this bug. ***
Comment 17 Jakub Hrozek 2011-11-07 09:45:51 UTC 
*** Bug 751654 has been marked as a duplicate of this bug. ***
Comment 18 errata-xmlrpc 2011-12-06 17:36:09 UTC 
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-2011-1705.html