Thanks for the log. I copied the SAML authn request from the log and ran our ValidateAgainstSchema console app that validates the XML against the SAML XML schemas. The ValidateAgainstSchema project is under the Examples\Utility folder.
ValidateAgainstSchema.exe authnrequest.xml Loading authnrequest.xml Validating against XML schemas Validated: False The element 'Extensions' in namespace 'urn:oasis:names:tc:SAML:2.0:protocol' has invalid child element 'EncryptedExtensions'. List of possible elements expected: any element in namespace '##other'. Elapsed time: 146.3557 ms
The issue is that the XML schema expects the EncryptedExtensions to be under a namespace. If you updated your EncryptedExtensions to specify a namespace declaration (eg <EncryptedExtensions xmlns="urn:EncryptedExtensions"> ), the XML validates against the schema. Of course, you would still have to confirm with the IdP what namespace it expects for the EncryptedExtensions element.
Regards ComponentSpace Development
|