Philippe A created RAMPART-366:
----------------------------------
Summary: sp:EncryptBeforeSigning protection order does not work
Key: RAMPART-366
URL: https://issues.apache.org/jira/browse/RAMPART-366
Project: Rampart
Issue Type: Bug
Components: rampart-policy
Affects Versions: 1.7.0
Reporter: Philippe A
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?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
