First Response Dispatched by mod_shib Before Metadata Reloading Completes?

[Nate Klingenstein]

I can make dynamic reloading "work" by having the metadata upload  
process touch /etc/shibboleth/shibboleth2.xml and then issue a curl  
command to a session initiator, triggering the refresh ahead of the  
first user attempt.  Any opinion on whether this is good, bad, or  
ugly, relative to having the metadata upload process forcibly reboot  
shibd?

On Sep 4, 2012, at 14:38 , Cantor, Scott wrote:

> On 9/3/12 7:02 PM, "Nate Klingenstein" <ndk at internet2.edu> wrote:
>
>> I've got a 2.5.0 SP loading a folder of metadata with the new Folder
>> MetadataProvider.  If I place a new metadata file in that folder and
>> touch /etc/shibboleth/shibboleth2.xml, and then try accessing a
>> SessionInitiator, the session initiator will dispatch a response(e.g.
>> Unable to locate metadata for identity provider) before the metadata
>> reloading is complete.
>
> That's because you don't control when the reload happens, it's in the
> background to prevent hung clients. If your use case is such that the
> configuration change has to be tightly controlled, restarting the SP  
> is
> the only way to guarantee that.
>
> -- Scott
>
>
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net