reload-metadata & multiple metadata providers

[Rod Widdowson]

Reloading the metadata service is entirely different and would involve saying "reload-service".  It completely restarts the service
including reloading all files.

Reloading metadata providers is about reloading one provider at the "level down" from that, so in your case you either have two
files and that is the level at which you can reload or you have one file where the topmost element is a chaining provider.  Either
way you cannot descend into the next level down

So if you had a single file looking roughly like this

<MetadataProvider type="chaining">
	<MetadataProvider type="chaining" id=" ShibbolethMetadata">
		<MetadataProvider type="chaining" id="NEFED">
	</MetadataProvider>
	<MetadataProvider type="chaining" id="NebraskaShibbolethMetadata ">

And so on, you can reload NebraskaShibbolethMetadata an ShibbolethMetadata, but not NEFED.

Similarly if you had two files one for NebraskaShibbolethMetadata and the other ShibbolethMetadata 

Either way, you only get to chose from those two.

I suspect the team would entertain and RFE (if one was forthcoming) to look at the idea of allowing recursive descent into
sub-providers, but a full fix might implicate the status page and gauges so it might blow up and not happen....

/Rod

> -----Original Message-----
> From: users <users-bounces at shibboleth.net> On Behalf Of Ryan Rumbaugh
> Sent: 26 July 2019 16:44
> To: Shib Users <users at shibboleth.net>
> Subject: RE: reload-metadata & multiple metadata providers
> 
> Right, I can reload the metadata resolver service, my particular issue is when using the bin/reload-metadata.sh
> (/idp/shibboleth/reload-metadata?id=XXXX) service which allows us to reload a particular metadata entry in the metadata-
> providers.xml file instead of the entire service.
> 
> 
> --
> Ryan Rumbaugh