IdP startup issues
cantor.2 at osu.edu
Thu Apr 3 10:52:26 EDT 2014
On 4/3/14, 10:46 AM, "Joel Goguen" <joel.goguen at unb.ca> wrote:
>All of our MetadataProvider entries are defined as
>FileBackedHTTPMetadataProvider types. This is causing us issues with
>starting up the IdP; whenever any one or more metadata sources is
>unavailable, the IdP refuses to start entirely even if the defined
>backingFile exists. Is there some way (preferably without external cron
>jobs) we can have automatically-updating MetadataProvider definitions but
>not have the IdP fail to start when a metadata source can't be reached?
Yes, turn failFastInitialization off.
But you should understand that in doing that, your IdP will start up fine
and then services will just fail to work randomly. Either way you're going
to get called, so a complete solution is probably to look into fixing
whatever's causing problems with metadata sources.
More information about the users