Chaining MetadataProvider and IdPv3

[Cantor, Scott]

On 5/19/16, 11:50 AM, "users on behalf of Nate Klingenstein" <users-bounces at shibboleth.net on behalf of nate.klingenstein at utah.edu> wrote:

>1)  Why was the Chaining MetadataProvider type brought forward to IdPv3?  Config compatibility, other?  Is it still mandatory?

Compatibility obviously, and because it's implicitly the only way to load multiple resolvers anyway, so it gets created whether it's explicitly configured or not.

>2)  Is there any functional difference between having a Chaining element wrapped around two providers and having multiple EntityDescriptors beyond the modest control provided by the MetadataProvider configuration itself?

Not likely much different unless you were talking about a duplicate I guess, but there's more overhead having two resolvers than one.

-- Scott