Howdy, In a similar situation we use a web service running on another (3rd) tomcat server. It's worked well, especially as we've added more applications beyond our original two.
Agreed. This is the cleanest long-term solution I've come across as it clearly defines responsibility boundaries between your apps/components. It's more work than other (IMO hackish) solutions, but opens up so many more possibilities once you've got it up and running.
Yoav Shapira Millennium ChemInformatics
justin
>-----Original Message----- >From: jerome moliere [mailto:[EMAIL PROTECTED] >Sent: Thursday, December 04, 2003 6:51 AM >To: Tomcat Users List >Subject: Re: [offtopic] Architecture Question > >Laurent Michenaud wrote: > >>Hi, >> >> >Hi laurent, > >> >>We have two tomcat servers. >>One is located at our enterprise. >>The other is located at our hosting provider. >>They can see each other by Internet. >> >>We would like to set up an unique authentification system for both >>server. >>The authentification system will be on the server at our entreprise. >>The web applications on both servers will query the authentification >>system. >> >>What's the best/clean/nice way to do this ? >>JAAS ? Web services ? SSL keys ? >> >>
______________________________________________ Justin Ruthenbeck Software Engineer, NextEngine Inc. justinr - AT - nextengine DOT com Confidential. See: http://www.nextengine.com/confidentiality.php ______________________________________________
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
