File(s): conf/metadata-providers.xml
Format: Custom Schema
...
Localtabgroup |
---|
Localtab |
---|
active | true |
---|
id | CommonAttributes |
---|
title | Common XML Attributes |
---|
| Include Page |
---|
| MetadataProviderCommonAttributes |
---|
| MetadataProviderCommonAttributes |
---|
|
|
Localtab |
---|
id | ReloadingAttributes |
---|
title | Reloading XML Attributes |
---|
| Include Page |
---|
| MetadataProviderReloadingAttributes |
---|
| MetadataProviderReloadingAttributes |
---|
|
|
Localtab |
---|
id | DynamicAttributes |
---|
title | Dynamic XML Attributes |
---|
| Include Page |
---|
| MetadataProviderDynamicAttributes |
---|
| MetadataProviderDynamicAttributes |
---|
|
|
Localtab |
---|
id | HTTPAttributes |
---|
title | HTTP XML Attributes |
---|
| Include Page |
---|
| MetadataProviderHTTPAttributes |
---|
| MetadataProviderHTTPAttributes |
---|
|
|
Localtab |
---|
id | ChildElements |
---|
title | Common XML Elements |
---|
| The following child element may be used with all MetadataProvider types except the ChainingMetadataProvider type: | Name | Cardinality | Description |
---|
<MetadataFilter > | 0 or more | A metadata filter applied to candidate metadata as it flows through the metadata pipeline Include Page |
---|
| MetadataProviderChildElements |
---|
| MetadataProviderChildElements |
---|
|
|
Miscellany
Localtabgroup |
---|
Localtab |
---|
active | true |
---|
title | Multiple Configuration FIles |
---|
| As described in the ReloadableServices documentation, the configuration is actually loaded from a bean whose name is specified by the property idp.service.metadata.resources, with the default value shibboleth.MetadataResolverResources (in turn defined in conf/services.xml to be a list with one entry: the file metadata-providers.xml)
You can, if you choose, override this with additional or different files or more advanced sources. Each resource usually is expected to supply a "top level" <MetadataProvider> element with attributes and child elements as described above. Search order amongst multiple top level elements is arbitrated by the sortKey attribute, where lower values are processed before higher ones. It is also now possible to declare "by reference" metadata filters that are attached by reference, so it is possible to supply a resource whose top-level element is such a <MetadataFilter> in such cases. |
Localtab |
---|
id | SearchOrdering |
---|
title | Search Ordering |
---|
| If a specific relying party (as identified by a specific entityID) is duplicated in the metadata sources provided, then which precise entry is chosen is governed by the following rules: |
|