The Shibboleth IdP V3 software has reached its End of Life and is no longer supported. This documentation is available for historical purposes only. See the IDP4 wiki space for current documentation on the supported version.
MetadataReload
This service reloads a specific <MetadataProvider> plugin via the id specified in the MetadataConfiguration.
<MetadataProvider id="nameUsedbelow" xsi:type="Whatever" .... >The underlying web interface, which is managed as an AdministrativeConfiguration, looks like this:
|
The same thing on the command line would be:
|
The parameters supported and their corresponding command line options are:
Query String | Command Line | Cardinality | Description |
|---|---|---|---|
|
| Required | ProviderId to reload |
This (and status and mdquery and AACLI) is (inferred) GET only.
Do we want to go into any details of that, or givce the HTTP error status's that may be returned? All these feel more interactive that the more REST-full flows.