Versions Compared

Old Version 18

changes.mady.by.user Scott Cantor

Saved on

compared with

New Version 19

changes.mady.by.user Rod Widdowson

Saved on

Key

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

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
activetrue
idCommonAttributes
Expand
titleCommon XML Attributes

Include Page
MetadataProviderCommonAttributes
MetadataProviderCommonAttributes

localtab


DynamicAttributes
Expand
idReloadingAttributes
titleReloading XML Attributes

Include Page
MetadataProviderReloadingAttributes
MetadataProviderReloadingAttributes

Localtab
id



HTTPAttributes
Expand
titleDynamic XML Attributes

Include Page
MetadataProviderDynamicAttributes
MetadataProviderDynamicAttributes

Localtab
id


id
Expand
titleHTTP XML Attributes

Include Page
MetadataProviderHTTPAttributes
MetadataProviderHTTPAttributes

Localtab



Expand
ChildElements
titleCommon XML Elements

Include Page
MetadataProviderChildElements
MetadataProviderChildElements


Miscellany

SearchOrdering


Localtabgroup
Localtab
activetrue
Expand
titleMultiple 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


Expand
titleSearch 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:

  • Metadata sources combined via a chain are searched in the order in which they occur in the chain, and the first entry matching the entityID is returned.

  • If multiple "top level" Metadata Providers are provided then they are searched in an order derived from the (numeric) value of the sortKey attribute (lowest key first). If no sortKey is specified, then the search order is undefined.

  • In whatever order of sources is in effect, the first entry matching the entityID is returned.
  • If a single metadata source contains multiple entries with the same entityID, then which entry is returned is undefined (exception: invalid entries would be ignored in favor of valid ones in most cases).