Damien McKenna wrote: > 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. >
That sounds like a pretty neat solution. I do something similar in a fwe apps at work where I authenticate users against our DB2 mainframe, then store their user information in a local oracle table.... except in my case, users are ALWAYS authenticated against DB2... I just keep the information in oracle for other purposes.. (like when someone reserves a conference room, I've got their name, phone, dept, etc locally) - Rick -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.4 - Release Date: 2/1/2005 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:192794 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
