There's been one request for follow up so I'll post our current findings.
This is what we've identified that we need to do to get Tomcat running
after moving from 5.5 to 7.0. At this point web application porting can
commence.
1. We used several Tomcat classes (e.g. EndPoint,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 1/6/12 7:05 PM, Mark Lim wrote:
We are in the process of upgrading Tomcat 5.5 to Tomcat 7.0.
These Tomcat deployments use a custom FIPS 140-2 certified JSSE
implementation for their SSL Connectors.
In case you are interested, Tomcats
Thanks for offering, but we're already in certification. When
recertification comes up we'll certainly consider consolidating security
modules.
On 2/13/12 1:33 PM, Christopher Schultz ch...@christopherschultz.net
wrote:
* PGP Signed by an unknown key
Mark,
On 1/6/12 7:05 PM, Mark Lim wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 2/13/12 4:45 PM, Mark Lim wrote:
Thanks for offering, but we're already in certification. When
recertification comes up we'll certainly consider consolidating
security modules.
Okay. Well, if you're willing to put our code into
We are in the process of upgrading Tomcat 5.5 to Tomcat 7.0. These Tomcat
deployments use a custom FIPS 140-2 certified JSSE implementation for their SSL
Connectors.
In Tomcat 5.5, the Connectors are configured like this:
!-- Define a SSL Coyote HTTP/1.1 Connector on port specified by the
Mark Lim mark_...@symantec.com wrote:
It seems that tomcat is trying the default JSSE implementation despite
the sslImplementationName attribute being set. Are there internal
precedence controls or does the classloader hierarchy matter or what?
No, but what makes you assume what you are trying
I have set up a Tomcat 5.5 server on a Windows machine. I modified the
server.xml file to enable SSL, created and imported a self-signed cert
using keytool, and it appears to be working. I can access
https://myserver:8443 both locally and from another machine on the
network.
However, I am
I have set up a Tomcat 5.5 server on a Windows machine. I modified the
server.xml file to enable SSL, created and imported a self-signed cert
using keytool, and it appears to be working. I can access
https://myserver:8443 both locally and from another machine on the
network.
However, I am
Hi,
I am pretty newbie to Tomcat.
I have been reading the documentation, and I was not successful enabling SSL
for tomcat 5.5.
I have a PKCS12 certificate (file name ***-cert.p12) and I want to use it
as my Tomcat certificate.
When I run the keytool command line utility I always get an error
I would *really* like to see more of your log, since this is a classic this
can't happen bug.
Jana Nguyen [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Hi there,
I am running Tomcat 5.5 on RH Linux as user 'tomcat', I'm trying to
get tomcat to run on a secure port 8443 instead of
Hi there,
I am running Tomcat 5.5 on RH Linux as user 'tomcat', I'm trying to
get tomcat to run on a secure port 8443 instead of 8080. I
uncommented the SSL HTTP/1.1 Connector entry in
$CATALINA_HOME/conf/server.xml and generated a host certificate as
user 'tomcat'. The .keystore file got
11 matches
Mail list logo
