Re: No X509Certificate Attribute In IIS Redirected Request

2007-06-27 Thread Simon . Temple
rom Microsoft called SSLDiag to diagnose the second of my problems. I hope this is useful... if only to state that this is NOT a problem with JK1.2 or Tomcat 6 Thanks to all who commented - Simon T Subject: Re: No X509Certificate Attribute In IIS Redirected Request Hi Simon, Have

Re: No X509Certificate Attribute In IIS Redirected Request

2007-06-21 Thread Bill Barker
<[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > Hi, > > I'm using: > >IIS V6.0 >JK 1.2.23 >Tomcat 6.0.13 > > No X509Certificate attribute is present in the request header received by > my servlet when using Client Authenticated SLL with IIS6 and JK1. > > If I use Apach

Re: No X509Certificate Attribute In IIS Redirected Request

2007-06-21 Thread Rainer Jung
OK, then you should be able to retrieve them on the tomcat side with request.getAttribute(). [EMAIL PROTECTED] wrote: OK I enabled JK1 debug level logging and can see that IIS6 *is* relaying the client authenticated SSL details in the AJP stream. I see attributes called: CERT_ISSUER

Re: No X509Certificate Attribute In IIS Redirected Request

2007-06-21 Thread Rainer Jung
I never used it. If you have a test system, you could switch you switch the log level of the isapi plugin to debug and check, if your plugin log file shows messages containing Client Certificate encoding Then you would at least find out, if the plugin detected a client certificate. Regards,

Re: No X509Certificate Attribute In IIS Redirected Request

2007-06-21 Thread Simon . Temple
HTTPS_SERVER_ISSUER HTTPS_KEYSIZE JK1 appears to ignore them! So is this a defect in JK 1.2.23 or something I need to 'switch-on'? - Simon Temple 21 June 2007 15:38 To: users@tomcat.apache.org cc: From: [EMAIL PROTECTED] Subject: No X509Certificate Attribute In IIS Redirected Req

No X509Certificate Attribute In IIS Redirected Request

2007-06-21 Thread Simon . Temple
Hi, I'm using: IIS V6.0 JK 1.2.23 Tomcat 6.0.13 No X509Certificate attribute is present in the request header received by my servlet when using Client Authenticated SLL with IIS6 and JK1. If I use Apache 2.2 with the mod_proxy modules it works fine. Is this a bug? If so, in what.