Chmouel Boudjnah wrote:
>
> J�rgen Hermanrud Fjeld <[EMAIL PROTECTED]> writes:
>
> > I see Cooker includes openldap and nss_ldap, but not pam_ldap. Is there a
> > particular reason for this?
>
> He will uploaded in five minutes.
It seems to be back again...
>
> > I would very much like to see Cooker include full LDAP support, that would > > > >
>make
> > it very easy to maintain organisations with many clients and users.
I agree
> > How about out of the box ldap server on localhost, and authentication against
> > localhost. The adjust some of the ldap for linuxconf, or have som script to
> > easily connect to another server.
I agree. I'm currently looking in ldapconf from
http://terminator.net/ldapconf/
> > Also use ldap for as many things as possible, instead of /etc/flat files
> > Have some way of mounting /home/$USER upon login, reading the mount
> > spesifications from some LDAP server.
> > Also make good tools for maintaining the LDAP equivalent of /etc/flat files.
> > These are my wishes, how sane are they?
about tools and scripts, you can find nss_ldap in cooker, and the
current
openldap RPM come with the Migration Tools.
The difficult point is to set up a "default" configuration for all these
components. Ldap can be used in many ways, and the current option is to
not
activate too many of them : it's more easy for an admin to add options
in
ldap.conf than to remove them...
I know a few tools to maintain ldap data (gq using gtk, kldap / KDE,
some
html tools), but not always reliable.
thanks for your advice
jd
