Am 28.04.2011 16:57, schrieb Christopher Schultz:
-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 an
mplementation and then different from Sun's)
Am 27.04.2011 18:39, schrieb Chris Beckey:
Are you using JSSE or OpenSSL for your SSL implementation?
On Tue, Apr 26, 2011 at 4:40 PM, Thomas Hill
wrote:
Hi Felix,
thanks for your reply. So does this mean no way on Tomcat 5.5? (as I
won't
the certificate to trigger read-only
restrictions).
Tx& Rgds
Am 26.04.2011 21:52, schrieb Felix Schumacher:
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-genera
y
(so misuse the expiry date on the certificate to trigger read-only
restrictions).
Tx & Rgds
Am 26.04.2011 21:52, schrieb Felix Schumacher:
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. T
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
