Thanks! That's perfect!
(Wow, there really is a 'bootableDevice' objectClass)
Cheers,
sach
On Wed, 5 Sep 2001, Lorin wrote:
> Here is a great site with the definitions of most of the standardly used
> schemas:
>
> http://ldap.hklc.com/
>
> The question is what are you really? Are you a Person, an InetOrgPerson,
> or perhaps a bootableDevice?
>
> -Lkb
>
> On Wed, 5 Sep 2001, tack wrote:
>
> > umich grad program docs for ldap are the holy grail....those students were
> > grabbed up by netscape in 96, so netscape dev site is also a gret
> > reference.
> >
> > In general, and ldap "key" is a "Distinguished Name" consisting of the
> > user's "common name (cn)" and country:
> >
> > cn="tack anti-gates" co="US"
> >
> > Optionally, people substitute organization or organizational unit for
> > country. I see this as a bad practice, as those can change frequently,
> > and country is a bit less volitile.
> >
> > Also consider doing an LDIF import. Usually, you can just create user
> > data externally then import it in bulk. OR....being LDAP, you can just
> > set the server to inherit the data from a higher level ldap server.
> >
> > tack
> >
> > On Wed, 5 Sep 2001, Sach Jobb wrote:
> >
> > > Hola!
> > >
> > > Anyone have any experience with using ldap for authentication? I'm using
> > > openldap and have slapd up and running okay but i'm having trouble finding
> > > standards for actually creating entries. I.E. objectClass=Person versus
> > > objectClass=organizationPerson and so on.
> > >
> > > Cheers,
> > > sach
> > >
> > >
> > >
> > >
> >
> >
>
>
--
/*
Sach Jobb
[EMAIL PROTECTED]
%s/windows/linux/g
*/
"As far as i'm concerned the two biggest hassles in the world revolve
around DNS and girlfriends."
-- (name undisclosed to protect the innocent)
