ws-wss4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Vladov (JIRA)" <>
Subject [jira] Commented: (WSS-198) Problem when body is signed and then an XPath is encrypted
Date Wed, 24 Jun 2009 14:59:07 GMT


Stefan Vladov commented on WSS-198:

Hi Colm,

sorry for the delay... I was busy with some other things...

I did a partial merge of your fix in wss4j 1.5.4 (this is the version used with rampart 1.4)
- I'm not really using the ref to the encrypted element but add an xpath to it instead (rampart
does not work with axiom DOM implementation but with OMElements instead). I modified rampart,
so that  when verifying encrypted elements I first apply the xpath expressions from the wss4j
data Refs to obtain a list of nodes that were actually decrypted, then use the xpath expressions
from the policy to get the nodes that should have been encrypted, and finally do a simple
ref comparison between the two lists. XPath in Rampart is handled using Jaxen and always returns
references from the xml tree so this should be ok. Of course "content"/"element" modifier
is also taken care of. I'm not really sure what will be the performance impact of this...

Sorry for the cloning remark... I was browsing quickly through your code, noticed some clone
in headers or sth and was quick to judge.

I'll talk to Nandana about the required modification in rampart and will send the proposed

> Problem when body is signed and then an XPath is encrypted
> ----------------------------------------------------------
>                 Key: WSS-198
>                 URL:
>             Project: WSS4J
>          Issue Type: Bug
>    Affects Versions: 1.5.7
>            Reporter: Dobri Kitipov
>            Assignee: Colm O hEigeartaigh
>             Fix For: 1.5.8
>         Attachments: send_to_server_side_before_encryption.xml, signed_doc_after_decryption.xml
> 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 body. 
> I am doing the tests with :
> Rampart from the trunk with WSS4J 1.5.7.
> 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.mycompany.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
> 	at
> 	at org.apache.tomcat.util.threads.ThreadPool$
> 	at
> Caused by: The signature or decryption was
> 	at
> 	at
> 	at
> 	at
> 	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.
> Regards,
> Dobri

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