[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Login Failure

Well, the hell if I know.  I did two things.....I rebooted.....I copied
the /etc/ldap.conf from the other machine and it started working.......

go figure.....

It had to of been something hungup in the OS somewhere.  I did a diff on
the two ldap.conf files and found them identical.  No tabs all white

Turns out nothing was wrong with userPassword, I seen this when I logged
in on another machine with the testuser account.

Well I learned how to search, add, modify, replace, about objects, about
attributes, *and* little more than I wanted to known about the fuzz
between the toes of my 4 year daugherty.  heheheheh She's funny. :-) Had
me rolling on the floor....

Robert Canary wrote:
> Well I've come to a point where I was set to try some real time test...
> I used a test user that I keep on the local machine.  Who was migrated
> successfully to the ldap server.
> I remove the testuser entries from the local machines files, and then I
> tried to login. Failure, Failure, Failure.
> I did notice the encypted password in the testuser file is not what I
> would expect it to be.  The migrate script sent
> {crypt}gYGSGYsyduiedhia== however, the userPassword is showning
> something entirely diferrent.  So here is the question:
> When one modifies a userPassword as follows:
> #>slapd -h {md5}
> #>password: ***********
> #{md5}ggGUYGiu_8==
> testuser.ldif
> -------------------
> dn: uid=testuser,ou=People,dc=example,dc=com
> changetype: modify
> replace: userPassword
> userPassword: {md5}ggGUYGiu_8==
> ldapmodify -H ldap://localhost -D "cn=root,dc=example,dc=com" -x -W -f
> testuser.ldif
> What is ldap doing with the userPassword to change it.  Should I not be
> crypting the password entry?  Should I just put the bare text
> {MD5}password as the entry.  The import came from a /etc/shadow file.
> I can see the nscd log where it going out for the passwd to ldap server,
> however, I don't see anything on the ldap server that it trying to do
> anything.