November 2010 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2379) Using a custom HandlerResolver on client while using WS-Security does not add ws-security header to soap envelope

by Yousuf Haider (JIRA)

Using a custom HandlerResolver on client while using WS-Security does not add ws-security header to soap envelope ----------------------------------------------------------------------------------------------------------------- Key: JBWS-2379 URL: https://jira.jboss.org/jira/browse/JBWS-2379 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: ws-security Affects Versions: jbossws-2.0.1.SP2 Environment: JBoss4.3 JDK1.5 Reporter: Yousuf Haider I have a webservice deployed as an EJB endpoint with the correct WS-Security Configuration (using UsernameToken) My standalone java client code looks like this: ReflectorEjbWsseApi port = null; Service service = (Service) Service.create(wsdlURL, serviceQName); service.setHandlerResolver(new CustomHandlerResolver); port = service.getPort(ReflectorEjbWsseApi.class); HandlerResolver hr = new HandlerResolver(); ((BindingProvider)port).getRequestContext().put(BindingProvider.USERNAME_PROPERTY, WebServiceConstants.USERNAME); ((BindingProvider)port).getRequestContext().put(BindingProvider.PASSWORD_PROPERTY, WebServiceConstants.PASSWORD); URL securityURL = new File("jboss-wsse-client.xml").toURL(); ((StubExt)port).setSecurityConfig(securityURL.toExternalForm()); ((StubExt) port).setConfigName("Standard WSSecurity Client"); ((BindingProvider)port).getRequestContext().put(StubExt.PROPERTY_AUTH_TYPE, StubExt.PROPERTY_AUTH_TYPE_WSSE); As you can see I am setting my own custom HandlerResolver. However by doing this I am somehow overriding the default HandlerChain which would have used the USERNAME_PROPERTY and PASSWORD_PROPERTY values and added the ws-security header to the soap message. When executing this code I get a SOAPFault from the server saying that the soap message does not contain a required header. javax.xml.ws.soap.SOAPFaultException: org.jboss.ws.core.CommonSOAPFaultException: This service requires <wsse:Security>, which is missing. If I don't set the handlerResolver by removing this line from my client: service.setHandlerResolver(new CustomHandlerResolver); the request goes through fine and I get a valid response. My own customhandlers do nothing but some logging activity. I should be able to use my own custom handlers with WS-Security. -- 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

13 years, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBWS-2695) Setting a new config at runtime the properties are not available to RemotingConnectionImpl

by Darran Lofthouse (JIRA)

Setting a new config at runtime the properties are not available to RemotingConnectionImpl ------------------------------------------------------------------------------------------ Key: JBWS-2695 URL: https://jira.jboss.org/jira/browse/JBWS-2695 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.2.0 Using the following to replace the configuration for the client: - ((StubExt)port).setConfigName("Custom Client Config","descriptors/jaxws-client-config.xml"); Handlers are updated as required, however the properties that are processed by RemotingConnectionImpl still use the original values. This is because the MessageContext obtains the config from the OperationMetaData as the custom config was not set when the MessageContext was created. -- 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

13 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBWS-3163) Upgrade to Apache CXF 2.3.1

by Alessio Soldano (JIRA)

Upgrade to Apache CXF 2.3.1 --------------------------- Key: JBWS-3163 URL: https://jira.jboss.org/browse/JBWS-3163 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-3.4.0 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3160) Release JBossWS 3.4.0.GA

by Alessio Soldano (JIRA)

Release JBossWS 3.4.0.GA ------------------------ Key: JBWS-3160 URL: https://jira.jboss.org/browse/JBWS-3160 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-native, productization Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-3.4.0, jbossws-native-3.4.0 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3159) SAAJ implementation does not set the correct NS prefix in SOAP header and body elements

by Jim Ma (JIRA)

SAAJ implementation does not set the correct NS prefix in SOAP header and body elements --------------------------------------------------------------------------------------- Key: JBWS-3159 URL: https://jira.jboss.org/browse/JBWS-3159 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.4.0.CR1 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-native-3.4.0 With native saaj implementation to create soap message from this string : <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><S:Header xmlns:S='http://schemas.xmlsoap.org/soap/envelopes'></S:Header><S:Body xmlns:S='http://schemas.xmlsoap.org/soap/envelopes'> <ns1:addItemResponse xmlns:ns1='http://org.jboss.ws/addressing/replyto'> <result>Mars Bar</result> </ns1:addItemResponse> </S:Body></env:Envelope> The created soap header and soap body are with prefix "env" . This caused some problem when ws security is enabled and soap header or body part is signed. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3156) Refactor ThreadLocalAwareWebserviceContext

by Richard Opalka (JIRA)

Refactor ThreadLocalAwareWebserviceContext ------------------------------------------ Key: JBWS-3156 URL: https://jira.jboss.org/browse/JBWS-3156 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration, jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-cxf-3.4.0, jbossws-native-3.4.0 Current ThreadLocalAwareWebServiceContext implementation is private class. In order to allow proper switchboard/jboss-injection integration this needs to be accessible from outside and have to be extracted to public class. Once this is done proper WebServiceContext resource provider can be implemented. -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3155) Implement support for anonymous attachments

by Richard Opalka (JIRA)

Implement support for anonymous attachments ------------------------------------------- Key: JBWS-3155 URL: https://jira.jboss.org/browse/JBWS-3155 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.4.0 "Anonymous attachments" are MIME attachments that might appear on the wire, but are not mapped to JAXWS method parameters/return types. This feature request will make these anonymous attachments to be accessible/provideable in JAXWS standard way - using - MessageContextJAXWS.INBOUND_MESSAGE_ATTACHMENTS - to access incoming anynymous attachments - MessageContextJAXWS.OUTBOUND_MESSAGE_ATTACHMENTS - to provide outgoing anynymous attachments -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3154) wsa:MessageID is missing in response message

by Jim Ma (JIRA)

wsa:MessageID is missing in response message -------------------------------------------- Key: JBWS-3154 URL: https://jira.jboss.org/browse/JBWS-3154 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native, ws-addressing Affects Versions: jbossws-native-3.4.0.CR1 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-native-3.4.0 The wsa messageId header is missing in the response header . Although it is optional as per WSA spec , adding this to get better Interoperability. -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3140) Process the <addressing> element in webservices.xml

by Jim Ma (JIRA)

Process the <addressing> element in webservices.xml ---------------------------------------------------- Key: JBWS-3140 URL: https://jira.jboss.org/browse/JBWS-3140 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.4.0.Beta2 Reporter: Jim Ma Fix For: jbossws-cxf-3.4.0, jbossws-native-3.4.0 The <addressing> element configuration in webservices.xml does not work in both native and cxf stack. -- 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

13 years, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (JBWS-3141) Mtom configuration in webservices.xml DD doesn't work

by Jim Ma (JIRA)

Mtom configuration in webservices.xml DD doesn't work ------------------------------------------------------ Key: JBWS-3141 URL: https://jira.jboss.org/browse/JBWS-3141 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.4.0.Beta2 Reporter: Jim Ma Fix For: jbossws-cxf-3.4.0 The mtom configuration in webservices.xml is not handled in cxf stack : <webservice-description> <webservice-description-name>MTOMService</webservice-description-name> <wsdl-file>WEB-INF/wsdl/MTOMwsdl</wsdl-file> <port-component> <port-component-name>MTOM</port-component-name> <wsdl-port>wsdl:MTOMPort</wsdl-port> <enable-mtom>true</enable-mtom> <protocol-binding>##SOAP11_HTTP</protocol-binding> ... </port-component> <port-component> -- 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

13 years, 5 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues November 2010