It works really well.
I've done this on many projects in the past with very good results. I've had the need to do it in both directions, having the DN be the primary key in a RDB table (a Pseudo-foreign key), and having a RDB primary key be part of the DN of an LDAP object that was being programmatically created. You have the obvious potential for problems due to the possibility of failure of one system or the other, but there are many things you can do to minimize those issues. Replicating the information between the two systems is usually much more expensive, less maintainable, and not much more reliable than the above alternatives.
My $.02
chris murphy
lead developer
�
nuforia inc.��� > houston
v 713.354.1557
f 713.354.1600
http://www.nuforia.com
-----Original Message-----
From: Javier Borrajo [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 24, 2000 12:35 PM
To: [EMAIL PROTECTED]
Subject: Re: LDAP + SQL
So when the app creates a new user it inserts a new entry into both
LDAP and into a table in the DB, maybe "user distingished name" (DN)
into table USERS...
Javier
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
