Dynamic Metadata and Artifacts

[Cantor, Scott]

On 11/10/17, 10:32 AM, "dev on behalf of Tom Scavo" <dev-bounces at shibboleth.net on behalf of trscavo at gmail.com> wrote:

> 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?

No, because the metadata code couldn't possibly know that, and it doesn't need to, because it does know if it's being asked to query based on an artifact. It may or may not be able to tell whether that query can work, and that's what we were debating.

> 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.

There's not much to configure (except a key, which is generated automatically), so what would be the point? The query support is a bit different because of the reasons it gets done. That may get adjusted.

-- Scott