...
This service reloads a specific <MetadataProvider>
plugin via the id
specified in the MetadataConfiguration. In the case of dynamic resolvers, a reload will clear the state of the resolver's in-memory cache.
...
language | xml |
---|
<MetadataProvider
...
id="nameUsedbelow"
...
xsi:type="Whatever"
...
....
...
>
The underlying web interface, which is managed as an AdministrativeConfiguration, looks like this:
...
http[s]://localhost/idp/profile/admin/reload-metadata?id=nameSpecifiedAbove
The same thing on the command line would be:
...
$
...
/opt/shibboleth-idp/bin/reload-metadata.sh
...
-id
...
nameSpecifiedAbove
The parameters supported and their corresponding command line options are:
Query String | Command Line |
---|
Description | |
---|---|
id | --provider, |
-id |
Metadata Resolver to reload |
Tip |
---|
The identifiers of the resolvers are also listed by the status and metrics administrative flows. |
...
V4.1 includes properties to control various aspects of the flow's behavior using an internally-defined bean that may be overridden if required.
Localtabgroup | |||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
The general properties configuring this flow via admin/admin.properties are:
To replace the internally defined flow descriptor bean, the following XML is required:
In older versions and upgraded systems, this list is defined in conf/admin/general-admin.xml. In V4.1+, no default version of the list is provided and it may simply be placed in conf/global.xml if needed. |