You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Cencio <ce...@gmail.com> on 2010/06/23 15:51:09 UTC

MustUnderstand and Actor

Hi all,

i have a message including some SOAPHeaders with mustUnderstand=1 and actor
value. Not all headers are directed to me, but some must be understand by
next nodes. I process my headers (i decide if an header is mine looking the
actor value) and ignore the other. Then CXF throw the exception because some
header isn't understood.

There is a way to configure CXF or the service specifing a list of actor of
our interest and ignore the other header even if the mustUnderstand=1?

Thx,
Lorenzo
-- 
View this message in context: http://old.nabble.com/MustUnderstand-and-Actor-tp28972126p28972126.html
Sent from the cxf-user mailing list archive at Nabble.com.


Re: Username token and derived keys

Posted by Daniel Kulp <dk...@apache.org>.
On Thursday 24 June 2010 7:41:17 am Pages Laurent wrote:
> Hello!
> 
> I'm trying to use UsernameToken in CXF 2.2.9 and to derive key from the
> password in order to encrypt the message body. Service and client use CXF
> stack. The security policy is described in the WSDL, but CXF client
> complains as if it does not support this functionnality. Does someone know
> if CXF is able to deal with key derived from UsernameToken ?

As Sergey mentioned, not yet.    Part of the reason is that at the time the 
WS-SecPol stuff was being worked on, WSS4J didn't support this.    This was 
added for the latest WSS4J, but we never went back and added support into the 
SecPol implementation.

Dan


> 
> FYI, I tried to call the CXF service with a client that uses the Metro
> stack, and it works (on the Metro side) but then the service complains it
> cannot find the key used for encryption...
> 
> Thanks!
> 
> Laurent

-- 
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog

Re: Username token and derived keys

Posted by Sergey Beryozkin <sb...@gmail.com>.
Just FYI :

https://issues.apache.org/jira/browse/CXF-2864

However I can not commit at this stage to fixing it - but it will be tracked
and is possible it will be addressed sooner rather than later

thanks for reporting the issue
Sergey

On Thu, Jun 24, 2010 at 12:41 PM, Pages Laurent <la...@yahoo.fr> wrote:

> Hello!
>
> I'm trying to use UsernameToken in CXF 2.2.9 and to derive key from the
> password in order to encrypt the message body. Service and client use CXF
> stack.
> The security policy is described in the WSDL, but CXF client complains as
> if it does not support this functionnality.
> Does someone know if CXF is able to deal with key derived from
> UsernameToken ?
>
> FYI, I tried to call the CXF service with a client that uses the Metro
> stack, and it works (on the Metro side) but then the service complains it
> cannot find the key used for encryption...
>
> Thanks!
>
> Laurent
>
>
>

Username token and derived keys

Posted by Pages Laurent <la...@yahoo.fr>.
Hello!

I'm trying to use UsernameToken in CXF 2.2.9 and to derive key from the password in order to encrypt the message body. Service and client use CXF stack.
The security policy is described in the WSDL, but CXF client complains as if it does not support this functionnality.
Does someone know if CXF is able to deal with key derived from UsernameToken ?

FYI, I tried to call the CXF service with a client that uses the Metro stack, and it works (on the Metro side) but then the service complains it cannot find the key used for encryption...

Thanks!

Laurent