Does the authentication have to happen on a physically separate web server?
If you're the maintainer of both of the initial applications then writing an authentication library for use in both applications is certainly less work than maintaining third application for authentication and the communication from the two applications to that authentication server. What maintenance does a library need? Just create it and put it into a jar file. It should have a connection pool to the database and a knowledge of what tables to access for authentication. Then in your servlet's init, initialize the library and then call its .isAuthenticated method. Look at the PetStore app example on how to do stuff like that. d. rusty bawa wrote:
Thank you for your reply. I have thought about it, but how can i call a library residing on another server? I can replicate [by pushing] libraries to each server when files get updated, but that looks like a lot of maintenance work. what do you think? bawa __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
-- David Mossakowski Instinet Corporation ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
