Miguel Figueiredo wrote:
Just thought I'd drop you a quick note on options that might make your option #1 a lot faster: I don't know what kind of data store your thinking about using; maybe something like embedded HSQL? Anyway, if its anything like that you might want to look at:Hello folks,
I have a comment about out-of-box software ldap-enabled. It is very good to have a ldap implementation distributed alongside with our software, but will the clients want it? I believe most enterprises have already an authentication server, and they won't feel right to have another server to configure and maintain, just because our software needs it.
To solve this, one solution could be to distribute our software with easy LDAP configuration GUIs, that would connect our software with the client's enterprise Active Directory/LDAP server. Another solution would be to ship with our software an ldap cached proxy. The configuration GUI would still be needed but the good thing is that our software wouldn't slow down because of the remote ldap server and that same remote ldap server wouldn't slow down because of our software.
Anyway, the first solution means that we don't need to distribute any ldap server implementation! ;)
Best regards, Miguel Figueiredo
http://free.tagish.net/jaas/doc.html <- LGPL implementations of JAAS for a couple of different backends.
And again with acegi (Apache license); I haven't had a chance to get into it yet, but it appears to support JAAS authentication against a wide varient of backends, with all sort of different options, see:
http://acegisecurity.sourceforge.net/multiproject/acegi-security/apidocs/index.html
-- Robert r. Sanders Chief Technologist iPOV www.ipov.net
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
