Hi,
I'm  trying to get automount maps to work using ldap against AD using the 
default NIS/rfc2307 schema entries as on MS Server2008R2 from an osol snv_134 
client

All is well with kerberos, ldap works with sasl/GSSAPI  but the problem seems 
to lay in the ldap client config with either the objectclassMap setup or the 
SSDs

relevant bits of schema mapping-some of which may be superfluous- in ldapclient 
config is:

-a objectClassMap=automount:automountMap=nisMap \
-a objectClassMap=automount:automount=nisObject \
-a objectClassMap=auto_home:automount=nisObject \
-a objectClassMap=auto_home:automountMap=nisMap \


-a attributeMap=passwd:homedirectory=unixHomeDirectory \
-a attributeMap=auto_home:automountMapName=nisMapName \
-a attributeMap=auto_home:automountInformation=nisMapEntry \
-a attributeMap=auto_home:automountKey=cn \
-a attributeMap=automount:automountMapName=nisMapName \
-a attributeMap=automount:automountInformation=nisMapEntry \
-a attributeMap=automount:automountKey=cn \


SSDs of the form (as found by Googling many many docs)

serviceSearchDescriptor=auto_home:nisMapName=auto.home,cn=nisdomain,cn=defaultMigrationContainer30,dc=....

    return Object not found 

 but if I use cn=  for the object type automounts (auto_home maps) work fine

serviceSearchDescriptor=auto_home:cn=auto.home,cn=nisdomain,cn=defaultMigrationContainer30,dc=...?sub

locates the map entries and returns correct info.  So I can make it work but:

  1/  why do I need to specify the whole path of cn=...  containers to find the 
map entries?

  2/ I expected the nisMapName attribute to match the "auto.home"  attribute in 
the AD entry

I'm obviously misunderstanding something - anyone see what could be wrong?
-- 
This message posted from opensolaris.org
_______________________________________________
networking-discuss mailing list
networking-discuss@opensolaris.org

Reply via email to