[JIRA] Commented: (JOST-162) Globally enabling schema validation breaks the Signature metadata filter

[Scott Cantor (JIRA)]

    [ https://issues.shibboleth.net/jira/browse/JOST-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13592#comment-13592 ] 

Scott Cantor commented on JOST-162:
-----------------------------------

This is not that issue. Defaults are not a configurable behavior in validation, but normalization is. You simply can't normalize and verify signatures, not unless the normalization avoids corrupting the DOM. Xerces-C was patched numerous times to deal with that problem, but Xerces-J is apparently still changing the DOM directly.

> Globally enabling schema validation breaks the Signature metadata filter
> ------------------------------------------------------------------------
>
>                 Key: JOST-162
>                 URL: https://issues.shibboleth.net/jira/browse/JOST-162
>             Project: OpenSAML 2 - Java
>          Issue Type: Bug
>          Components: SAML 2
>    Affects Versions: 2.5.0
>         Environment: Jetty 7.4, Java 1.6, Linux, latest endorsed libraries
>            Reporter: Scott Cantor
>            Assignee: Chad La Joie
>
> When schema validation is enabled for the parser pool in the IdP, the signature metadata filter starts refusing to validate the signature over metadata that is known to be valid. It loads in other respects.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira