Broken MappedAttributeDefinition Example?

[Klingenstein, Nate]

Yea, from the release notes:

IDP-813 : Remove the need for separate 'dc:', 'enc:',  and 'ad:' namespaces in the attribute-resolver file.
Additionally, the ordering requirements on sub-elements has been removed.

https://wiki.shibboleth.net/confluence/display/IDP30/ReleaseNotes#ReleaseNotes-NewFeatures

I'm almost certain this fully explains the behavior we experienced.  I used 3.2.1 as the basis for my files, but I didn't touch any of the schema definitions.

I can't recall whether the schema URL's in the schemaLocation elements even get resolved at runtime, but one deployment was using 3.2.1 with that configuration and one was using 3.3.0, but likely with more ported/hardcoded config pulled out of 3.2.1 than I checked in.

I'll confirm this on Monday, but I already know what my wish is: consistent documentation.

The rest of the IDP30 documentation is painfully explicit about versioning.  By contrast, the MappedAttributeDefinition documentation seems to say nothing about versioning or backward compatibility.

https://wiki.shibboleth.net/confluence/display/IDP30/MappedAttributeDefinition
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20161128/e5c37246/attachment.html>