Metadata resolver failing to initialise due to one failed metadata provider

[Max Spicer]

Aha, I had indeed missed that - thanks!

For the record,
https://shibboleth.atlassian.net/wiki/spaces/IDP4/pages/1265631657/MetadataProviderCommonAttributes
shows that failFastInitialization defaults to true for
a FileBackedHTTPMetadataProvider.

Setting failFastInitialization="false" on the MetadataProvider then causes
the IdP to log this at startup and the MetadataResolver initialises
"successfully":

ERROR
[org.opensaml.saml.metadata.resolver.impl.AbstractMetadataResolver:296] [ ]
- Metadata Resolver FileBackedHTTPMetadataResolver foobar: Metadata
provider failed to properly initialize, fail-fast=false, continuing on in a
degraded state

Thanks,

Max

On Tue, 20 Jul 2021 at 13:00, Cantor, Scott <cantor.2 at osu.edu> wrote:

> If the service had been failfast the IdP wouldn't have started, so it's
> working exactly as intended. I imagine you are also ignoring the fact that
> each individual resolver has its own fail fast settings.
>
> -- Scott
>
>
>

-- 
Max Spicer - Identity Systems Developer
IT Services, University of York
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20210720/1cd5ce6a/attachment.htm>