Documentation of Extensions generated by SP Metadata handler

[Cantor, Scott]

On 3/5/15, 6:07 PM, "James Sanders" <sanderjd at gmail.com> wrote:
>
>I think I can guess the purpose of all of these, but I can't seem to find 
>any documentation about what exactly they are for, or recommendations 
>regarding whether or not it's good practice to include them in real 
>metadata.

The SAML extension specifications that defined them are all in the OASIS 
wiki [1] under Committee Specifications, you can ask on saml-dev if you 
have any questions about them generally or here if you wanted to know what 
Shibboleth does with them, if anything.

With a few exceptions there is no other software in the world that does 
anything with them.

Whether it's good practice is in the eye of the beholder, but some are 
more useful than others. Ultimately, anything that's accurate is at least 
neutral, apart from just taking up space. The SP generates anything it can 
generate that it has a reasonable belief will be accurate, leaving out 
lots of useful extensions that it can't know, such as MDUI extensions, 
though they can be embedded in the configuration of the handler so that it 
does include them.

-- Scott

[1] https://wiki.oasis-open.org/security