cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wabi Sabi <wabisabi2...@gmail.com>
Subject Re: Configuring SwA to work with WS-Security in a CXF client
Date Wed, 19 Feb 2014 16:31:20 GMT
Thank you, Colm!

Upgraded to milestone2. Still no luck:

Caused by: *org.apache.wss4j.common.ext.WSSecurityException*: Attachment
not found

at
org.apache.wss4j.dom.processor.ReferenceListProcessor.decryptEncryptedData(
*ReferenceListProcessor.java:360*)

at org.apache.wss4j.dom.processor.EncryptedKeyProcessor.decryptDataRef(
*EncryptedKeyProcessor.java:487*)

at org.apache.wss4j.dom.processor.EncryptedKeyProcessor.decryptDataRefs(
*EncryptedKeyProcessor.java:422*)

at org.apache.wss4j.dom.processor.EncryptedKeyProcessor.handleToken(
*EncryptedKeyProcessor.java:210*)

at org.apache.wss4j.dom.processor.EncryptedKeyProcessor.handleToken(
*EncryptedKeyProcessor.java:66*)

at org.apache.wss4j.dom.WSSecurityEngine.processSecurityHeader(
*WSSecurityEngine.java:421*)

at org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor.handleMessage(
*WSS4JInInterceptor.java:257*)

... 40 more




On Wed, Feb 19, 2014 at 5:26 AM, Colm O hEigeartaigh <coheigea@apache.org>wrote:

> Hi,
>
> You are seeing the WSS4J beta jars because you are using CXF version
> "3.0.0-milestone1". So you should either instead use version
> "3.0.0-SNAPSHOT", or even better use the just-released "3.0.0-milestone2".
>
> Colm.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message