Incorrect SoapFault format
---------------------------
Key: RAMPARTC-109
URL: https://issues.apache.org/jira/browse/RAMPARTC-109
Project: Rampart/C
Issue Type: Bug
Components: Rampart-core
Affects Versions: 1.2.0
Environment: axis2/c v1.4, Linux 64bit
Reporter: Subra A Narayanan
Assignee: Malinda Kaushalye Kapuruge
Rampart v1.2 is not generating soap faults correctly. The response below is for
a soap 1.1 message as captured by tcpmon. As you can see the <subcode> node
does not belong here. <subcode> is part of soap1.2 fault not soap1.1 fault.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
<soapenv:Header/>
<soapenv:Body>
<soapenv:Fault>
<faultcode>
<Subcode
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";>
<Value>wsse:InvalidSecurity</Value>
</Subcode>soapenv:Sender
</faultcode>
<faultstring>Signature Verification failed.</faultstring>
<detail>
<wsse:ProblemSecurityHeader
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";>ds:Signature</wsse:ProblemSecurityHeader>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
