SP V3 metadata types
Tom Scavo
trscavo at gmail.com
Mon Jun 11 15:46:21 EDT 2018
On Mon, Jun 11, 2018 at 3:01 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
>>
>> As a hypothetical concept, does that make sense?
>
> Sure, in theory, just not really in practice today.
I agree, custom remote metadata aggregates are not very practical
today. OTOH, a DynamicHTTPMetadataProvider aggregates the metadata of
your SP partners as a side effect. The current implementation doesn't
fully leverage that metadata, however.
The current implementation of DynamicHTTPMetadataProvider caches
entity metadata in a local directory (if
persistentCacheManagerDirectory is specified) but then the cache is
treated as nothing more than a glorified backing file (at least
AFAICT). The provider needs to be smarter about how it leverages
cached metadata.
At this point, I'm tempted to dive into a number of "what ifs" but
that would probably be premature since (as you say) some modifications
are coming. I hope I'm watching the relevant jira issues. Can/should
we discuss it here instead?
>> I was asking about the IdP documentation...if anyone on the dev team thinks
>> the wiki example [1] is counterproductive, I will remove it.
>
> I think it's probably not crazy to show in the IdP today, but I've already asked Brent to improve some of the behavior of the dynamic plugin and I think that will render it unnecessary so I would prefer we not complicate examples with it now.
Okay, the example is gone. I still think our story surrounding remote
metadata is incomplete.
Thanks,
Tom
More information about the dev
mailing list