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.crypto.provider.SunJCE
security.provider.5=sun.security.jgss.SunProvider
Why is that? When I run from the command line, I do get SunJCE. That is the difference.
At 07:26 AM 3/27/2004, you wrote:
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.security.Security.getEngineClassName(Security.java:595) java.security.Security.getImpl(Security.java:1044) java.security.KeyPairGenerator.getInstance(KeyPairGenerator.java:146) org.apache.jsp.TEST_KEYPAIR_jsp._jspService(TEST_KEYPAIR_jsp.java:58) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:204)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
I can run the DH generator from the command line. So, the DH KeyPairGenerator IS available. I have no trouble with Resin 2.1.x. What is up? Come on you guys, give me a hand here. The documentation indicates that I should not be having a problem.
