Custom DataConnector failing when upgrading to Shibboleth IDP 5.x

[Cantor, Scott]

This is a dev list sort of topic, but having said that, our docs for extensions are out of date I would imagine, we have no resources to update them. I don't know if they are out of date enough to lead to schema access problems.

What drives the custom parser lookups is the schemaLocation attribute within the XML. You can break it very easily by using alternative locations that don't match what's defined in the spring.schemas file exactly, but I doubt that's the issue.

It sounds like a bug to me or perhaps a Spring regression, but you'd have to reproduce it on Jetty before we'd look into it for a non-member.

We aren't really going to provide any support for extension devlopment outside of member support but since the mechanism involved is the same as what we use ourselves, we'd have to look into it if it happens with Jetty. 

-- Scott