January 2014 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3738) Expand WS-Trust / STS test coverage and documentation

by R Searls (JIRA)

[ https://issues.jboss.org/browse/JBWS-3738?page=com.atlassian.jira.plugin.... ] R Searls commented on JBWS-3738: -------------------------------- Committed tests for CALLBACK_HANDLER and SIGNATURE_USERNAME attributes Committed revision 18270. > Expand WS-Trust / STS test coverage and documentation > ----------------------------------------------------- > > Key: JBWS-3738 > URL: https://issues.jboss.org/browse/JBWS-3738 > Project: JBoss Web Services > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: R Searls > Fix For: jbossws-cxf-4.3 > > > We should possibly cover more WS-Trust/STS scenarios in the testsuite (different SAML tokens, etc.) and expand the documentation accordingly. -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3662) dynamic registration of Bouncy Castle JCE provider in cxf specific tests

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/JBWS-3662?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda commented on JBWS-3662: ----------------------------------------- [~asoldano] +1 > dynamic registration of Bouncy Castle JCE provider in cxf specific tests > ------------------------------------------------------------------------ > > Key: JBWS-3662 > URL: https://issues.jboss.org/browse/JBWS-3662 > Project: JBoss Web Services > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.1.3, jbossws-cxf-4.2 > Reporter: Petr Sakař > Assignee: Alessio Soldano > Priority: Minor > Fix For: jbossws-cxf-4.3 > > Attachments: patch_jbossws_cxf_specific_tests_bc_provider_dynamic_registration.v2.txt > > > currently the SignEncryptGCMTestCase requires static registration of Bouncy Castle JCE provider in JRE. The patch removes this need -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3662) dynamic registration of Bouncy Castle JCE provider in cxf specific tests

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3662?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3662: --------------------------------------- ~rsvoboda we can do that if you want > dynamic registration of Bouncy Castle JCE provider in cxf specific tests > ------------------------------------------------------------------------ > > Key: JBWS-3662 > URL: https://issues.jboss.org/browse/JBWS-3662 > Project: JBoss Web Services > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.1.3, jbossws-cxf-4.2 > Reporter: Petr Sakař > Assignee: Alessio Soldano > Priority: Minor > Fix For: jbossws-cxf-4.3 > > Attachments: patch_jbossws_cxf_specific_tests_bc_provider_dynamic_registration.v2.txt > > > currently the SignEncryptGCMTestCase requires static registration of Bouncy Castle JCE provider in JRE. The patch removes this need -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3662) dynamic registration of Bouncy Castle JCE provider in cxf specific tests

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/JBWS-3662?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda commented on JBWS-3662: ----------------------------------------- [~asoldano] will you backport changes from r18269 to 4.2.x branch ? > dynamic registration of Bouncy Castle JCE provider in cxf specific tests > ------------------------------------------------------------------------ > > Key: JBWS-3662 > URL: https://issues.jboss.org/browse/JBWS-3662 > Project: JBoss Web Services > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.1.3, jbossws-cxf-4.2 > Reporter: Petr Sakař > Assignee: Alessio Soldano > Priority: Minor > Fix For: jbossws-cxf-4.3 > > Attachments: patch_jbossws_cxf_specific_tests_bc_provider_dynamic_registration.v2.txt > > > currently the SignEncryptGCMTestCase requires static registration of Bouncy Castle JCE provider in JRE. The patch removes this need -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3749) update build-testsuite.xml to reflect new location of netty module in wildfly 8.0.0

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3749?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3749: ---------------------------------- Fix Version/s: jbossws-cxf-4.3 > update build-testsuite.xml to reflect new location of netty module in wildfly 8.0.0 > ----------------------------------------------------------------------------------- > > Key: JBWS-3749 > URL: https://issues.jboss.org/browse/JBWS-3749 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: R Searls > Assignee: R Searls > Labels: netty, testsuite, wildfly > Fix For: jbossws-cxf-4.3 > > > The module location of netty has changed wildfly 8.0.0. It was located in > ${jboss.home}/modules/system/layers/base/org/jboss/netty/main/ > its now located in > ${jboss.home}/modules/system/layers/base/io/netty/main/ > File build-testsuite.xml needs to be updated to reflect this so testsuite will run. -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3749) update build-testsuite.xml to reflect new location of netty module in wildfly 8.0.0

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3749?page=com.atlassian.jira.plugin.... ] Alessio Soldano edited comment on JBWS-3749 at 1/21/14 9:57 AM: ---------------------------------------------------------------- URL: https://svn.jboss.org/repos/jbossws/stack/cxf/trunk/modules Committed revision 18226. https://source.jboss.org/changelog/JBossWS?cs=18226 was (Author: rsearls): URL: https://svn.jboss.org/repos/jbossws/stack/cxf/trunk/modules Committed revision 18226. > update build-testsuite.xml to reflect new location of netty module in wildfly 8.0.0 > ----------------------------------------------------------------------------------- > > Key: JBWS-3749 > URL: https://issues.jboss.org/browse/JBWS-3749 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: R Searls > Assignee: R Searls > Labels: netty, testsuite, wildfly > Fix For: jbossws-cxf-4.3 > > > The module location of netty has changed wildfly 8.0.0. It was located in > ${jboss.home}/modules/system/layers/base/org/jboss/netty/main/ > its now located in > ${jboss.home}/modules/system/layers/base/io/netty/main/ > File build-testsuite.xml needs to be updated to reflect this so testsuite will run. -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3574) SignEncryptGCMTestCase fails even if Bouncy Castle is installed

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3574?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3574: --------------------------------------- For the records, see https://issues.jboss.org/browse/JBWS-3662?focusedCommentId=12937555&page=... > 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 > Assignee: Richard Opalka > 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3662) dynamic registration of Bouncy Castle JCE provider in cxf specific tests

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3662?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3662: ---------------------------------- Fix Version/s: jbossws-cxf-4.3 > dynamic registration of Bouncy Castle JCE provider in cxf specific tests > ------------------------------------------------------------------------ > > Key: JBWS-3662 > URL: https://issues.jboss.org/browse/JBWS-3662 > Project: JBoss Web Services > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.1.3, jbossws-cxf-4.2 > Reporter: Petr Sakař > Priority: Minor > Fix For: jbossws-cxf-4.3 > > Attachments: patch_jbossws_cxf_specific_tests_bc_provider_dynamic_registration.v2.txt > > > currently the SignEncryptGCMTestCase requires static registration of Bouncy Castle JCE provider in JRE. The patch removes this need -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3702) Replace sun http server with undertow

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3702?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3702: --------------------------------------- [~ctomc] Jim has been working on this, so I've moved it again to 4.3 > Replace sun http server with undertow > ------------------------------------- > > Key: JBWS-3702 > URL: https://issues.jboss.org/browse/JBWS-3702 > Project: JBoss Web Services > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Tomaz Cerar > Assignee: Jim Ma > Priority: Minor > Fix For: jbossws-cxf-4.3 > > > It would be really nice if we could get rid of sun http server. > currently webservices are only user in wildfly dependancy tree that still use it. -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3702) Replace sun http server with undertow

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3702?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3702: ---------------------------------- Fix Version/s: jbossws-cxf-4.3 (was: jbossws-cxf-4.4) > Replace sun http server with undertow > ------------------------------------- > > Key: JBWS-3702 > URL: https://issues.jboss.org/browse/JBWS-3702 > Project: JBoss Web Services > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Tomaz Cerar > Assignee: Jim Ma > Priority: Minor > Fix For: jbossws-cxf-4.3 > > > It would be really nice if we could get rid of sun http server. > currently webservices are only user in wildfly dependancy tree that still use it. -- 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

10 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues January 2014