You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Jamie Goodyear (JIRA)" <ji...@apache.org> on 2008/10/06 20:32:52 UTC
[jira] Created: (SMX4-133) WS Security Test failing on AIX
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
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):
#
# 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SMX4-133) WS Security Test failing on AIX
Posted by "Jamie Goodyear (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46287#action_46287 ]
Jamie Goodyear commented on SMX4-133:
-------------------------------------
I've worked out a solution based in part upon the approach take in servicemix-cxf-bc component, however in this case an alternate java.security property file will be forced upon test cases run by surefire.
The key to this solution is the use a double equals (==) when specifying the new properties file. If you use a single equals (=) then it appends to the default property file, thereby not picking up changes required for the IBM JDK.
Please note that the new java.security properties file will only be used on IBM JDK, all other JVMs will use their own default values.
Will attach patch once fully tested on AIX and a non-IBM JDK system.
> 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.
[jira] Updated: (SMX4-133) WS Security Test failing on AIX
Posted by "Jamie Goodyear (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jamie Goodyear updated SMX4-133:
--------------------------------
Attachment: smx4-133.txt
Contains modifications to camel/servicemix-camel/pom.xml to add ibm jdk profile that will force surefire to use ibm.jdk15.security properties file with IBM JDK.
Tested on AIX v5.3 and MacOSX 10.5.5.
> 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
> Attachments: smx4-133.txt
>
>
> 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.
[jira] Resolved: (SMX4-133) WS Security Test failing on AIX
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang resolved SMX4-133.
-------------------------------
Fix Version/s: 4.0-m2
Resolution: Fixed
patch applied on behalf of Jamie with thanks
Sending servicemix-camel/pom.xml
Adding servicemix-camel/src/test/resources/ibm.jdk15.security
Transmitting file data ..
Committed revision 703339.
> 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
> Fix For: 4.0-m2
>
> Attachments: smx4-133.txt
>
>
> 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.
[jira] Assigned: (SMX4-133) WS Security Test failing on AIX
Posted by "Jamie Goodyear (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jamie Goodyear reassigned SMX4-133:
-----------------------------------
Assignee: Jamie Goodyear
> 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.
[jira] Work started: (SMX4-133) WS Security Test failing on AIX
Posted by "Jamie Goodyear (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on SMX4-133 started by Jamie Goodyear.
> 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
> Attachments: smx4-133.txt
>
>
> 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.
[jira] Work stopped: (SMX4-133) WS Security Test failing on AIX
Posted by "Jamie Goodyear (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on SMX4-133 stopped by Jamie Goodyear.
> 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
> Attachments: smx4-133.txt
>
>
> 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.
[jira] Commented: (SMX4-133) WS Security Test failing on AIX
Posted by "Jamie Goodyear (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (SMX4-133) WS Security Test failing on AIX
Posted by "Jamie Goodyear (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jamie Goodyear updated SMX4-133:
--------------------------------
Description:
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}
was:
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):
#
# 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
> 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
>
> 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.