metadata-driven configuration

[Tom Scavo]

[Since metadata-driven configuration is mostly dependent on V3.4, I'm
posting this to dev, not users]

I'm reviewing the page on metadata-driven configuration [1] but I
think I'm missing something.

I definitely see the benefit of the "direct method" of handling local
metadata: just add any desired entity attributes to the entity
descriptor and drop it into the sourceDirectory of a
LocalDynamicMetadataProvider. This provides a scalable "no touch"
method of relying party configuration.

I also see how the "indirect method" can be used to set defaults on
aggregate metadata (as a one-time configuration operation) but I don't
see how to customize single entities in the aggregate without touching
the config. What am I missing?

At least one metadata source is ignored here, that is, single entities
obtained remotely via the metadata query protocol. How are those
customized without touching the config? (Maybe I'm asking the wrong
question, I don't know)

Thanks,

Tom

[1] https://wiki.shibboleth.net/confluence/x/VQC_AQ