Chris,
many thanks for your explanaitions on OpenSSL. The hoster is now running
Tomcat using Sun's JDK JSSE implementation and everything is working as
I wanted, i.e. client certificates can be used post their expiration date.
I have tested with FireFox and assume other browsers will show the
Christhoper,
thanks for your continued support. I am glad that, now with my hosted
server using the Sun JSSE implementation, everything is working as I
wanted and I do not have to try using a different trust manager (which I
am afraid would have been a too technical task for me).
Regards
Are you confident OpenSSL ...
From what you have presented so far I'd say the answer is yes. Regardless
of which library you are using, the TLS/SSL handshake protocol is completed
before Tomcat code has been called into so it is either an OpenSSL or a JSSE
lib issue and not, at least technically,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas,
On 4/26/2011 4:40 PM, Thomas Hill wrote:
thanks for your reply. So does this mean no way on Tomcat 5.5? (as I
won't switch to a newer version, especially 7.x any time soon)
There is another way to install your trust manager: we used this
The Tomcat hoster tells me OpenSSL is used on the server side (in a
reply email from support - I will double-check in a phone call during
business hours as this was not my current understanding).
Are you confident OpenSSL is refusing the connection to be established
when a client certficate
Are you using JSSE or OpenSSL for your SSL implementation?
On Tue, Apr 26, 2011 at 4:40 PM, Thomas Hill thomas.k.h...@t-online.dewrote:
Hi Felix,
thanks for your reply. So does this mean no way on Tomcat 5.5? (as I won't
switch to a newer version, especially 7.x any time soon)
To your
Hi,
I am using clientAuth on Tomcat 5.5.30, JVM version 1.6.0_21-b06 from
Sun on Linux. The client certificates are self-generated and signed as I
am acting as CA for the client certificates. Authentication is working
as expected until the certificate expiry date is reached which is when I
am
On Tue, 26 Apr 2011 20:44:38 +0200, Thomas Hill wrote:
Hi,
I am using clientAuth on Tomcat 5.5.30, JVM version 1.6.0_21-b06 from
Sun on Linux. The client certificates are self-generated and signed
as
I am acting as CA for the client certificates. Authentication is
working as expected until the
Hi Felix,
thanks for your reply. So does this mean no way on Tomcat 5.5? (as I
won't switch to a newer version, especially 7.x any time soon)
To your question:
Primary reason is I want my fat client java application and my java web
application to react the same way when a user supplies an
