There have been various posts regarding Tomcat's inability to successfully
complete client authentication, particularly with Microsoft's IE. We've
discovered the answer to Tomcat's problem. It turns out that as part of the
client-cert request in the standard SSL protocol, the server side sends a
I had a similar problem, except that I also had a sealed-data exception. In
my case, it turned out that the (sealed) jar file crimson.jar is in both the
lib and server directories. I fixed my problem by unsealing the .jar file --
that is, by un-jaring the file and then re-jaring it.
the client
cert to IIS. Anybody have any clues??
R.W. Shore
Templar Corporation
Alexandria VA
