[Ext] Chaining MetadataProvider and IdPv3
Nate Klingenstein
nate.klingenstein at utah.edu
Thu May 19 13:57:25 EDT 2016
>> Is it still mandatory?
>
> ISTR that old style relying party needs it.
Any recollection regarding metadata-providers.xml’s requirements?
>> 2) Is there any functional difference between having a Chaining element
>> wrapped around two providers and having multiple EntityDescriptors beyond
>> the modest control provided by the MetadataProvider configuration itself?
>
> I'm not sure I understand the question. But I can tell you that all that
> happens if the parser meets multiple metadata providers is that it grows an
> implicit chaining provider and inserts it.
Whether there’s a difference between:
<MetadataProvider id="chain" xsi:type="ChainingMetadataProvider">
<MetadataProvider id="LocalMetadata" xsi:type="FilesystemMetadataProvider" ...>
<!-- ... -->
</MetadataProvider>
<MetadataProvider id="FederationMetadata" xsi:type="FileSystemMetadataProvider" ...>
<!-- ... -->
</MetadataProvider>
</MetadataProvider>
with two files
and
<MetadataProvider id="chain" xsi:type="ChainingMetadataProvider">
<MetadataProvider id=“ConcatenatedMetadata" xsi:type="FilesystemMetadataProvider" ...>
<!-- ... -->
</MetadataProvider>
</MetadataProvider>
other than the flags you can set on the MetadataProvider element itself.
Thanks so much,
Nate.
More information about the users
mailing list