Dynamic Metadata and Artifacts

[Tom Scavo]

On Fri, Nov 10, 2017 at 6:04 AM, Rod Widdowson <rdw at steadingsoftware.com> wrote:
>
> So my question was "In the case when someone configures a WellKnown or Substsitute dynamic metadata provider *and* we see artefacts should we warn that this may not always work.

I think I understand now, Rod. Thanks for taking the time to explain.

A couple of observations (to test my understanding):

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.

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.

Does that make sense?

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.

Tom