logo       

Static Mappings: msg#00019

ldap.padl.nss

Subject: Static Mappings


Is there any way to create static mappings with nss_ldap? I'm trying to
integrate a network appliance into MS Active Directory so I can do user info
lookups, but I'd really rather not require that customers install SFU and
setup all their users as NIS users. With potentially thousands of existing
users/groups and the ongoing hassle of remember to add NIS attributes to all
new users/groups it's simply too much work to require for integration with
my appliance.

On OS X for example, it's possible to map an LDAP attribute to a static
value rather than to a up in the directory -- I'd like to do that with
gidNumber and uidNumber so that the default AD user entries are sufficient.
All authorization on the system is based on user/group name, so there's no
need to have real mappings, just sufficiently valid mappings to make NSS
work for username->group membership lookups and the like.

So if there's a way to create static mappings in nss_ldap, or some other way
to trick nss_ldap into thinking that the default AD users are sufficient for
use in Unix I'd be very appreciative of a link or other instructions.
--
View this message in context:
http://www.nabble.com/Static-Mappings-t1314790.html#a3504980
Sent from the NSS LDAP forum at Nabble.com.




<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise