fetching user details from a ldap entry which consists of an objectClass other than posixAccount

View: New views
3 Messages — Rating Filter:   Alert me  

fetching user details from a ldap entry which consists of an objectClass other than posixAccount

by amaramrahul :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I am using libnss-ldap in Debian Lenny. My LDAP user account entry does not contain the objectClass posixAccount. Instead it belongs to another objectClass sCSPerson. Adding both the object classes to the user account entry is not an option. I would like to know the configuration parameter to be used in libnss-ldap.conf so that the user details are fetched from the entries whose objectClass is sCSPerson rather than posixAccount. I have tried the below configuration parameter but it does not work:

nss_base_passwd     ou=People,dc=synovel,dc=com?sub?objectClass=sCSPerson

Are there any other means of achieving the same?

Re: fetching user details from a ldap entry which consists of an objectClass other than posixAccount

by Bugzilla from bgmilne@mandriva.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Monday 06 April 2009 15:04:09 amaramrahul wrote:
> I am using libnss-ldap in Debian Lenny. My LDAP user account entry does not
> contain the objectClass posixAccount. Instead it belongs to another
> objectClass sCSPerson. Adding both the object classes to the user account
> entry is not an option.

Since posixAccount is an auxiliary objectclass, this should really not be a
problem ...

> I would like to know the configuration parameter to
> be used in libnss-ldap.conf so that the user details are fetched from the
> entries whose objectClass is sCSPerson rather than posixAccount. I have
> tried the below configuration parameter but it does not work:
>
> nss_base_passwd     ou=People,dc=synovel,dc=com?sub?objectClass=sCSPerson
>
> Are there any other means of achieving the same?

Please see the nss_map_objectclass option, documented in the nss_ldap(5) man
page in recent releases of nss_ldap.

Regards,
Buchan

Parent Message unknown Re: fetching user details from a ldap entry which consists of an objectClass other than posixAccount

by amaramrahul :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Thanks for the prompt reply. This option works perfectly. I somehow did
not understand this option properly and tried it out but did not put in
the correct configuration. But now it works great.

- Rahul.


Rechenberg, Andrew wrote:

> You have to compile nss_ldap with schema attribute mapping enabled (it
> might be enabled by default now) and add an entry to libnss-ldap.conf or
> ldap.conf :
>
> nss_map_objectclass posixAccount sCSPerson
>
>
>
>    
>> -----Original Message-----
>> From: owner-nssldap@... [mailto:owner-nssldap@...] On Behalf
>> Of amaramrahul
>> Sent: Monday, April 06, 2009 9:04 AM
>> To: nssldap@...
>> Subject: [nssldap] fetching user details from a ldap entry which
>> consists of an objectClass other than posixAccount
>>
>>
>> I am using libnss-ldap in Debian Lenny. My LDAP user account entry
>>      
> does
>    
>> not
>> contain the objectClass posixAccount. Instead it belongs to another
>> objectClass sCSPerson. Adding both the object classes to the user
>> account
>> entry is not an option. I would like to know the configuration
>>      
> parameter
>    
>> to
>> be used in libnss-ldap.conf so that the user details are fetched from
>> the
>> entries whose objectClass is sCSPerson rather than posixAccount. I
>>      
> have
>    
>> tried the below configuration parameter but it does not work:
>>
>> nss_base_passwd
>> ou=People,dc=synovel,dc=com?sub?objectClass=sCSPerson
>>
>> Are there any other means of achieving the same?
>> --
>> View this message in context: http://www.nabble.com/fetching-user-
>> details-from-a-ldap-entry-which-consists-of-an-objectClass-other-than-
>> posixAccount-tp22908363p22908363.html
>> Sent from the NSS LDAP mailing list archive at Nabble.com.
>>      
>
>
> Confidentiality Notice: This e-mail message including attachments, if any, is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, but do not wish to receive communications through this medium, please so advise the sender immediately.
>