February 2012 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-3287) Deployment descriptor support for declaring jbossws-config-file / jbossws-config-name

by Alessio Soldano (JIRA)

Deployment descriptor support for declaring jbossws-config-file / jbossws-config-name ------------------------------------------------------------------------------------- Key: JBWS-3287 URL: https://issues.jboss.org/browse/JBWS-3287 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration, jbossws-native Reporter: Alessio Soldano Fix For: jbossws-native-4.1, jbossws-cxf-4.1 The jaxws endpoint configuration is currently declared through the @EndpointConfig annotation. The jbossws-native used to support declaring the same through context-params in the servlet web.xml. We should allow the same (perhaps even for ejb descriptor). For the jbws-cxf stack that probably implies early looking at the parameters when creating/rewriting the web.xml, as the endpoint publish (which needs those params) happens at bus startup in BusDeploymentAspect (deploy time, not runtime / when the endpoint servlet is first called) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
2
0 / 0

[JBoss JIRA] (JBWS-3383) WS-sec truststore/keystore urls should be obtained from the central security configuration

by Richard Opalka (Created) (JIRA)

WS-sec truststore/keystore urls should be obtained from the central security configuration ------------------------------------------------------------------------------------------ Key: JBWS-3383 URL: https://issues.jboss.org/browse/JBWS-3383 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: Anil Saldhana wrote: Ensure that the ws-sec truststore/keystore urls are obtained from the central security configuration. Rely on the from https://docs.jboss.org/author/display/AS7/Security+subsystem+configuration Reporter: Richard Opalka Assignee: Alessio Soldano Fix For: jbossws-native-4.0, jbossws-cxf-4.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
4
0 / 0

[JBoss JIRA] (JBWS-3443) Add configurable per client SSL parameters

by Alex O (JIRA)

Alex O created JBWS-3443: ---------------------------- Summary: Add configurable per client SSL parameters Key: JBWS-3443 URL: https://issues.jboss.org/browse/JBWS-3443 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.4.1 Reporter: Alex O Currently, when web service clients exist inside a Jboss deployment (war, ear, etc), they explicitly rely on SSL settings from javax.ssl in the System.Properties() collection. This is global and affects all web service clients in the container. This can be problematic for obvious reasons, different clients calling different endpoints, possibly with different truststores. In addition, for web service clients that rely on HTTP client-cert for authentication, different certificates can be used for each client. We're specifically talking only about transport security here. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2070) Add attachment interop endpoint for MTOM and SwaRef

by Heiko Braun (JIRA)

Add attachment interop endpoint for MTOM and SwaRef --------------------------------------------------- Key: JBWS-2070 URL: http://jira.jboss.com/jira/browse/JBWS-2070 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Heiko Braun -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
8
0 / 0

[JBoss JIRA] Created: (JBWS-2833) WebServiceContext#getUserPrincipal() returns null when a service is protected by "Standard WSSecurity Endpoint"

by Morten Andersen (JIRA)

WebServiceContext#getUserPrincipal() returns null when a service is protected by "Standard WSSecurity Endpoint" --------------------------------------------------------------------------------------------------------------- Key: JBWS-2833 URL: https://jira.jboss.org/jira/browse/JBWS-2833 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: ws-security Affects Versions: jbossws-native-3.1.2 Environment: jboss-5.1.0.GA (i.e. JBoss Web Services version 3.1.2.GA) java 1.6 Reporter: Morten Andersen When exposing a webservice using the "@WebServiceProvider" annotation, and protecting it with WSSE username token the WebServiceContext#userPrincipal is not set. The WEB-INF/jboss-wsse-server.xml is configured as described here: http://www.jboss.org/community/wiki/JBossWS-WS-Securityoptions#POJO_Endpo... Although this does not really seem to be enough, as it is also required to have META-INF/standard-jaxws-endpoint-config.xml file with only the "Standard WSSecurity Endpoint" on the server to actually enforce the authentication of the username token. Attached: * wstest.war: example war - exposing one webservice (compiled from the content of server.zip) * server.zip: source for the wstest.war * client.zip: simple client for the server, sending a username token. Reproducing the problem: 1) deploy wstest.war to a jboss 5.1.0 2) open the run.sh in the client.zip, and set the JBOSS_5 to fit your installation. It the server is not listening on 8080, modify the url in the client source (WsExampleClient.java). 3) compile and run the client, by running ./run.sh 4) inspect the server log. If this says: "[INFO] Principal = null" we have the problem (expected principal = admin) Server code: * service: server.zip:src/main/java/org/example/WsExample.java * wsdl: server.zip:src/main/webapp/WEB-INF/wsdl * wsse-config: server.zip:src/main/webapp/WEB-INF/jboss-wsse-server.xml * wsse-config2: server.zip:src/main/webapp/META-INF/standard-jaxws-endpoint-config.xml It seems that "wsse-config2" is required. If this is not present, it is possible for the client to send any client credentials it want (or leave them out) and it will still get admission to the service. Other areas where this has been discussed: * http://www.jboss.org/index.html?module=bb&op=viewtopic&t=127582&postdays=... * http://www.jboss.org/community/wiki/jbosssecuritytokenservice#comment-2075 (in relation to the same problem in the JBoss STS) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBWS-3072) The wsdl part generated for fault message is not valid

by Jim Ma (JIRA)

The wsdl part generated for fault message is not valid ------------------------------------------------------ Key: JBWS-3072 URL: https://jira.jboss.org/browse/JBWS-3072 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Jim Ma Assignee: Jim Ma -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] (JBWS-3407) Client aggregation module for Native stack

by Alessio Soldano (Created) (JIRA)

Client aggregation module for Native stack ------------------------------------------ Key: JBWS-3407 URL: https://issues.jboss.org/browse/JBWS-3407 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration, jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-4.0.1 We either need a module similar to org.jboss.ws.cxf.jbossws-cxf-client:main but for native stack or clear directions in the doc for what to use with native stack installed on AS7. The xts module dependency also probably needs to be fixed to be able to work with native stack too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-2744) Dispatch and Config Provider via System Properties and/or a Properties file

by Anil Saldhana (JIRA)

Dispatch and Config Provider via System Properties and/or a Properties file --------------------------------------------------------------------------- Key: JBWS-2744 URL: https://jira.jboss.org/jira/browse/JBWS-2744 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Anil Saldhana The Dispatch seems to be an important JAXWS client construct. It does not provide everything that any JBossWS user needs. Hence there are chances where he may have to cast the dispatch to ConfigProvider and provide the additional settings as outlined in the forum thread. For this reason, I suggest adding a properties file on the classpath and one setting that can be done via system property. The DispatchImpl implementation needs to handle this one system prop and use the associated properties file to get the settings. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
8
0 / 0

[JBoss JIRA] Created: (JBWS-3311) Make SwapableMemoryDataSource.maxMemorySize Configurable

by Kyle Lape (JIRA)

Make SwapableMemoryDataSource.maxMemorySize Configurable -------------------------------------------------------- Key: JBWS-3311 URL: https://issues.jboss.org/browse/JBWS-3311 Project: JBoss Web Services Issue Type: Enhancement Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Kyle Lape Assignee: Mustafa Musaji Make the maxMemorySize configurable by a system property. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
2
0 / 0

[JBoss JIRA] (JBWS-3376) Introduce jboss-webservices.xml DD

by Richard Opalka (Created) (JIRA)

Introduce jboss-webservices.xml DD ---------------------------------- Key: JBWS-3376 URL: https://issues.jboss.org/browse/JBWS-3376 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-4.0, jbossws-cxf-4.0 It's needed for customization of webservices.xml <webservices> <context-root/>? <config-name/>? <config-file/>? <webservice-description>* <webservice-description-name/> <wsdl-publish-location/> </webservice-description> </webservices> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues February 2012