Local version of schema definition for validation

[Wessel, Keith]

A follow-up question to using the schema files that Peter pointed me to on the UK Federation Github repository. It works great as the schema directory parameter to xmlsectool, but I'm not having as much luck when using the same fileset with the metadata aggregator.

When I point MDA to saml-schema-metadata-2.0.xsd directly, it complains that xmldsig-core-schema is unreadable or doesn't have an xsd:schema element at its root. In fact, it has <schema...> at its root. Missing the xsd: tag, but so is saml-schema-metadata-2.0.xsd, and that doesn't seem to be causing a problem with it.

I thought that it might help if I just let MDA make its way through the whole directory as I do with xmlsectool, but when I provide just the directory name, it complains that it can't read it. I'm using an org.springframework.core.io.FileSystemResource for the item inside the list of resources assigned to the schemaResources property.

Is there another class I should be using to get it to read the directory? Or something I need to modify in the xsd files?

I've got everything working except for this and, while schema validation isn't necessary considering my sources are already validated elsewhere, I figured it was a nice safeguard.

Thanks,
Keith


-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Ian Young
Sent: Tuesday, July 19, 2016 8:29 AM
To: Shib Users <users at shibboleth.net>
Subject: Re: Local version of schema definition for validation


> On 18 Jul 2016, at 16:57, Wessel, Keith <kwessel at illinois.edu> wrote:
> 
> Or does XMLSecTool 2.0 have schema compiled in, like the IDP, for schema validation making the need for external schema obsolete?

Just to be clear, XMLSecTool 2.0.0 should behave exactly the same way as 1.2.0 in this regard. I had to reimplement some of that code for the new stack, but there are no built-in schemas.

    -- Ian