Yes, there was a bug fixed in WSS4J 1.6.2 that was probably causing
the error you were seeing:
https://issues.apache.org/jira/browse/WSS-301
Colm.
On Fri, Dec 16, 2011 at 3:35 PM, fachhoch wrote:
> I think its a bug with wss4j-1.6.0.jar I replaced this with
> wss4j-1.6.3.jar it works.
>
>
I think its a bug with wss4j-1.6.0.jar I replaced this with
wss4j-1.6.3.jar it works.
--
View this message in context:
http://cxf.547215.n5.nabble.com/moving-to-cxf-2-5-org-apache-ws-security-WSSecurityException-The-signature-or-decryption-was-invalid-tp5077993p5080564.html
Sent from th
Do you have a test-case that shows the bug?
Colm.
On Thu, Dec 15, 2011 at 8:20 PM, fachhoch wrote:
> I enabled org.apache.ws logging here is more debug from logs
>
>
>
>
> --
> View this message in context:
> http://cxf.547215.n5.nabble.com/moving-to-cxf-2-5-org-apache-ws-security-WSSecurit
I enabled org.apache.ws logging here is more debug from logs
--
View this message in context:
http://cxf.547215.n5.nabble.com/moving-to-cxf-2-5-org-apache-ws-security-WSSecurityException-The-signature-or-decryption-was-invalid-tp5077993p5078579.html
Sent from the cxf-user mailing list arch
enabled logging and here is the exception
--
View this message in context:
http://cxf.547215.n5.nabble.com/moving-to-cxf-2-5-org-apache-ws-security-WSSecurityException-The-signature-or-decryption-was-invalid-tp5077993p5078372.html
Sent from the cxf-user mailing list archive at Nabble.com.
This shows that the server side is sending back a fault. You may need to
look at the logs on the server side to see what is wrong.
Dan
On Thursday, December 15, 2011 8:22:56 AM fachhoch wrote:
> trying cxf with 2.50 caused this error
>
>
>
> It works good with cxf 2.2.6, wss4j 1.5.8
>
trying cxf with 2.50 caused this error
It works good with cxf 2.2.6, wss4j 1.5.8
now I am trying to migrate to cxf 2.5.0 I get the error and wss4j 1.6.0.
--
View this message in context:
http://cxf.547215.n5.nabble.com/moving-to-cxf-2-5-org-apache-ws-security-WSSecurityException-The-sign
