Open grindhold opened 2 years ago
This is what I have a in mind:
The validator needs to be built before it can be used. It needs to be provided with the namespaces and schemas that it will load and parse. This is state that needs to be held somewhere (1), along with new configurations (2) to set that state.
SecurityContext
.SecurityContext
, the validator will also be loaded, given the right configuration. The configuration will set additional locations (mapping between namespace and local file) which will be merged with the builtin locations.validate
function will be integrated into the SecurityContext
API and files will be validated through that API.
I monkeypatched
xml/schema/__init__.py
as suggested in #833 to achieve loading a user-provided xsd. And it worked until, recently, the file has been altered.I urgently need this feature.
a) If I was to implement it, how should the API look like? Could you outline an architectural approach that would match what you as maintainers strive to get for pysaml2? What non-obvious problems should one consider before implementing?
b) Who could I throw money at to implement this for me?