Hmm, I just noticed that the following is commented out in jwsdp:
Could that be the source of the problem in some sense?
At 01:31 PM 3/27/2004, you wrote:
Djava.endorsed
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additio
Parser</jvm-options>'>
??? Why would extension jars have to be manually configured in
Tomcat? Thanks.
At 12:23 PM 3/27/2004, Bill Barker wrote:
- Original Message -
From: "Michael McGrady" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAI
- Original Message -
From: "Michael McGrady" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Saturday, March 27, 2004 8:46 AM
Subject: Re: java.security.NoSuchAlgorithmException in Tomcat SOLUTION
> For s
For some reason Tomcat is not seeing the com.sun.crypto.provider package in
jre/lib/ext. The work around is to put the SunJCE provider
(sunjce_provider.jar) into commons/lib of Tomcat and to then add the
provider manually with
Security.addProvider(new com.sun.crypto.provider.SunJCE()). Why t
When I run Security.getProviders() I do not get SunJCE, even though I have
the following in the java.security file:
security.provider.1=sun.security.provider.Sun
security.provider.2=com.sun.net.ssl.internal.ssl.Provider
security.provider.3=com.sun.rsajca.Provider
security.provider.4=com.sun.crypt
I am using j2se 1.4.2_04. When I attempt to run
java.security.KeyPairGenerator.getInstance("DH") in Tomcat, I get a stack
trace as follows:
java.security.NoSuchAlgorithmException: DH KeyPairGenerator not available
java.security.Security.getEngineClassName(Security.java:584)
java
