I took a look to JavaDoc and saw that all methods are deprecated. Is it really the right way? My first thought was that it's very low level. Doesn't there exist an easier solution for my problem?
****************************************************************** Oliver Wulff Zürich Versicherungs-Gesellschaft IA4, CoC Middleware Postfach, 8085 Zürich Telefon: +41- 1 628 58 07 Fax: +41 - 1 623 58 07 E-Mail: mailto:[EMAIL PROTECTED] "Ralph Einfeldt" <[EMAIL PROTECTED] An: "Tomcat Users List" <[EMAIL PROTECTED]> ime-isc.de> Kopie: Thema: RE: user principal, realm 01.04.2003 14:50 Bitte antworten an "Tomcat Users List" Although I havn't tried it, I guess yes. I think you have to define your own RequestWrapper that lets you set the principal. > -----Original Message----- > From: Oliver Wulff [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 01, 2003 2:42 PM > To: [EMAIL PROTECTED] > Subject: user principal, realm > > > Can I implement a filter which sets the current principal, so > that calls to > request.getUserPrincipal().getName() succeed? > > In our company, an apache server in front of tomcat authenticates the > client and delegates the user principal as an http header attribute. > I want to read this principal and set the user principal in a filter. > Can I do this? > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
