Skip to content
Advertisement

Tag: xsd-validation

Why is this XML Validation failing on NameIDFormat from an extended type?

I recently encountered an issue with SAML metadata validation from a customer. The relevant part of metadata that is failing: This fails with the folowing error: cvc-complex-type.2.4.a: Invalid content was found starting with element ‘NameIDFormat’. One of ‘{“urn:oasis:names:tc:SAML:2.0:metadata”:SingleSignOnService, “urn:oasis:names:tc:SAML:2.0:metadata”:NameIDMappingService, “urn:oasis:names:tc:SAML:2.0:metadata”:AssertionIDRequestService, “urn:oasis:names:tc:SAML:2.0:metadata”:AttributeProfile, “urn:oasis:names:tc:SAML:2.0:assertion”:Attribute}’ is expected. The following is the relevant portion of saml-schema-metadata-2.0.xsd: I notice that the error message only specifies

Validation issues with polymorphic xml

We have some abstract elements defined in our root schema e.g.: … which are then extended as follows: These elements are used inside our xml file: However, when I try to validate the xml using Saxon command line, I get the error message below: Here is a link to the actual sample files for reference: xml / root schema –

Advertisement