[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: LDAP vs SQL

To: openldap-general@openldap.org
Subject: Re: LDAP vs SQL
From: Jonathan Ruano <kobalt@james.encomix.es>
Date: Wed, 28 Oct 1998 10:08:02 +0100
In-reply-to: <Pine.LNX.3.95.981027142829.118M-100000@freeside.ultraviolet.org>; from Tracy R Reed on Tue, Oct 27, 1998 at 03:16:00PM -0800
References: <Pine.LNX.3.95.981027142829.118M-100000@freeside.ultraviolet.org>

On Tue, Oct 27, 1998 at 03:16:00PM -0800, Tracy R Reed wrote:

> people have a perl script running on each system that queries the LDAP
> server and rebuilds files (password, shadow, tcb, group, aliases, hosts,
> dns, etc) based on the info it retrieves?  If this is the case, there
> doesn't seem to be much advantage to using LDAP over a regular SQL
> database. 
> Generating the whole password file sounds kinda risky anyhow.
> What if there were a crash as it was half written? At least root would be
> first. 
I'd implement a method of authenticating users thru LDAP, rather than
replicating passwd's. PAM (Plugglable Authentication Modules) comes to
my mind.

The only problem you should solve is uid/gid/homedir mapping, if any.

-- 
Jonathan Ruano <kobalt@james.encomix.es>
Intercomputer soft, s.a.
Dpto. de Tecnologia

References:
- LDAP vs SQL
  - From: Tracy R Reed <treed@ultraviolet.org>

Prev by Date: Superclasses in Nestcape directory server and OpenLDAP server
Next by Date: RE: LDAP vs SQL
Index(es):
- Chronological
- Thread