axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Attanayake (JIRA)" <>
Subject [jira] [Commented] (RAMPART-366) sp:EncryptBeforeSigning protection order does not work
Date Thu, 12 Sep 2013 14:56:52 GMT


Suresh Attanayake commented on RAMPART-366:

Yes, EncryptBeforeSigning is supported in rampart. However SignedEncryptedSupportingTokens
is not supported. However SignedEncryptedSupportingTokens is not supported in the PolicyBasedResultsValidator
for signature and encryption handling. 

Cannot reproduce this error. Attaching the policy I tried and the given bellow is the error
I get, it is due to SignedEncryptedSupportingTokens are not supported yet. 

[INFO] Listening on port 8080
     [java] [SimpleHTTPServer] Started
     [java] [ERROR] Unexpected encrypted data found, no encryption required
     [java] org.apache.axis2.AxisFault: Unexpected encrypted data found, no encryption required
     [java] 	at org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(
     [java] 	at org.apache.rampart.handler.RampartReceiver.invoke(
     [java] 	at org.apache.axis2.engine.Phase.invokeHandler(
     [java] 	at org.apache.axis2.engine.Phase.invoke(
     [java] 	at org.apache.axis2.engine.AxisEngine.invoke(
     [java] 	at org.apache.axis2.engine.AxisEngine.receive(
     [java] 	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(
     [java] 	at org.apache.axis2.transport.http.HTTPWorker.service(
     [java] 	at org.apache.axis2.transport.http.server.AxisHttpService.doService(
     [java] 	at org.apache.axis2.transport.http.server.AxisHttpService.handleRequest(
     [java] 	at
     [java] 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
     [java] 	at java.util.concurrent.ThreadPoolExecutor$
     [java] 	at
     [java] Caused by: org.apache.rampart.RampartException: Unexpected encrypted data found,
no encryption required
     [java] 	at org.apache.rampart.PolicyBasedResultsValidator.validateEncrSig(
     [java] 	at org.apache.rampart.PolicyBasedResultsValidator.validate(
     [java] 	at org.apache.rampart.RampartEngine.process(
     [java] 	at org.apache.rampart.handler.RampartReceiver.invoke(
     [java] 	... 12 more

> sp:EncryptBeforeSigning protection order does not work
> ------------------------------------------------------
>                 Key: RAMPART-366
>                 URL:
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-policy
>    Affects Versions: 1.7.0
>            Reporter: Philippe A
>         Attachments: policy.xml, tested-policy.xml
> Specifying <sp:EncryptBeforeSigning/> protection order in my <sp:SymmetricBinding>
security binding results in my Axis server returning the following fault:
> org.apache.axis2.AxisFault: An unsupported signature or encryption algorithm was used
(WSSecurityEngine: EncryptedData does not contain xenc:EncryptedKey)
> My requests go through if I comment out <sp:EncryptBeforeSigning/> from my policy.
My requests also go through with similar security options <sp:SignBeforeEncrypting/>
+ <sp:EncryptSignature/>.  
> In Axis 1.5.2 + Rampart 1.5.2 and in 1.6.1, the symptom is the following:
> 2012-04-24 17:41:43,604 [main] DEBUG org.apache.rampart.MESSAGE  - ***********************
RampartReceiver received
> <?xml version='1.0' encoding='utf-8'?>
> <soapenv:Envelope xmlns:soapenv="">
>   <soapenv:Body>
>     <soapenv:Fault>
>       <faultcode>soapenv:Server</faultcode>
>       <faultstring>Missing argument</faultstring>
>       <detail />
>     </soapenv:Fault>
>   </soapenv:Body>
> </soapenv:Envelope>
> Lastly, I looked for a Rampart example using sp:EncryptBeforeSigning  but found none.
I wonder if this is supported at all?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

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

View raw message