Date: Fri, 29 Mar 2024 10:25:53 +0000 (UTC) Message-ID: <916050879.7839.1711707953046@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7838_2015103437.1711707953044" ------=_Part_7838_2015103437.1711707953044 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The application can generate a metadata-providers.xml
confi=
guration appropriate for use in the Shibboleth IdP. There are 2 ways to acc=
ess this configuration: through a web endpoint or a file.
Web endpoint
A request can be made to the ${ui.baseUrl}/=
api/MetadataResolvers
to get the current configuration
File export
A file can be periodically written to disk. Set th=
e application property shibui.metadataProviders.target
, pointi=
ng to a spring file resource. Note that there is no value set by default, a=
nd nothing will be written out by default. A file, once defined, will be wr=
itten every 30 seconds by default. To change the rate, set the shibui=
.metadataProviders.taskRunRate
application property, in milliseconds=
.
If writing the file out, one should use a mount in the docker container = for the destination. While a bind mount might be easiest, if running on a W= indows host, one might run into problems. This is easily avoided by using a= volume instead. Refer to https://docs.docker.com/storage/ for more info= rmation.