SP V3 metadata types

Tom Scavo trscavo at gmail.com
Mon Jun 11 14:56:34 EDT 2018


On Mon, Jun 11, 2018 at 2:13 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
>
> ... the Folder hack doesn't really work for that, so I don't know what you had in mind there.

What happens if you take the notion of "high-value entity" to its
logical conclusion? The concept is really quite simple. Suppose an IdP
has access to a trusted, remote metadata aggregate containing most of
its SP partners. (That's a big "IF" but please bear with me as I make
my point.) In that case, the tail of the provider chain would consist
of a FileBackedHTTPMetadataProvider (to load the aggregate) followed
by a DynamicHTTPMetadataProvider (to pick up any stray SPs not in the
aggregate). QED

Such a configuration minimizes the number of times the
DynamicHTTPMetadataProvider makes a request. If it does fail, it fails
on an SP that is not a recognized SP partner (since its not in the
aggregate).

As a hypothetical concept, does that make sense?

>> If you (the Shib dev team) don't think this is a Good Thing To Do, please let me
>> know so I can remove the example from the wiki.
>
> I believe we felt it unnecessary in light of existing features and how it's all meant to be run.

I was asking about the IdP documentation...if anyone on the dev team
thinks the wiki example [1] is counterproductive, I will remove it.

Tom

[1] RemoteEntityMetadataExample https://wiki.shibboleth.net/confluence/x/YwbKAg


More information about the dev mailing list