cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aki Yoshida <>
Subject Re: Copy all these properties to RMClient's message ?
Date Thu, 24 Apr 2014 12:54:43 GMT
Hi Dennis,
a combined scenario of ws-rm + ws-sec works fine in general. (and
there is a test case in systests/ws-rm that Jim mentioned).

But I think Jim is trying to control some of its behavior by passing
some properties in the client context and that won't work if those
properties are not copied into the new client's context.

regards, aki

2014-04-24 13:28 GMT+02:00 Dennis Sosnoski <>:
> Hi Jim,
> Which version of the code are you using? I've been working on combining
> WS-RM and WS-Security in the 3.0 code. There are still some pieces that need
> to be put in place (especially persisting the security properties so
> messages can be retransmitted), but the basic security+rm operation has been
> working for me in my tests.
> Regards,
>   - Dennis
> Dennis M. Sosnoski
> Java Web Services Consulting <>
> CXF and Web Services Security Training
> <>
> Web Services Jump-Start <>
> On 04/24/2014 06:40 PM, Jim Ma wrote:
>> Hi All,
>> 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/"));
>> ....
>> This doesn't work as expected and there is exception thrown:
>> Failed to send RM protocol message {
>> 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
>> 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.
>> I went back to look at jaxws spec about BindingProvider's requestContext
>> and it's scope. There isn't clue and detail to say if these properties
>> should be copied into the new created message like RM message from the
>> message which send out the real payload with user's setting though
>> requestContext.
>> Do you think we should copy them ? or What can do to support this easily?
>> Thanks in advance.
>> Jim

View raw message