AffiliationDescriptor

[Tom Scavo]

On Wed, May 23, 2018 at 10:56 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:
>> I don't know what race condition you're referring to. Is there an existing jira
>> issue that tracks this?
>
> You're inside the code that constructs the individual components that will make up the MetadataResolverService, as it's loading metadata and running filters for the first time. It therefore by definition cannot take itself as a dependency in order to use itself to look up metadata (in this case an AffiliationDescriptor). It's circular.
>
> We don't currently have any notion of multiple copies of the service, so it isn't possible to define a set of metadata sources that would expose this and then feed that into a another set of metadata sources that would consume the information.
>
> Basically, you can't use the MetadataResolver service as an input component to any of the objects that are built on the inside of the MetadataResolver service itself.

Thanks Scott. I captured this issue in jira:
https://issues.shibboleth.net/jira/browse/IDP-1294

Tom