ws-wss4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dobri Kitipov (JIRA)" <>
Subject [jira] Created: (WSS-198) Problem when body is signed and then an XPath is encrypted
Date Thu, 11 Jun 2009 14:33:07 GMT
Problem when body is signed and then an XPath is encrypted

                 Key: WSS-198
             Project: WSS4J
          Issue Type: Bug
    Affects Versions: 1.5.7
            Reporter: Dobri Kitipov
            Assignee: Ruchith Udayanga Fernando

Hi everybody,
there is a problem when when a message body is signed and then an XPath expression pointing
to a body element is encrypted.
The problem is that the verification of the signature cannot pass. This is caused by the fact
that there is a difference between the signed body and the body used for signature verification.
The body used for signature verification is modified because after XPath element decryption
an ID is added to the element. This ID is used to verify the decryption, but changes the original

Exception thrown is:

[WARN] Verification failed for URI "#Id-11235685"
[WARN] Expected Digest: o0jyc1pJHEawRaLNry+cnYeCc80=
[WARN] Actual Digest: VMEF6KgvE6t3PNLlYR49LGEW+xM=
[ERROR] The signature or decryption was invalid
org.apache.axis2.AxisFault: The signature or decryption was invalid
	at org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(
	at org.apache.rampart.handler.RampartReceiver.invoke(
	at org.apache.axis2.engine.Phase.invoke(
	at org.apache.axis2.engine.AxisEngine.invoke(
	at org.apache.axis2.engine.AxisEngine.receive(
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(
	at org.apache.axis2.transport.http.AxisServlet.doPost(
	at com.softwareag.wsstack.deployment.server.SAGAdminServlet.doPost(
	at javax.servlet.http.HttpServlet.service(
	at javax.servlet.http.HttpServlet.service(
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(
	at org.apache.catalina.core.StandardWrapperValve.invoke(
	at org.apache.catalina.core.StandardContextValve.invoke(
	at org.apache.catalina.core.StandardHostValve.invoke(
	at org.apache.catalina.valves.ErrorReportValve.invoke(
	at org.apache.catalina.core.StandardEngineValve.invoke(
	at org.apache.catalina.connector.CoyoteAdapter.service(
	at org.apache.coyote.http11.Http11Processor.process(
	at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(
	at org.apache.tomcat.util.threads.ThreadPool$
Caused by: The signature or decryption was invalid
	at org.apache.rampart.RampartEngine.process(
	at org.apache.rampart.handler.RampartReceiver.invoke(
	... 22 more

I will try to apply a patch tomorrow.

Any comments and ideas are appreciated.


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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message