Jboss 3.2.2/Tomcat4.1 Cert authentication is not good enough.

["Rawat, Krishna" <Kr...@DRKW.com>]

Hi All,
 
Jboss 3.2.2 comes default as Tomcat 4.1 web container whose Cert
Authentication does not work as Jetty's.
 
Let me elaborate my problem and then will write my Fix.
 
After certificate authentication, the application writers will want to get
more information about the user other than just the principal name.  In
order to do this we have a service which returns information about the user
when passed the authenticated principal. This means than the principal name
needs to be something sensible ( currently userID in Jetty and Weblogic
setup )
 
To fix above problem, i have created a wrapper  which creates a principal
and changed its name without changing  the Object hashcode. This works fine.

 
I am happy to send the patch, let me know whom do i send it to?
 
thanks
Krishna
 
 
 
 
 


--------------------------------------------------------------------------------
The information contained herein is confidential and is intended solely for the
addressee. Access by any other party is unauthorised without the express
written permission of the sender. If you are not the intended recipient, please
contact the sender either via the company switchboard on +44 (0)20 7623 8000, or
via e-mail return. If you have received this e-mail in error or wish to read our
e-mail disclaimer statement and monitoring policy, please refer to 
http://www.drkw.com/disc/email/ or contact the sender.
--------------------------------------------------------------------------------