« Return to Thread: pam_ldap on CentOS passed INCORRECT is local account doesn't exist

Re: pam_ldap on CentOS passed INCORRECT is local account doesn't exist

by lavermil :: Rate this Message:

Reply to Author | View in Thread

WOOHOO!!! I have solved my problem with a LOT of looking around and
nice responses from Weston and Patrick. Thank you for all your help.

To sum things up in case anyone else runs across this too.

OpenDS does not create the objectClass posixAccount or
extensibleObject by default. You will need to add these to use PAM. If
you have a default install of OpenDS then you will need to do the
following:

Add objectClass = nisKeyObject (requires many other attributes)
or
Add objectClass = extensibleObject (required for uidNumber)

Add uidNumber = <some UID number> (requires extensibleObject or nisKeyObject)
Add gidNumber = <some GID number>
Add homeDirectory = <some directory path for user accounts>

If all of that is there then you should have an output like I have
below after adding the attributes mentioned above to the default load
of test users.

#
# Output of all my fields.
#
dn: uid=user.2,ou=People,dc=disamcep,dc=com
objectClass: person
objectClass: inetorgperson
objectClass: organizationalperson
objectClass: extensibleObject
objectClass: posixAccount
objectClass: top
postalAddress: Aarika Atpco$00900 Maple Street$New Orleans, KS  10857
postalCode: 10857
uid: user.2
description: This is the description for Aarika Atpco.
loginShell: /bin/bash
userPassword:: e1NTSEF9T3VSS1ViQ1hLUTJFdG9aNzRnamVqSTJFTDhjRm1uaG14anAvdmc9PQ=
 =
employeeNumber: 2
initials: AOA
givenName: Aarika
pager: +1 053 688 9803
mobile: +1 279 618 3901
cn: Aarika Atpco
telephoneNumber: +1 757 462 0301
sn: Atpco
street: 00900 Maple Street
homeDirectory: /home/user.2
homePhone: +1 003 428 0962
uidNumber: 1002
mail: user.2@...
l: New Orleans
st: KS
gidNumber: 1002



On Tue, Sep 2, 2008 at 1:18 PM, Lance Vermilion <pamldap@...> wrote:

> Hmm. I don't see a single ldap packet go out for the getent passwd
> user.2 or getent -s ldap passwd user.2.
>
> On Tue, Sep 2, 2008 at 12:14 PM, Weston Rogers <wrogers@...> wrote:
>>> Is the "getent passwd user.2" suppose to query the ldap server?
>>
>> Yeah, if that doesn't work you've got a wrong binddn, or some other
>> configuration setting that is making LDAP auth not work.
>>
>> Wes
>>
>

 « Return to Thread: pam_ldap on CentOS passed INCORRECT is local account doesn't exist