Since this only really has a chance of working with a 2.3+ container (like Tomcat 4.x), I'd probably use a Filter instead of chaining Servlets. However, the idea is the same. You create a HttpServletRequestWrapper that overrides getRemoteUser and getUserPrincipal (and, possibly, isUserInRole) that understands the Domino authentication. You then pass the Wrapper along in the chain so that the destination Servlet gets the correct values for the above.
"Jim Henderson" <[EMAIL PROTECTED]> wrote in message 003301c2c313$8cdf8910$[EMAIL PROTECTED]">news:003301c2c313$8cdf8910$[EMAIL PROTECTED]... > I have an existing Servlet that requires an authenticated user > (HttpServletRequest.getRemoteUser()). However, the Servlet can now be > invoked from another application on a Domino server which the user has > already signed on to. The Domino server will redirect the request to my > Servlet and pass the user ID in a file. To avoid changing my original > Servlet I want to try Servlet Chaining. However, how do I set the userID in > the redirected request stream? Is that possible? > > Thanks! > Jim Henderson -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
