Re: SQL/LDAP Gateway

["Mark Wilcox" <mark@mjwilcox.com>]

I like Kelvin's suggestion of seperating the data out if possible (e.g.
keeping a rdn or dn pointer in the SQL database that links to user contact
information)

There are 3 possible ways of also handling this:
1) Duplicate all of the data in both servers. Denote one server (probaly SQL
server if you have legacy applications tied to it already) as the master
server. All updates should be processed through this server and then passed
onto the LDAP server. Don't allow updates to the LDAP server (except for
perhaps password). This is what we're doing at work. Of course at work I
don't even have the option of rolling the other way (e.g. our primary
database is a mainframe application which we're not allowed to update)

2)  a middleware package that queries both systems and updates the parts
that changes into each server

3) a server plugin that passes all updates to the SQL server as well as let
the LDAP server handle the updates.

Mark
-----Original Message-----
From: m2n-openldap.general@do.khs-ag.de <m2n-openldap.general@do.khs-ag.de>
Newsgroups: mail.openldap.general
To: openldap-general@OpenLDAP.org <openldap-general@OpenLDAP.org>
Date: Tuesday, August 17, 1999 9:28 AM
Subject: SQL/LDAP Gateway


>Hi,
>
>I have a SQL server and a LDAP server.  Some part of the information
>should be stored in both servers.  Whenever someone changes somthing
>in the LDAP server, it should be updated in the SQL server and the
>other way round.  So I need some kind of LDAP/SQL gateway.  Does
>anybody know a software that can be used for such task?
>
>Sascha
>
>
>
>