Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The following example illustrates one or more providers of type FilesystemMetadataProvider followed by a single FileBackedHTTPMetadataProvider:

Expand
titleExample 1: A traditional configuration
Code Block
languagexml
<MetadataProvider id="chain" xsi:type="ChainingMetadataProvider">
	<!-- 
		One or more providers of type FilesystemMetadataProvider for local metadata.
		Each metadata provider describes a static entity descriptor stored in a file.
	-->
	<MetadataProvider id="LocalMetadata" xsi:type="FilesystemMetadataProvider" ...>
      <!-- ... -->
	</MetadataProvider>
	
	<!-- 
		Exactly one provider of type FileBackedHTTPMetadataProvider for federation metadata.
		The metadata provider automatically refreshes a metadata aggregate (EntitiesDescriptor)
		which would otherwise expire.
	-->
	<MetadataProvider id="FederationMetadata" xsi:type="FileBackedHTTPMetadataProvider" ...>
      <!-- ... -->
	</MetadataProvider>
</MetadataProvider>                                   

In the above example, local metadata is loaded before externally resolved federation metadata. This prevents federation metadata from accidentally overriding local metadata sources.

The following example is similar to the previous example except that multiple providers of type FilesystemMetadataProvider have been replaced with a single LocalDynamicMetadataProvider:

...