[JBoss JIRA] (JBWS-3574) SignEncryptGCMTestCase fails even if Bouncy Castle is installed
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/JBWS-3574?page=com.atlassian.jira.plugin.... ]
Richard Opalka commented on JBWS-3574:
--------------------------------------
Works for me:
Running org.jboss.test.ws.jaxws.samples.wssePolicy.SignEncryptGCMTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 12.364 sec
My configuration was:
[supervoid][/home/ropalka/svn/jbossws/stack/cxf/branches/jbossws-cxf-3.1.2]>svn info
Path: .
Working Copy Root Path: /home/ropalka/svn/jbossws/stack/cxf/branches/jbossws-cxf-3.1.2
URL: https://svn.jboss.org/repos/jbossws/stack/cxf/branches/jbossws-cxf-3.1.2
Repository Root: https://svn.jboss.org/repos/jbossws
Repository UUID: 50344849-fb0f-0410-a53f-a94597aac05c
Revision: 17068
Node Kind: directory
Schedule: normal
Last Changed Author: alessio.soldano(a)jboss.com
Last Changed Rev: 17062
Last Changed Date: 2012-12-10 14:51:55 +0100 (Mon, 10 Dec 2012)
---
[supervoid][/home/ropalka/svn/jbossws/thirdparty/wss4j/branches/1_5_x-fixes]>svn info
Path: .
Working Copy Root Path: /home/ropalka/svn/jbossws/thirdparty/wss4j/branches/1_5_x-fixes
URL: https://svn.jboss.org/repos/jbossws/thirdparty/wss4j/branches/1_5_x-fixes
Repository Root: https://svn.jboss.org/repos/jbossws
Repository UUID: 50344849-fb0f-0410-a53f-a94597aac05c
Revision: 17068
Node Kind: directory
Schedule: normal
Last Changed Author: alessio.soldano(a)jboss.com
Last Changed Rev: 17028
Last Changed Date: 2012-11-20 13:44:54 +0100 (Tue, 20 Nov 2012)
---
[supervoid][/home/ropalka/svn/jbossas/branches/JBPAPP_5_1]>svn info
Path: .
Working Copy Root Path: /home/ropalka/svn/jbossas/branches/JBPAPP_5_1
URL: https://svn.jboss.org/repos/jbossas/branches/JBPAPP_5_1
Repository Root: https://svn.jboss.org/repos/jbossas
Repository UUID: 84be2c1e-ba19-0410-b317-a758671a6fc1
Revision: 113829
Node Kind: directory
Schedule: normal
Last Changed Author: pskopek
Last Changed Rev: 113813
Last Changed Date: 2012-11-15 16:54:12 +0100 (Thu, 15 Nov 2012)
---
[supervoid][/home/ropalka]>mvn -version
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.7.0_09
Java home: /home/ropalka/java/jdk/orcl/jdk1.7.0_09/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" version: "3.6.9-2.fc17.x86_64" arch: "amd64" Family: "unix"
---
[supervoid][/home/ropalka]>java -version
java version "1.7.0_09"
Java(TM) SE Runtime Environment (build 1.7.0_09-b05)
Java HotSpot(TM) 64-Bit Server VM (build 23.5-b02, mixed mode)
---
[supervoid][/home/ropalka]>uname -a
Linux supervoid 3.6.9-2.fc17.x86_64 #1 SMP Tue Dec 4 13:26:04 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
> SignEncryptGCMTestCase fails even if Bouncy Castle is installed
> ---------------------------------------------------------------
>
> Key: JBWS-3574
> URL: https://issues.jboss.org/browse/JBWS-3574
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf
> Affects Versions: jbossws-cxf-3.1.2
> Environment: JBoss Web Services - Stack CXF 3.1.2.SP12, Oracle JDK 1.7.0_09 with Bouncy Castle installed (both bcprov-ext-jdk15on-147.jar and bcprov-jdk15on-147.jar), RHEL 5 x86
> Reporter: Martin Vecera
> Attachments: TEST-org.jboss.test.ws.jaxws.samples.wssePolicy.SignEncryptGCMTestCase.xml
>
>
> I run WS-CXF integration test suite against SOA-P 5.3.1 and I faces issues with security tests due to missing Bouncy Castle installation. After installing it, there is still a test that fails:
> java.lang.Exception: Please check that the Bouncy Castle provider is installed.
> at org.jboss.test.ws.jaxws.samples.wssePolicy.SignEncryptGCMTestCase.test(SignEncryptGCMTestCase.java:65)
> Caused by: javax.xml.ws.soap.SOAPFaultException: Cannot encrypt data
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:146)
> at $Proxy38.sayHello(Unknown Source)
> at org.jboss.test.ws.jaxws.samples.wssePolicy.SignEncryptGCMTestCase.test(SignEncryptGCMTestCase.java:61)
> ... 30 more
> Caused by: org.apache.cxf.ws.policy.PolicyException: Cannot encrypt data
> at org.apache.cxf.ws.security.wss4j.policyhandlers.AbstractBindingBuilder.policyNotAsserted(AbstractBindingBuilder.java:283)
> at org.apache.cxf.ws.security.wss4j.policyhandlers.AsymmetricBindingHandler.doEncryption(AsymmetricBindingHandler.java:319)
> at org.apache.cxf.ws.security.wss4j.policyhandlers.AsymmetricBindingHandler.doSignBeforeEncrypt(AsymmetricBindingHandler.java:141)
> at org.apache.cxf.ws.security.wss4j.policyhandlers.AsymmetricBindingHandler.handleBinding(AsymmetricBindingHandler.java:90)
> at org.apache.cxf.ws.security.wss4j.PolicyBasedWSS4JOutInterceptor$PolicyBasedWSS4JOutInterceptorInternal.handleMessage(PolicyBasedWSS4JOutInterceptor.java:139)
> at org.apache.cxf.ws.security.wss4j.PolicyBasedWSS4JOutInterceptor$PolicyBasedWSS4JOutInterceptorInternal.handleMessage(PolicyBasedWSS4JOutInterceptor.java:77)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:516)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:313)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:265)
> at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
> ... 32 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBWS-3573) Review Coverity reports for JBossWS projects
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/JBWS-3573?page=com.atlassian.jira.plugin.... ]
Richard Opalka commented on JBWS-3573:
--------------------------------------
Yes vfsRoot not deserialized is intentional. We're using this de/serialization feature only in our tests
and I implemented Thread.currentThread().getContextClassloader() based workaround in getWsdlLocation() & getMappingLocation() methods (notice vfsRoot != null checks there)
> Review Coverity reports for JBossWS projects
> --------------------------------------------
>
> Key: JBWS-3573
> URL: https://issues.jboss.org/browse/JBWS-3573
> Project: JBoss Web Services
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: productization
> Reporter: Rostislav Svoboda
> Assignee: Alessio Soldano
> Fix For: jbossws-cxf-4.1.1, jbossws-native-4.1.1
>
>
> http://station5.brq.redhat.com:8080
> Analyzed trunks for:
> * JBossWS API
> * JBossWS SPI
> * JBossWS Common
> * JBossWS Common Tools
> * JBossWS CXF
> * JBossWS Native
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBWS-3574) SignEncryptGCMTestCase fails even if Bouncy Castle is installed
by Martin Vecera (JIRA)
[ https://issues.jboss.org/browse/JBWS-3574?page=com.atlassian.jira.plugin.... ]
Martin Vecera updated JBWS-3574:
--------------------------------
Attachment: TEST-org.jboss.test.ws.jaxws.samples.wssePolicy.SignEncryptGCMTestCase.xml
Attached surefire report.
> SignEncryptGCMTestCase fails even if Bouncy Castle is installed
> ---------------------------------------------------------------
>
> Key: JBWS-3574
> URL: https://issues.jboss.org/browse/JBWS-3574
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf
> Affects Versions: jbossws-cxf-3.1.2
> Environment: JBoss Web Services - Stack CXF 3.1.2.SP12, Oracle JDK 1.7.0_09 with Bouncy Castle installed (both bcprov-ext-jdk15on-147.jar and bcprov-jdk15on-147.jar), RHEL 5 x86
> Reporter: Martin Vecera
> Attachments: TEST-org.jboss.test.ws.jaxws.samples.wssePolicy.SignEncryptGCMTestCase.xml
>
>
> I run WS-CXF integration test suite against SOA-P 5.3.1 and I faces issues with security tests due to missing Bouncy Castle installation. After installing it, there is still a test that fails:
> java.lang.Exception: Please check that the Bouncy Castle provider is installed.
> at org.jboss.test.ws.jaxws.samples.wssePolicy.SignEncryptGCMTestCase.test(SignEncryptGCMTestCase.java:65)
> Caused by: javax.xml.ws.soap.SOAPFaultException: Cannot encrypt data
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:146)
> at $Proxy38.sayHello(Unknown Source)
> at org.jboss.test.ws.jaxws.samples.wssePolicy.SignEncryptGCMTestCase.test(SignEncryptGCMTestCase.java:61)
> ... 30 more
> Caused by: org.apache.cxf.ws.policy.PolicyException: Cannot encrypt data
> at org.apache.cxf.ws.security.wss4j.policyhandlers.AbstractBindingBuilder.policyNotAsserted(AbstractBindingBuilder.java:283)
> at org.apache.cxf.ws.security.wss4j.policyhandlers.AsymmetricBindingHandler.doEncryption(AsymmetricBindingHandler.java:319)
> at org.apache.cxf.ws.security.wss4j.policyhandlers.AsymmetricBindingHandler.doSignBeforeEncrypt(AsymmetricBindingHandler.java:141)
> at org.apache.cxf.ws.security.wss4j.policyhandlers.AsymmetricBindingHandler.handleBinding(AsymmetricBindingHandler.java:90)
> at org.apache.cxf.ws.security.wss4j.PolicyBasedWSS4JOutInterceptor$PolicyBasedWSS4JOutInterceptorInternal.handleMessage(PolicyBasedWSS4JOutInterceptor.java:139)
> at org.apache.cxf.ws.security.wss4j.PolicyBasedWSS4JOutInterceptor$PolicyBasedWSS4JOutInterceptorInternal.handleMessage(PolicyBasedWSS4JOutInterceptor.java:77)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:516)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:313)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:265)
> at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
> ... 32 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBWS-3574) SignEncryptGCMTestCase fails even if Bouncy Castle is installed
by Martin Vecera (JIRA)
Martin Vecera created JBWS-3574:
-----------------------------------
Summary: SignEncryptGCMTestCase fails even if Bouncy Castle is installed
Key: JBWS-3574
URL: https://issues.jboss.org/browse/JBWS-3574
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-cxf
Affects Versions: jbossws-cxf-3.1.2
Environment: JBoss Web Services - Stack CXF 3.1.2.SP12, Oracle JDK 1.7.0_09 with Bouncy Castle installed (both bcprov-ext-jdk15on-147.jar and bcprov-jdk15on-147.jar), RHEL 5 x86
Reporter: Martin Vecera
I run WS-CXF integration test suite against SOA-P 5.3.1 and I faces issues with security tests due to missing Bouncy Castle installation. After installing it, there is still a test that fails:
java.lang.Exception: Please check that the Bouncy Castle provider is installed.
at org.jboss.test.ws.jaxws.samples.wssePolicy.SignEncryptGCMTestCase.test(SignEncryptGCMTestCase.java:65)
Caused by: javax.xml.ws.soap.SOAPFaultException: Cannot encrypt data
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:146)
at $Proxy38.sayHello(Unknown Source)
at org.jboss.test.ws.jaxws.samples.wssePolicy.SignEncryptGCMTestCase.test(SignEncryptGCMTestCase.java:61)
... 30 more
Caused by: org.apache.cxf.ws.policy.PolicyException: Cannot encrypt data
at org.apache.cxf.ws.security.wss4j.policyhandlers.AbstractBindingBuilder.policyNotAsserted(AbstractBindingBuilder.java:283)
at org.apache.cxf.ws.security.wss4j.policyhandlers.AsymmetricBindingHandler.doEncryption(AsymmetricBindingHandler.java:319)
at org.apache.cxf.ws.security.wss4j.policyhandlers.AsymmetricBindingHandler.doSignBeforeEncrypt(AsymmetricBindingHandler.java:141)
at org.apache.cxf.ws.security.wss4j.policyhandlers.AsymmetricBindingHandler.handleBinding(AsymmetricBindingHandler.java:90)
at org.apache.cxf.ws.security.wss4j.PolicyBasedWSS4JOutInterceptor$PolicyBasedWSS4JOutInterceptorInternal.handleMessage(PolicyBasedWSS4JOutInterceptor.java:139)
at org.apache.cxf.ws.security.wss4j.PolicyBasedWSS4JOutInterceptor$PolicyBasedWSS4JOutInterceptorInternal.handleMessage(PolicyBasedWSS4JOutInterceptor.java:77)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:516)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:313)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:265)
at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
... 32 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBWS-3546) Support -a WSProvide option
by Alessio Soldano (JIRA)
Alessio Soldano created JBWS-3546:
-------------------------------------
Summary: Support -a WSProvide option
Key: JBWS-3546
URL: https://issues.jboss.org/browse/JBWS-3546
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jaxws-tools-maven-plugin
Reporter: Alessio Soldano
Fix For: jbossws-jaxws-tools-maven-plugin-1.1.1.GA
... while moving to JBossWS 4.1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBWS-3571) SOAPAddressWSDLParser does not process wsdl imports
by Alessio Soldano (JIRA)
Alessio Soldano created JBWS-3571:
-------------------------------------
Summary: SOAPAddressWSDLParser does not process wsdl imports
Key: JBWS-3571
URL: https://issues.jboss.org/browse/JBWS-3571
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-cxf
Reporter: Alessio Soldano
Fix For: jbossws-cxf-4.1.1
The SOAPAddressWSDLParser currently does not process wsdl imports, so it basically misses soap:address entries corresponding to bindings living in imported wsdl docs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months