[JIRA] Updated: (JOST-135) Opensaml prunes empty xml namespaces, that are required for correct encryption

[Scott Cantor (JIRA)]

     [ https://issues.shibboleth.net/jira/browse/JOST-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Cantor updated JOST-135:
------------------------------

    Fix Version/s:     (was: 2.5.4)
                   2.6.0

> Opensaml prunes empty xml namespaces, that are required for correct encryption
> ------------------------------------------------------------------------------
>
>                 Key: JOST-135
>                 URL: https://issues.shibboleth.net/jira/browse/JOST-135
>             Project: OpenSAML 2 - Java
>          Issue Type: Bug
>          Components: SAML 2
>            Reporter: Kjeld Froberg
>            Assignee: Brent Putman
>             Fix For: 2.6.0
>
>
> Opensaml's XML helpers prunes empty default namespaces - but according to the XML Canoncalization ( http://www.w3.org/TR/xml-exc-c14n/ Section 3 point 4 ) it is told that:
> If the token representing the default namespace is not present in InclusiveNamespaces PrefixList, then the rules for rendering xmlns="" are changed as follows. When canonicalizing the namespace axis of an element E that is in the node-set, output xmlns=""  if and only if all of the conditions are met:
>    1. E visibly utilizes the default namespace (i.e., it has no namespace prefix), and
>    2. it has no default namespace node in the node-set, and
>    3. the nearest output ancestor of E that visibly utilizes the default namespace has a default namespace node in the node-set.
> When the empty default namespace is missing then the hash value for the element which is STR transformed is calculated incorrectly.

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