Skip to:
When an enhanced client sends this SOAP 1.1 package to the SP endpointhttps://FQDN/Shibboleth.sso/SAML2/ECP
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><S:Fault><faultcode>S:Server</faultcode><faultstring>a message goes here</faultstring></S:Fault></S:Body></S:Envelope>
in the Apache httpd server log one finds
[Thu May 12 06:54:14 2011] [error] [client xxx.xxx.xxx.xxx] Invalid child element: faultcode
and in native.log
2011-05-12 06:54:14 ERROR Shibboleth.Listener [4062] shib_handler: remoted message returned an error: Invalid child element: faultcode2011-05-12 06:54:14 ERROR Shibboleth.Apache [4062] shib_handler: Invalid child element: faultcode
http://svn.shibboleth.net/view/cpp-xmltooling?view=revision&revision=851
When an enhanced client sends this SOAP 1.1 package to the SP endpoint
https://FQDN/Shibboleth.sso/SAML2/ECP
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body>
<S:Fault>
<faultcode>S:Server</faultcode>
<faultstring>a message goes here</faultstring>
</S:Fault>
</S:Body>
</S:Envelope>
in the Apache httpd server log one finds
[Thu May 12 06:54:14 2011] [error] [client xxx.xxx.xxx.xxx] Invalid child element: faultcode
and in native.log
2011-05-12 06:54:14 ERROR Shibboleth.Listener [4062] shib_handler: remoted message returned an error: Invalid child element: faultcode
2011-05-12 06:54:14 ERROR Shibboleth.Apache [4062] shib_handler: Invalid child element: faultcode