[
https://issues.apache.org/activemq/browse/SMX4-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46211#action_46211
]
Jamie Goodyear commented on SMX4-133:
-------------------------------------
The camel project makes use of crypto provider settings just for IBM JDK, I may
be able to reuse their work around.
Grep for IBM crypto providers in here:
http://svn.apache.org/repos/asf/servicemix/components/bindings/servicemix-cxf-bc/trunk/pom.xml
> WS Security Test failing on AIX
> -------------------------------
>
> Key: SMX4-133
> URL: https://issues.apache.org/activemq/browse/SMX4-133
> Project: ServiceMix 4
> Issue Type: Test
> Affects Versions: 4.0-m2
> Environment: AIX 5.3
> Java 1.5
> Reporter: Jamie Goodyear
> Assignee: Jamie Goodyear
>
> The test case "org.apache.servicemix.camel.nmr.ws.security.WSSecurityTest" is
> failing on AIX.
> In the first fail scenario the test case can not find the jaxb libraries, in
> the second scenario the IBM JDK security providers are not being found. Both
> issues are related to differences in IBM JDK and SUN SDK. Please note that
> even with jaxp-ri.jar added to classpath the providers list will have to be
> adjusted.
> A more permanent solution will need to be devised to allow the IBM Java
> security providers be re-configured via pom instead of configuring the JDK's
> security file manually before maven build invocation.
> Two part work around:
> 1) Add to camel/servicemix-camel/pom.xml the dependency for jaxp-ri.jar (see
> smx4-128 for more details).
> 2) In ${JAVA_HOME}/jre/lib/security/java.security update the following
> (important part here is moving the crypto provider to first position in list):
> {noformat}
> #
> # List of providers and their preference orders (see above):
> #
> #security.provider.1=com.ibm.jsse2.IBMJSSEProvider2
> #security.provider.2=com.ibm.crypto.provider.IBMJCE
> #security.provider.3=com.ibm.security.jgss.IBMJGSSProvider
> #security.provider.4=com.ibm.security.cert.IBMCertPath
> #security.provider.5=com.ibm.security.sasl.IBMSASL
> ## Work around for IBM JDK to be compatible with Sun SDK ##
> security.provider.1=com.ibm.crypto.provider.IBMJCE
> security.provider.2=com.ibm.jsse.IBMJSSEProvider
> security.provider.3=com.ibm.jsse2.IBMJSSEProvider2
> security.provider.4=com.ibm.security.jgss.IBMJGSSProvider
> security.provider.5=com.ibm.security.cert.IBMCertPath
> security.provider.6=com.ibm.security.sasl.IBMSASL
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
