Re: matching leading space in uid lookup

[Duncan Brannen <dbb@st-andrews.ac.uk>]

Samba is passing on what Windows passes to it, so I'm not sure Samba is broken,
it's asking ldap if user " xxx" can authenticate with credentials y and 
ldap's saying
yes user "xxx" can authenticate with credentials y.  I don't see that " 
xxx" == "xxx"

uid equality is a caseignoreMatch which is space insensitive, I guess that 
includes
leading spaces? Is this then, correct ldap behavior for this case?

Is there a way to change this without necessarily changing the core schema?

To 'fix' samba, you'd have to fail logins for any username starting with a 
space.
I can't see why people would want to start a username with a space but....

Of course, getting the windows admin to turn on the "Press Ctrl-Alt-Del" to 
log in
gets rid of the "user pressing space bar to login" problem :)


Cheers,
        Duncan


At 13:05 19/05/2003 +0200, Michael Ströder wrote:
> Duncan Brannen wrote:
> > We're running samba 2.2.8a as a PDC for windows classrooms with an LDAP 
> > backend.
> > What's happening is that users are waking up the windows machines by 
> > pressing the
> > space bar and then logging in.  They authenticate successfully (leading 
> > spaces ignored)
> > but windows is miscreating the roaming profiles with leading spaces which 
> > causes the
> > folder structure to be created incorrectly.
>
> Doesn't sound like an OpenLDAP issue to me. Probably one has to fix Samba.
>
> Ciao, Michael.