In many typical cases, the MDQ plugin may be easier to configure as it automates certain options when using a compliant metadata source.


Identified by type="Dynamic", this MetadataProvider loads metadata on-demand from an HTTP server. The precise URL accessed is derived from the entityID of the peer and may be literal (i.e., that entityID) or more commonly constructed based on a simple substitution or transform involving the entityID. It is optimized to be reliable and efficient by caching in-memory and on-disk and by preventing unnecessary re-processing via HTTP caching support.


The type="Dynamic" attribute must be present.


Dynamic Metadata Source
<MetadataProvider type="Dynamic" id="mdq.example.org" ignoreTransport="true" cacheDirectory="mdq-example-org"> <Subst hashed="SHA1">http://mdq.example.org/global/entities/$entityID</Subst> <MetadataFilter type="Signature" certificate="metadata-signing-key.pem"/> <MetadataFilter type="RequireValidUntil" maxValidityInterval="8640000"/> </MetadataProvider>