I'm trying to configure beta2 to use LDAP for authentication (I'm currently
running 6.2 with this configuration with no problems, so I know things are
working in general).
However, after filling out the LDAP server and base DN in the installer,
the installer ran the following authconfig command line:
authconfig --kickstart --nostart --useshadow --enableMD5 --enableldap
--ldapserver '' --ldapbasedn ''
The LDAP server and base DN appear to have been lost in the shuffle.
I should also mention that selection "LDAP" for authentication during the
install does not appear to automatically select nss_ldap and pam_ldap for
installation, making it likely that things will break in any case.
This works correctly for me in the current internal build.
Passed to test lab for verification.
hmmm ... in the test lab using beta2 both in TUI & GUI mode the ldapserver and
basedn parameters are properly populated by the values entered in at the
a quick test verified ldap's local server data configuration was passed to the
client ...further the relevant packages were installed:
% rpm -q nss_ldap openldap
These installs were minimal custom installs enabling shadow, md5 and ldap at the
authentication screen ... Is this much different than what you are doing, Lars
this is also working in beta3 ... please reopen if you are seeing different
results than us, Lars ... thanks for your report!