Hi Bruno, Thanks for the details. Do you have pointers to how this mechanism precisely works in Tomcat and/or Jetty?
Also, if you could open an RFE and summarize our discussion that would be a good step forward. Best regards, Jerome > -----Message d'origine----- > De : news [mailto:[EMAIL PROTECTED] De la part de Bruno Harbulot > Envoyé : lundi 5 novembre 2007 10:22 > À : [email protected] > Objet : Re: Client X509Certificate attribute using the AJP connector > > Hello Jérôme, > > I'm using the Jetty AJP connector directly. I haven't tried the > ServerServlet yet, so I'm not sure what information it passes through. > Another thing I would be interested in is to get the remote user, as > authenticated by Apache Httpd. This is something servlets can > get using > Jetty or Tomcat (provided they are configured accordingly). > I'm quite new to Restlets, but I had in mind it could be > useful to get > the client X.509 certificate and/or the remote user in a Guard that > would perform the authorisation. > > Best wishes, > > Bruno. > > Jerome Louvel wrote: > > Hello Bruno, > > > > Are you using the ServerServlet adapter class or directly the Jetty > > AJP connector with Restlet ? > > > > Thanks, > > Jerome > > > > 2007/11/2, Bruno Harbulot <[EMAIL PROTECTED]>: > >> Hello, > >> > >> Using Servlets and Tomcat behind Apache Httpd/AJP > (configured to require > >> or want a client certificate in HTTPS), it's possible to > get the client > >> certificate chain using this: > >> request.getAttribute("javax.servlet.request.X509Certificate"); > >> > >> I've tried to get this piece of information with a Restlet > (using AJP), > >> but this attribute doesn't seem be set. This is hardly surprising > >> because of "servlet" in the name, but I can't find any equivalent > >> attribute. Is there any other mechanism to get this from a Request? > >> > >> Best wishes, > >> > >> Bruno. > >> > >
