RE: Tomcat IBM SSL Provider

2003-08-03 Thread McClure, Timothy J(IndSys, GE Interlogix)
I am still having trouble trying to use Tomcat with the IBM JVM 1.4 on AIX.  I took 
the 4.1.26 jsse package and replaced to tomcat-util 4.1.24 jsse package files.  I was 
running everything with 4.1.24 except for the 4.1.26 jsse package.  When I brought 
Tomcat up I received some reflection error.  I then just decide to use the 
tomcat-util.jar 4.1.26 with Tomcat 4.1.24.  This seems to work better however I 
receive a SunX509 algorithm not found IO error.  I have the Sun JSSE jars in my Tomcat 
Server lib and I entered them into the java.security file.  I also had 
algorithm=IbmX509 set in the right place in my server.xml file.  Tomcat seems to 
want to use SunX509 no matter what.  I would greatly appreciate any help someone could 
give regarding this issue.

Tim

-Original Message-
From: Bill Barker [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 22, 2003 11:40 PM
To: [EMAIL PROTECTED]
Subject: Re: Tomcat IBM SSL Provider


4.1.26 is currently in it's evaluation period to determine what it's
stability rating will be.  The official release is likely to be the end of
the week, or early next week.  In the mean time, it is currently living at
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.26-alpha/,
for anyone that wants to help out in the evaluation.  Don't be scared off by
the alpha label:  That's just what it gets called until the evaluation
period is over.

McClure, Timothy J(IndSys, GE Interlogix) [EMAIL PROTECTED] wrote in
message
news:[EMAIL PROTECTED]
We are using what I thought was the lastest 4.1.24.  I did not see an option
for download 4.1.26 on the jakarta web page.

Tim

-Original Message-
From: Bill Barker [mailto:[EMAIL PROTECTED]
Sent: Monday, July 21, 2003 11:09 PM
To: [EMAIL PROTECTED]
Subject: Re: Tomcat IBM SSL Provider


It mostly works in 4.1.26 (you still need the JSSE jar, but Tomcat won't use
it).  It should work completely in 4.1.27.  If you are impatient, you can
always grap the CVS code from
jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net/jsse and
compile it.

To work with the IBM JVM, you also need to remember to set
'alogrithm=IbmX509' in the SocketFactory element in server.xml.

McClure, Timothy J(IndSys, GE Interlogix) [EMAIL PROTECTED] wrote in
message
news:[EMAIL PROTECTED]
I am running Tomcat on AIX using JVM 1.4.  When Tomcat comes up with SSL
enabled it is looking for the Sun provider.  I copied the Sun JSSE 1.3 jar
into the Tomcat lib and this error went away.  However I am having problems
because I generated the certificate using the AIX keytool which used the IBM
provider.  This causes and IO Exception because the Sun provider is trying
to use the certificate created by the IBM provider.  The bottom line is how
do I get Tomcat to use IBM as it's SSL provider

Tim McClure
[EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Tomcat IBM SSL Provider

2003-07-22 Thread McClure, Timothy J(IndSys, GE Interlogix)
We are using what I thought was the lastest 4.1.24.  I did not see an option for 
download 4.1.26 on the jakarta web page.

Tim

-Original Message-
From: Bill Barker [mailto:[EMAIL PROTECTED]
Sent: Monday, July 21, 2003 11:09 PM
To: [EMAIL PROTECTED]
Subject: Re: Tomcat IBM SSL Provider


It mostly works in 4.1.26 (you still need the JSSE jar, but Tomcat won't use
it).  It should work completely in 4.1.27.  If you are impatient, you can
always grap the CVS code from
jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net/jsse and
compile it.

To work with the IBM JVM, you also need to remember to set
'alogrithm=IbmX509' in the SocketFactory element in server.xml.

McClure, Timothy J(IndSys, GE Interlogix) [EMAIL PROTECTED] wrote in
message
news:[EMAIL PROTECTED]
I am running Tomcat on AIX using JVM 1.4.  When Tomcat comes up with SSL
enabled it is looking for the Sun provider.  I copied the Sun JSSE 1.3 jar
into the Tomcat lib and this error went away.  However I am having problems
because I generated the certificate using the AIX keytool which used the IBM
provider.  This causes and IO Exception because the Sun provider is trying
to use the certificate created by the IBM provider.  The bottom line is how
do I get Tomcat to use IBM as it's SSL provider

Tim McClure
[EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Tomcat IBM SSL Provider

2003-07-22 Thread Bill Barker
4.1.26 is currently in it's evaluation period to determine what it's
stability rating will be.  The official release is likely to be the end of
the week, or early next week.  In the mean time, it is currently living at
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.26-alpha/,
for anyone that wants to help out in the evaluation.  Don't be scared off by
the alpha label:  That's just what it gets called until the evaluation
period is over.

McClure, Timothy J(IndSys, GE Interlogix) [EMAIL PROTECTED] wrote in
message
news:[EMAIL PROTECTED]
We are using what I thought was the lastest 4.1.24.  I did not see an option
for download 4.1.26 on the jakarta web page.

Tim

-Original Message-
From: Bill Barker [mailto:[EMAIL PROTECTED]
Sent: Monday, July 21, 2003 11:09 PM
To: [EMAIL PROTECTED]
Subject: Re: Tomcat IBM SSL Provider


It mostly works in 4.1.26 (you still need the JSSE jar, but Tomcat won't use
it).  It should work completely in 4.1.27.  If you are impatient, you can
always grap the CVS code from
jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net/jsse and
compile it.

To work with the IBM JVM, you also need to remember to set
'alogrithm=IbmX509' in the SocketFactory element in server.xml.

McClure, Timothy J(IndSys, GE Interlogix) [EMAIL PROTECTED] wrote in
message
news:[EMAIL PROTECTED]
I am running Tomcat on AIX using JVM 1.4.  When Tomcat comes up with SSL
enabled it is looking for the Sun provider.  I copied the Sun JSSE 1.3 jar
into the Tomcat lib and this error went away.  However I am having problems
because I generated the certificate using the AIX keytool which used the IBM
provider.  This causes and IO Exception because the Sun provider is trying
to use the certificate created by the IBM provider.  The bottom line is how
do I get Tomcat to use IBM as it's SSL provider

Tim McClure
[EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Tomcat IBM SSL Provider

2003-07-21 Thread Bill Barker
It mostly works in 4.1.26 (you still need the JSSE jar, but Tomcat won't use
it).  It should work completely in 4.1.27.  If you are impatient, you can
always grap the CVS code from
jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net/jsse and
compile it.

To work with the IBM JVM, you also need to remember to set
'alogrithm=IbmX509' in the SocketFactory element in server.xml.

McClure, Timothy J(IndSys, GE Interlogix) [EMAIL PROTECTED] wrote in
message
news:[EMAIL PROTECTED]
I am running Tomcat on AIX using JVM 1.4.  When Tomcat comes up with SSL
enabled it is looking for the Sun provider.  I copied the Sun JSSE 1.3 jar
into the Tomcat lib and this error went away.  However I am having problems
because I generated the certificate using the AIX keytool which used the IBM
provider.  This causes and IO Exception because the Sun provider is trying
to use the certificate created by the IBM provider.  The bottom line is how
do I get Tomcat to use IBM as it's SSL provider

Tim McClure
[EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]