Dynamic Metadata and Artifacts

[Rod Widdowson]

> If an SP deployment does not support artifact resolution, it may use
> any flavor of Dynamic Metadata Provider. Put another way, if published
> metadata does not contain an AssertionConsumerService endpoint that
> supports an artifact binding, the SP may use any flavor of Dynamic
> Metadata Provider.

Yes.
 
> I assume an SP can be configured to not support artifact resolution.
> In that case, there's no need to issue a warning since the SP can use
> any metadata provider it wants.

I guess so - Scott would be certain

> Does that make sense?

yes

> As an aside, have you thought about shipping the SP with a default
> configuration that disables artifact resolution, attribute query, and
> in fact all back-channel message flows? Few deployments really need or
> want that stuff.

Another one for Scott....

/R