Ok, let me try to post something that isn't gibberish for the non believers. :-) This is my setup.
I have AIX 5.3. I'm running IBM JVM 1.4.2, which as we all know includes JSSE by default. I'm using the default java.security file, which is pre-configured for the IBM JSSE providers. ./java -version java version "1.4.2" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2) Classic VM (build 1.4.2, J2RE 1.4.2 IBM AIX build ca142-20040917 (JIT enabled: jitc)) Here is the manifest file for the JBoss run.jar. I believe this should give a good understanding of which version of JBoss I'm using. Manifest-Version: 1.0 Specification-Title: JBoss Created-By: 1.4.2_05-b04 (Sun Microsystems Inc.) Specification-Version: 3.2.6 Implementation-Vendor-Id: http://www.jboss.org/ Implementation-URL: http://www.jboss.org/ Class-Path: ../client/getopt.jar Ant-Version: Apache Ant 1.6.2 Main-Class: org.jboss.Main Implementation-Title: JBoss [WonderLand] Specification-Vendor: JBoss (http://www.jboss.org/) Implementation-Version: 3.2.6 (build: CVSTag=JBoss_3_2_6 date=20041014 0106) Implementation-Vendor: JBoss.org I've generated a keystore, which works fine on Linux and Windows under JBoss, so I know the keystore is fine. I've modified server\default\server\deploy\jbossweb-tomcat50.sar\server.xml to include the following section: | <Connector port="8443" minProcessors="5" maxProcessors="200" | enableLookups="true" disableUploadTimeout="true" | keystoreFile="${jboss.server.home.dir}/conf/.keystore" | keystorePass="changeit" | acceptCount="200" debug="0" scheme="https" secure="true" | clientAuth="false" sslProtocol="TLS" /> | I've modified jboss-service.xml by switching the JaasSecurityManagerService to use the JaasSecurityDomain instead of the JassSecurityManager. Here is what that looks like in the file. | <mbean code="org.jboss.security.plugins.JaasSecurityManagerService" | name="jboss.security:service=JaasSecurityManager"> | <attribute name="SecurityManagerClassName"> | org.jboss.security.plugins.JaasSecurityDomain | </attribute> | </mbean> | I've also modified jboss-service.xml by adding the mbean block for the JaasSecurityDomain. I've added the attribute to disable loading the Sun JSSE as recommended by the documentation when using JVM version 1.4.2 or a non-Sun JVM. That code block looks like this: | <mbean code="org.jboss.security.plugins.JaasSecurityDomain" | name="Security:service=JaasSecurityDomain,domain=TomcatSSL"> | <depends>jboss.security:service=JaasSecurityManager</depends> | <constructor> | <arg type="java.lang.String" value="TomcatSSL" /> | </constructor> | <attribute name="KeyStoreURL">${jboss.server.home.dir}/conf/.keystore</attribute> | <attribute name="KeyStorePass">changeit</attribute> | <attribute name="LoadSunJSSEProvider">false</attribute> | </mbean> | When I start jboss, I get several errors. These errors lead me to believe that using the Sun JSSE is hard coded into JBoss as first noted by javaholic: 17 Nov 2005 09:32:08 [ERROR] [org.jboss.security.plugins.JaasSecurityDomain] - Initialization failed Security:service=JaasSecurityDomain,domain=TomcatSSL java.security.NoSuchAlgorithmException: Algorithm SunX509 not available at com.sun.net.ssl.SunJSSE_b.a(DashoA6275) at com.sun.net.ssl.KeyManagerFactory.getInstance(DashoA6275) at org.jboss.security.plugins.JaasSecurityDomain.createService(JaasSecurityDomain.java:383) at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:237) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:219) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ... 17 Nov 2005 09:32:27 [ERROR] [org.apache.coyote.http11.Http11Protocol] - Error initializing endpoint java.io.IOException: Algorithm SunX509 not available at org.apache.tomcat.util.net.jsse.JSSE14SocketFactory.init(JSSE14SocketFactory.java:127) at org.apache.tomcat.util.net.jsse.JSSESocketFactory.createSocket(JSSESocketFactory.java:88) at org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoint.java:259) at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:137) at org.apache.coyote.tomcat5.CoyoteConnector.initialize(CoyoteConnector.java:1429) at org.jboss.web.tomcat.tc5.StandardService.initialize(StandardService.java:612) at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:2384) at org.apache.catalina.startup.Catalina.load(Catalina.java:507) at org.apache.catalina.startup.Catalina.start(Catalina.java:548) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) ... Now, I've taken the time to be as clear as I possibly can. If I've left out something you would like to have posted, just ask and I'll make it available. Basically telling users that they don't have a clue what they are doing doesn't help anyone. I would appreciate it if someone could provide thorough explaination of what I should try to resolve this issue. -- tale View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3907670#3907670 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3907670 ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
