Date: Fri, 29 Mar 2024 06:11:43 +0000 (UTC) Message-ID: <871297573.17.1711692703590@e89e1969b9fa> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_16_1186554924.1711692703589" ------=_Part_16_1186554924.1711692703589 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Namespace: urn:mace:shibboleth:2.0:metada=
ta
Schema: ht=
tp://shibboleth.net/schema/idp/shibboleth-metadata.xsd
The LocalDynamicMetadataProvider
fetches metadata from=
a local source dynamically as needed. The deployer is responsible for=
populating the local source with data, which may be done while the metadat=
a provider is running. New metadata will be seen automatically the first ti=
me it is requested.
The LocalDynamicMetadataProvider
is used with loca=
l metadata. See the MetadataMana=
gementBestPractices topic for more information.
A common use case will be to use a filesystem directory as the local sou=
rce. A convenience attribute sourceDirectory
is sup=
plied to facilitate this configuration. In this case, the deployer ad=
ds XML files each containing a single <md:EntityDescriptor> element to the
sourceDirectory
.
By default, when using a sourceDirectory
, the file naming c=
onvention will be the lower case hex-encoded SHA-1 digest of the enti=
tyID
, suffixed with ".xml". For example, the metadata for the entity=
with entityID
"urn:test:foobar" will be resolved from the
Note that with the default entityID
digest mechanism, the d=
igested value should not include any leading or trailing whitespace (in par=
ticular, no trailing new line character):
$ echo = -n "urn:test:foobar" | openssl sha1 d278c9975472a6b4827b1a8723192b4e99aa969c