questions re the ChainingMetadataProvider type

Tom Scavo trscavo at gmail.com
Mon May 14 17:07:36 EDT 2018


On Mon, May 14, 2018 at 12:15 PM, Tom Scavo <trscavo at gmail.com> wrote:
>
> ... the following statements in the documentation are incorrect:
>
> In MetadataConfiguration:
>
> "The Common Attributes are available on all metadata provider types"
>
> "The following child elements may be used with all metadata provider types"
>
> In ChainingMetadataProvider:
>
> "Any of the common attributes may be specified"
>
> "Any of the common child elements can be specified"

These doc bugs are fixed in the wiki. I don't think there's anything
particularly contentious to be reviewed but it is slightly more
complicated than it needs to be. I'll leave it at that.

I think there is a deployment issue here. Some federations document
the use of ChainingMetadataProvider while others do not. I know of at
least one federation document that does not use
ChainingMetadataProvider but neither does it use sortKey on the bare
metadata providers. AFAICT by reading *our* documentation, that
results in an unspecified search order. I'm pretty sure that's not
what the author of the federation document intended.

Tom


More information about the dev mailing list