tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: Authentication Practices
Date Fri, 16 May 2003 16:38:53 GMT
You can pass authentication using the URL syntax if you want to use basic 
authentication - eg link across to the other server with the URL 
http://username:password@myhost/myapp/ - this would be one way to solve 
it.  Otherwise we have written custom authentication handlers which can 
serialise a user's bean on the session and pass that id across to another 
server for it to be deserialized.  This is managed using filters instead 
of the standard system

Kiss Technologies

Please note, we have moved!

4, Percy Street

New permanent phone numbers:

Phone 020 7692 9922
Fax 020 7692 9923

danox <>
16/05/2003 02:11
Please respond to "Tomcat Users List"
        To:     Tomcat Users List <>
        Subject:        Authentication Practices

OK this is not a pure tomcat question, but hopefully it will be known by 
someone here.

I am working on moving a current application written for the Domino 
platform to a Tomcat platform, for various reasons, we have decided to 
do this piece by piece. Thus we will have a domino instance runing on 
one server and a tomcat instance running on another server.

The issue that I have is with authentication. I have been able to make 
tomcat authenticate from the same source as Domino, however when a 
person jumps from the domino server to the tomcat server, or vice versa, 
they must athenticate twice.

I need to find a way to make the browser send the same authentication 
details to both servers. I have been reading up on HTTP authentication, 
and I believe that this is possible to do with digest authentication (as 
opposed to basic), but my experiments with this have so far failed. Has 
anyone had any experiencing seting up tomcat to validate seamlessly with 
another type of server using digest authentication, or some other method?

Thanks in advance.


To unsubscribe, e-mail:
For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message