questions re the ChainingMetadataProvider type

[Rod Widdowson]

> child elements of the latter. In the schema, you'll find this
> sentence: "Note that metadata filters and the require valid metadata
> flag expressed on this configuration overrides those settings on
> member providers."

Sounds like we need an RFE to review the schema <documentation> Elements.  I don't have time to look at this in the V3 timeframe,
but it can be targeted for V4.
 
> 1) I understand the comment about the requireValidMetadata attribute
> but what about the rest of the Common Attributes? Are they simply
> ignored by the parent ChainingMetadataProvider?

As I recall we actually tend to warn if people use attributes which are meaningless particulsarly for the chaining provider

  >      log.warn("{} is not valid for ChainingMetadataProvider);

Which fires for:
	failFastInitialization
	requireValidMetadata
	satisfyAnyPredicates
	useDefaultPredicateRegistry
	criterionPredicateRegistryRef


 
> 2) I don't understand the comment about the metadata filters. 

Filters apply hierarchically.  

The SP doesn’t allow them at all on Chaining providers and I'd like to do something like that in the IdP but it gets grubby because
there is an implied chaining filter at the top level of each <MetadataProvider> so you may not be getting what you expect.  I don't
have enough deployment experience to make the call, but when Scott gets back he will no doubt have some comments to offer..