Same result in 1.6.1. sp:EncryptBeforeSigning seems to be broken. I think the problem lies on the client side, because I have the same result whether or not the server uses the same protection order. In other words, the server always reject client "encrypted first" request. If the client signs first and my server is configured to encrypt first, then I have a protection order mismatch fault.
2012/4/24 Philippe A. <[email protected]> > Hello, > > Can someone please confirm that sp:EncryptBeforeSigning work? My client is > reporting a strange soap fault: > > 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> > > I tried using sp:SignBeforeEncrypting + sp:EncryptSignature and it worked. > However I would prefer to go with sp:EncryptBeforeSigning and skip the > extra signature encryption. I attached my policy. > > I don't mind if this is confirmed with an higher version number. > > Thanks, > > -- > Philippe > > -- Philippe
