Fixed in the latest Rampart/C svn. -Manjula.
On Thu, 2008-06-05 at 16:29 -0400, Subra A Narayanan wrote: > Hello folks, > > 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> > > I have already created a JIRA for this => > https://issues.apache.org/jira/browse/RAMPARTC-109 > > > Thanks, > Subra > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
