Dynamic Metadata and Artifacts

[Rod Widdowson]

The topic that never wants to die...

So, now that we have decisions on

	1) Rev-ing the MDQ for SAML spec to make the artefact profiles work with it
And
	2) That there will be a specific Metadata Provider 'MDQ' for the SP in V3

Do we want to issue a warning if we ever encounter an artifact query for a 'Dynamic' provider (which means regexp, template or well
known)?

On the one hand it might be useful since in general it will work (because of caching) and when it doesn't the deployer will be
clueless as to why.  
On the other if someone has a chain of providers with a Dynamic provider at the top then they will get noise.    
Finally, I cannot envisage a big uptake for plain on "Dynamic" providers in V3, it will all be MDQ or LocalDynamic.

Potential mitigations might be

	- Issue the warning but once per reboot
	- Only issue the warning if we actually successfully resolved from an artifact with a Dynamic provider.

The other possibility of course is to just refuse to resolve artifacts with the dynamic provider full stop.

R