Shibboleth XML Configuration file Validation

[Mark O'Quinn]

Thanks Peter for your response.

I've been wondering if I should use the Shibboleth's class in charge of this process instead of validating the XMLs myself. I assume that can be done, because Shibboleth at some point needs to validate the xml (based on the schemas) in order to start the idp. I've been looking the class SAMLMDRelyingPartyConfigurationManager to check the validation of the relying-party.xml file. 

What I want to do is to dynamically modify the xml configuration files (some of them) during runtime and validate the xmls against the schemas in order to prevent idp from crashing. Does anybody know a way of doing this, or that can point me to some direction to start working.

Regards and thanks for all the help.

-Mark


On Sep 21, 2012, at 6:14 AM, Peter Schober wrote:

> * Mark O'Quinn <mark1oquinn at gmail.com> [2012-09-21 00:03]:
>> I trying to validate some of the xml files found in the
>> configuration folder of shibboleth (e.g, relying-party.xml) using
>> Xerces, XOM and javax.xml.* but when I load the xsd files mentioned
>> in the relying-party.xml file, it keeps asking for more and more xsd
>> files that are not mention in the previous xml file. So the question
>> is, how do you guys validate the xmls in shibboleth, what is the
>> class that does this in order to check the logic.
> 
> Just for validating SAML 2.0 (signed) metadata you need
> saml-schema-metadata-2.0.xsd
> saml-schema-assertion-2.0.xsd
> xmldsig-core-schema.xsd
> xenc-schema.xsd
> xml.xsd
> so I'd just keep adding those schemas ;)
> -peter
> --
> To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net