[RAMPART-366] sp:EncryptBeforeSigning protection order does not work

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.7.0
• Component/s: rampart-policy
• Assignee: Unassigned
• Reporter: Philippe A
• Created: 25/Apr/12 20:09
• Updated: 12/Sep/13 15:21

Description

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="http://schemas.xmlsoap.org/soap/envelope/">

<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?