I did something like that for TikiWiki two years ago. My technique was to use the database as a cache of the LDAP information. I would query the LDAP server first, if the member was found then either update the database or create a new account for them using the LDAP information. If the account was not found in the LDAP server then I would query the database per usual. I also added a part to create the LDAP user if it wasn't found, but that's probably a bit more than you want.
-- Damien McKenna - Web Developer - [EMAIL PROTECTED] The Limu Company - http://www.thelimucompany.com/ - 407-804-1014 #include <stdjoke.h> > -----Original Message----- > From: Rick Root [mailto:[EMAIL PROTECTED] > > It would take quite a lot of customization at this point to > integrate with activedirectory authentication, a shared user > database, etc... I haven't actually contemplated how to deal > with a shared user database yet.. > Especially in an environment where only some users (the > students) would authenticate via ActiveDirectory. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:192791 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
