September 2013 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3703) Early initialize WSSConfig (including BouncyCaste JCE provider registration)

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3703?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3703: ---------------------------------- Description: We should move the WSSConfig init earlier in the WS subsystem startup. Moreover on WildFly we have BouncyCastle JCE provider in org.bouncycastle module [1], so we can set a proper module dependency and avoid requiring the current JDK to have BC installed. [1] https://github.com/wildfly/wildfly/commit/81bdfd083d855ded4bb6ce7ea1d5679... was: We should move the WSSConfig init earlier in the WS subsystem startup. Moreover on WildFly we have BouncyCastle JCE provider in org.bouncycastle module, so we can set a proper module dependency and avoid requiring the current JDK to have BC installed. > Early initialize WSSConfig (including BouncyCaste JCE provider registration) > ---------------------------------------------------------------------------- > > Key: JBWS-3703 > URL: https://issues.jboss.org/browse/JBWS-3703 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2.1 > > > We should move the WSSConfig init earlier in the WS subsystem startup. > Moreover on WildFly we have BouncyCastle JCE provider in org.bouncycastle module [1], so we can set a proper module dependency and avoid requiring the current JDK to have BC installed. > [1] https://github.com/wildfly/wildfly/commit/81bdfd083d855ded4bb6ce7ea1d5679... -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3703) Early initialize WSSConfig (including BouncyCaste JCE provider registration)

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3703: ------------------------------------- Summary: Early initialize WSSConfig (including BouncyCaste JCE provider registration) Key: JBWS-3703 URL: https://issues.jboss.org/browse/JBWS-3703 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.2.1 We should move the WSSConfig init earlier in the WS subsystem startup. Moreover on WildFly we have BouncyCastle JCE provider in org.bouncycastle module, so we can set a proper module dependency and avoid requiring the current JDK to have BC installed. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3652) AbstractServerConfig.toIPv6URLFormat should not add brackets to IPv6 hostname

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3652?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3652: ---------------------------------- Fix Version/s: jbossws-cxf-4.2.1 (was: jbossws-cxf-4.3) > AbstractServerConfig.toIPv6URLFormat should not add brackets to IPv6 hostname > ----------------------------------------------------------------------------- > > Key: JBWS-3652 > URL: https://issues.jboss.org/browse/JBWS-3652 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Dillon Liang > Assignee: Jim Ma > Fix For: jbossws-cxf-4.2.1 > > > I am trying to specify the wsdl-host in AS7 webservice subsystem under IPv6 environment. I found if I provide the hostname, the web service will have wrong URL which has the brackets. This can be found in server.log. > The correct way to fix it is to determine whether the host parameter is a hostname or a pure IP address. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3610) Review of AccessController and PrivilegedAction use across JBossWS

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3610?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3610: ---------------------------------- Fix Version/s: jbossws-cxf-4.3 (was: jbossws-cxf-4.2.1) > Review of AccessController and PrivilegedAction use across JBossWS > ------------------------------------------------------------------ > > Key: JBWS-3610 > URL: https://issues.jboss.org/browse/JBWS-3610 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > See https://issues.jboss.org/browse/AS7-6316 description; most of that (especially on use of singletons for no param privileged actions) needs to be done on JBossWS codebase too. -- 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, 7 months

1
0
0 / 0

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

by Tomaz Cerar (JIRA)

Tomaz Cerar created JBWS-3702: --------------------------------- Summary: 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) Reporter: Tomaz Cerar Assignee: Alessio Soldano Priority: Minor 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3624) Create the test suite to check the WSI-BSP 1.1 compliance

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3624?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3624: ---------------------------------- Summary: Create the test suite to check the WSI-BSP 1.1 compliance (was: Create the test suite to check the wsi-bsp 11 compliance) > Create the test suite to check the WSI-BSP 1.1 compliance > --------------------------------------------------------- > > Key: JBWS-3624 > URL: https://issues.jboss.org/browse/JBWS-3624 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: productization > Reporter: Jim Ma > Assignee: Jim Ma > > Prepare the test suite to check the ws-i bsp compliance for jbossws-cxf/AS release -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3700) Unable to Check Roles in One-Way Operations

by Jim Ma (JIRA)

[ https://issues.jboss.org/browse/JBWS-3700?page=com.atlassian.jira.plugin.... ] Jim Ma edited comment on JBWS-3700 at 9/10/13 2:37 AM: ------------------------------------------------------- can you please try to configure the security constraint to servlet like the follow example to see if it works ? {code} <servlet> <servlet-name>HelloImpl</servlet-name> <servlet-class>org.jboss.test.ws.jaxws.jbws2307.HelloImpl</servlet-class> <load-on-startup>0</load-on-startup> <security-role-ref> <role-name>FRN</role-name> <role-link>friend</role-link> </security-role-ref> </servlet> <servlet-mapping> <servlet-name>HelloImpl</servlet-name> <url-pattern>/jaxws/Hello</url-pattern> </servlet-mapping> <session-config> <session-timeout>54</session-timeout> </session-config> <security-constraint> <web-resource-collection> <web-resource-name>WSHelloSecureService</web-resource-name> <url-pattern>/jaxws/*</url-pattern> <http-method>POST</http-method> </web-resource-collection> <auth-constraint> <role-name>friend</role-name> </auth-constraint> <user-data-constraint> <transport-guarantee>NONE</transport-guarantee> </user-data-constraint> </security-constraint> <login-config> <auth-method>BASIC</auth-method> <realm-name>default</realm-name> </login-config> <security-role> <role-name>friend</role-name> </security-role> {code} was (Author: jim.ma): can you please configure the security constraint to servlet like the follow example to see if it works ? {code} <servlet> <servlet-name>HelloImpl</servlet-name> <servlet-class>org.jboss.test.ws.jaxws.jbws2307.HelloImpl</servlet-class> <load-on-startup>0</load-on-startup> <security-role-ref> <role-name>FRN</role-name> <role-link>friend</role-link> </security-role-ref> </servlet> <servlet-mapping> <servlet-name>HelloImpl</servlet-name> <url-pattern>/jaxws/Hello</url-pattern> </servlet-mapping> <session-config> <session-timeout>54</session-timeout> </session-config> <security-constraint> <web-resource-collection> <web-resource-name>WSHelloSecureService</web-resource-name> <url-pattern>/jaxws/*</url-pattern> <http-method>POST</http-method> </web-resource-collection> <auth-constraint> <role-name>friend</role-name> </auth-constraint> <user-data-constraint> <transport-guarantee>NONE</transport-guarantee> </user-data-constraint> </security-constraint> <login-config> <auth-method>BASIC</auth-method> <realm-name>default</realm-name> </login-config> <security-role> <role-name>friend</role-name> </security-role> {code} > Unable to Check Roles in One-Way Operations > ------------------------------------------- > > Key: JBWS-3700 > URL: https://issues.jboss.org/browse/JBWS-3700 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.1.3 > Environment: All supported environments. > Reporter: Fernando Ribeiro > Assignee: Jim Ma > Fix For: jbossws-cxf-4.3 > > Attachments: jaxwssample-1.0.war > > > In any calls to one-way operations, the isUserInRole doesn't work as expected. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3700) Unable to Check Roles in One-Way Operations

by Jim Ma (JIRA)

[ https://issues.jboss.org/browse/JBWS-3700?page=com.atlassian.jira.plugin.... ] Jim Ma commented on JBWS-3700: ------------------------------ can you please configure the security constraint to servlet like the follow example to see if it works ? {code} <servlet> <servlet-name>HelloImpl</servlet-name> <servlet-class>org.jboss.test.ws.jaxws.jbws2307.HelloImpl</servlet-class> <load-on-startup>0</load-on-startup> <security-role-ref> <role-name>FRN</role-name> <role-link>friend</role-link> </security-role-ref> </servlet> <servlet-mapping> <servlet-name>HelloImpl</servlet-name> <url-pattern>/jaxws/Hello</url-pattern> </servlet-mapping> <session-config> <session-timeout>54</session-timeout> </session-config> <security-constraint> <web-resource-collection> <web-resource-name>WSHelloSecureService</web-resource-name> <url-pattern>/jaxws/*</url-pattern> <http-method>POST</http-method> </web-resource-collection> <auth-constraint> <role-name>friend</role-name> </auth-constraint> <user-data-constraint> <transport-guarantee>NONE</transport-guarantee> </user-data-constraint> </security-constraint> <login-config> <auth-method>BASIC</auth-method> <realm-name>default</realm-name> </login-config> <security-role> <role-name>friend</role-name> </security-role> {code} > Unable to Check Roles in One-Way Operations > ------------------------------------------- > > Key: JBWS-3700 > URL: https://issues.jboss.org/browse/JBWS-3700 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.1.3 > Environment: All supported environments. > Reporter: Fernando Ribeiro > Assignee: Jim Ma > Fix For: jbossws-cxf-4.3 > > Attachments: jaxwssample-1.0.war > > > In any calls to one-way operations, the isUserInRole doesn't work as expected. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3681) Add to testsuite profiles allowing to exclude tests requiring Bouncy Castle JCE provider or unlimited strength cryptography installed

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3681?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3681: ---------------------------------- Fix Version/s: jbossws-cxf-4.3 > Add to testsuite profiles allowing to exclude tests requiring Bouncy Castle JCE provider or unlimited strength cryptography installed > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBWS-3681 > URL: https://issues.jboss.org/browse/JBWS-3681 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2.1 > Reporter: Petr Sakař > Priority: Optional > Fix For: jbossws-cxf-4.3 > > Attachments: patch_jbossws_4.1.3_trunk_add_profiles_to_exclude_tests_related_to_JCE_Provider_BC_and_strong_cryptography.txt > > > Following tests require to pass java with installed BouncyCastle JCE Provider: > modules/testsuite/cxf-tests > org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples22xTestCase.test221 > org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples22xTestCase.test222 > org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples22xTestCase.test223 > org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples22xTestCase.test224 > org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase.test2314 > org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase.test2315 > org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase.test2324 > org.jboss.test.ws.jaxws.samples.wsse.policy.trust.WSTrustTestCase.test > org.jboss.test.ws.jaxws.samples.wsse.policy.trust.WSTrustTestCase.testUsingEPR > org.jboss.test.ws.jaxws.samples.wsse.policy.basic.SignEncryptGCMTestCase.testClientSide > org.jboss.test.ws.jaxws.samples.wsse.policy.basic.SignEncryptGCMTestCase.testClientSideUsingConfigProperties > org.jboss.test.ws.jaxws.samples.wsse.policy.basic.SignEncryptGCMTestCase.testServerSideUsingConfigProperties > Following tests require to pass java with installed strong cryptography policy files: > org.jboss.test.ws.jaxws.samples.wsse.policy.basic.SignEncryptGCMTestCase.testClientSide > org.jboss.test.ws.jaxws.samples.wsse.policy.basic.SignEncryptGCMTestCase.testClientSideUsingConfigProperties > org.jboss.test.ws.jaxws.samples.wsse.policy.basic.SignEncryptGCMTestCase.testServerSideUsingConfigProperties > > The profile exclude-integration-tests-BC-related and exclude-integration-tests-unlimited-strength-related allow to exclude these tests, so the testsuite can be successfully run without these tests. > The profiles are by default switched off. > To switch on profile use command line property -Dexclude-integration-tests-BC-related and -Dexclude-integration-tests-unlimited-strength-related -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3676) Minor dependency cleanup in jbossws-common

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3676?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3676: ---------------------------------- Fix Version/s: jbossws-cxf-4.3 > Minor dependency cleanup in jbossws-common > ------------------------------------------ > > Key: JBWS-3676 > URL: https://issues.jboss.org/browse/JBWS-3676 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: productization > Reporter: Paul Gier > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > Attachments: 0001-JBWS-3676-Fix-dep-issue-in-jaxrpc-api.patch > > > jbossws-common has an undeclared compile time dependency on javax.xml:jaxrpc which is pulled in transitively via the ejb api. And it appears ejb-api is not used. > This should be changed to use the org.jboss.specs project version of the jaxrpc api directly. -- 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, 7 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 September 2013