You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Jim Ma (JIRA)" <ji...@apache.org> on 2014/05/14 09:26:15 UTC
[jira] [Resolved] (CXF-5741) The properties in the requestContext
are not copied into RMClient
[ https://issues.apache.org/jira/browse/CXF-5741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Ma resolved CXF-5741.
-------------------------
Resolution: Fixed
> The properties in the requestContext are not copied into RMClient
> ------------------------------------------------------------------
>
> Key: CXF-5741
> URL: https://issues.apache.org/jira/browse/CXF-5741
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 3.0.0-milestone2, 2.7.11
> Reporter: Jim Ma
> Assignee: Jim Ma
> Fix For: 2.7.12, 3.0.0
>
>
> When I tried to put all the security configuration properties in the requestContext and call a service with both RM and security policy enabled(like the service in WSRMWithWSSecurityPolicyTest) :
> bp.getRequestContext().put(SecurityConstants.CALLBACK_HANDLER, new KeystorePasswordCallback());
> bp.getRequestContext().put(SecurityConstants.SIGNATURE_PROPERTIES,, getResource("/META-INF/security-client.properties"));
> ....
> This doesn't work as expected and there is exception thrown:
> Failed to send RM protocol message {http://schemas.xmlsoap.org/ws/2005/02/rm}CreateSequence.: org.apache.cxf.interceptor.Fault: Security configuration could not be detected. Potential cause: Make sure jaxws:client element with name attribute value matching endpoint port is defined as well as a ws-security.signature.properties element within it.
> After I investigated the code, I saw all these ws-scurity configuration properties are not copied into the new created message by RMClient which initialized by RM interceptor.
> That's the root cause for this failure.
--
This message was sent by Atlassian JIRA
(v6.2#6252)