The Shibboleth IdP V4 software has reached its End of Life and is no longer supported. This documentation is available for historical purposes only. See the IDP5 wiki space for current documentation on the supported version.
ChainingMetadataProvider
Namespace: urn:mace:shibboleth:2.0:metadata
Schema: http://shibboleth.net/schema/idp/shibboleth-metadata.xsd
Overview
The ChainingMetadataProvider
is a container for an ordered sequence of metadata providers of any type. When conducting a search, the metadata resolver consults each child provider in the order in which it is listed. See the parent topic for a detailed description of the search ordering algorithm used by the metadata resolver.
Reference
Examples
Here is a brief summary of the examples in this section:
Example 1: A traditional configuration using
FilesystemMetadataProvider
for local metadata andFileBackedHTTPMetadataProvider
for federation metadataExample 2: A "no touch" configuration using
LocalDynamicMetadataProvider
for local metadata andFileBackedHTTPMetadataProvider
for federation metadataExample 3: A completely dynamic configuration using
LocalDynamicMetadataProvider
for local metadata andDynamicHTTPMetadataProvider
for federation metadata
The following example illustrates one or more providers of type FilesystemMetadataProvider
followed by a single FileBackedHTTPMetadataProvider
:
Avoid redundant providers in the chain
Resolve federation metadata with either a FileBackedHTTPMetadataProvider
(Example #2) or a DynamicHTTPMetadataProvider
(Example #3) but not both. Assuming the same set of entities are represented in each case, the two approaches are mutually exclusive.