cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] Commented: (CXF-2854) Carriage return (\r) in String argument to service method causes "SoapFault: The signature or decryption was invalid"
Date Fri, 18 Jun 2010 17:09:25 GMT


Daniel Kulp commented on CXF-2854:

I believe this has been fixed for a fairly long time.   It works fine with the latest 2.2.10
release of CXF which includes the latest (1.5.8) version of wss4j and 1.4.3 version of xmlsec.

I would STRONGLY encourage upgrading to the latest versions to see if it's already fixed.

> Carriage return (\r) in String argument to service method causes "SoapFault: The signature
or decryption was invalid"
> ---------------------------------------------------------------------------------------------------------------------
>                 Key: CXF-2854
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.1.4
>         Environment: Windows XP Professional SP3
> JDK 1.6.0_13
>            Reporter: Web Development Guys
>         Attachments:
> When using a WSS4JOutInterceptor on the proxy client and WSS4JInInterceptor on the service
with the action WSHandlerConstants.SIGNATURE, the call to the service terminates in a SoapFault
for an invalid signature if a String containing a carriage return (\r) is passed as an argument
to the service. Strings not containing a carriage return result in a successful response.
> A short (fewer than 100 total lines) demonstration of the bug can be provided; a stack
trace is at the end of this description.
> Thank you.
> Stack Trace:
> The signature or decryption was invalid
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(
> 	at org.apache.cxf.transport.ChainInitiationObserver.onMessage(
> 	at org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(
> 	at org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(
> 	at org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(
> 	at org.mortbay.jetty.handler.ContextHandler.handle(
> 	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(
> 	at org.mortbay.jetty.handler.HandlerWrapper.handle(
> 	at org.mortbay.jetty.Server.handle(
> 	at org.mortbay.jetty.HttpConnection.handleRequest(
> 	at org.mortbay.jetty.HttpConnection$RequestHandler.content(
> 	at org.mortbay.jetty.HttpParser.parseNext(
> 	at org.mortbay.jetty.HttpParser.parseAvailable(
> 	at org.mortbay.jetty.HttpConnection.handle(
> 	at
> 	at org.mortbay.thread.BoundedThreadPool$

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message