File(s): conf/metadata-providers.xml
Format: Custom Schema
...
Configuration options common to two or more metadata providers are listed in the subsections below. Others are specific to the xsi:type
, and these are documented on the pages specific to each type.
Localtabgroup |
---|
Localtab |
---|
active | true |
---|
id | CommonAttributes |
---|
Expand |
---|
title | Common XML Attributes |
---|
|
Include Page |
---|
| MetadataProviderCommonAttributes |
---|
| MetadataProviderCommonAttributes |
---|
| localtab |
Expand |
---|
|
id | ReloadingAttributes |
---|
title | Reloading XML Attributes |
---|
| Include Page |
---|
| MetadataProviderReloadingAttributes |
---|
| MetadataProviderReloadingAttributes |
---|
|
Localtab |
---|
| id | DynamicAttributes
---|
Expand |
---|
title | Dynamic XML Attributes |
---|
|
Include Page |
---|
| MetadataProviderDynamicAttributes |
---|
| MetadataProviderDynamicAttributes |
---|
|
Localtab |
---|
| id | HTTPAttributes
---|
Expand |
---|
|
Include Page |
---|
| MetadataProviderHTTPAttributes |
---|
| MetadataProviderHTTPAttributes |
---|
|
Localtab | id |
Expand |
---|
ChildElements | |
Include Page |
---|
| MetadataProviderChildElements |
---|
| MetadataProviderChildElements |
---|
|
|
Miscellany
Localtabgroup |
---|
Localtab |
---|
active | true |
---|
Expand |
---|
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
---|
Expand |
---|
|
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: |