Date: Fri, 29 Mar 2024 00:18:23 +0000 (UTC) Message-ID: <23031661.7257.1711671503827@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7256_22958270.1711671503826" ------=_Part_7256_22958270.1711671503826 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
An InCommon participants registers and publishes its identity prov= ider (IdP) and/or service provider (SP) entity metadata in the InCommon&nbs= p;metadata (registry). By registering, the participant authorize= s InCommon to share that metadata with any person, organization, or system = entity. A Participant may remove its metadata from the InCommon regist= ry at any time.
To publish your metadata, sign into the InCommon Federation Manager web application to= add your entity to the registry.
Every entity descriptor published by InCommon is annotated with a&=
nbsp;RegistrationInfo
element that calls out the globally uniq=
ue identifier of the registrar that registered the metadata. Me=
tadata registered by the InCommon registrar is so marked. See MD-RPI Elements for specifics.
InCommon routinely collects and publishes metadata from non-Partic= ipants. In particular, InCommon imports metadata from other R&E federat= ions via eduGAIN. All metadata is tagged, annotated, and/or organized so th= at consumers may determine the source of individual entity descriptors.
See InCommon's Metadata Registration Practice Statement = for details about the registration and publication process.
Can't find what you are looking for?