The following attributes are required on all metadata provider types:
Identifier for logging, identification for command line reload, etc.
Specifies the exact type of provider to use (from those listed above, or a custom extension type)
The following attributes are common to all metadata provider types except the
Whether candidate metadata found by the resolver must be valid in order to be returned (where validity is implementation specific, but in SAML cases generally depends on a
validUntil attribute.) If this flag is true, then invalid candidate metadata will not be returned.
Whether to fail initialization of the underlying MetadataResolverService (and possibly the IdP as a whole) if the initialization of a metadata provider fails. When false, the IdP may start, and will continue to attempt to reload valid metadata if configured to do so, but operations that require valid metadata will fail until it does.
Defines the order in which metadata providers are searched (see below), can only be specified on top level
The following are advanced settings supporting a new low-level feature allowing metadata lookup by keys other than the unique entityID and are rarely of use to a deployer.
Identifies the a custom CriterionPredicateRegistry bean used in resolving predicates from non-predicate input criteria
Flag which determines whether the default CriterionPredicateRegistry will be used if a custom one is not supplied explicitly
Flag which determines whether predicates used in filtering are connected by a logical 'OR' (true) or by logical 'AND' (false)