Red Hat Bugzilla – Bug 462405
/etc/sysconfig/autofs does not support BASEDN for ldap search
Last modified: 2008-09-16 23:14:10 EDT
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install RHEL 5.2 with following packages
2. Configure autofs to use both local automount maps and LDAP based maps
Same ldap directory with two subdomain:
Without BASEDN to restrict search domain, all sites will get the same
automount maps for one of the two sites.
Both nyc and lax hosts will recieve the same automount maps. autofs-4.x supports BASEDN so each site can limit ldap search to only its own subdomain.
autofs-5.0.x should restore the BASEDN feature so ldap autofs maps can be retrieved based on the search domain.
Yes, that's right.
This was initially omitted from version 5 but, as of
RHEL-5.2, the SEARCH_BASE configuration option was
added. It has a different name, I know, but that's
because it provides slightly different functionality.
# SEARCH_BASE - base dn to use for searching for map search dn.
# Multiple entries can be given and they are checked
# in the order they occur here.
Perhaps you were lead astray by the reference to "map search dn"
but, in version 5, the base dn used in lookups is the map search
dn which is worked out at module load time and re-calculated when
a HUP signal is received.
At least it is supposed to work this way, is that not the case?
Thanks. I did test it on a 5.2 machine and it worked.
Please close this bug ticket.
Great, sorry about using a different config name but it
does work differently so I thought it best.