Date: Thu, 28 Mar 2024 22:50:52 +0000 (UTC) Message-ID: <712049931.7137.1711666252042@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7136_485956110.1711666252042" ------=_Part_7136_485956110.1711666252042 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The Incommon Federation and research and education (R&= E) identity federations worldwide rely on the Security Assertion Markup Language (SAML) to perform federated aut= hentication and access management.
The SAM= L metadata standard belongs to the family of SAML standards. A SAML metadata docu= ment describes a SAML deployment such as an Identity Provider or a Service = Provider. Deployments sha= re metadata via federation-operated metadata registr= ies to establish a baseline of trust and interoperability.
In addition the main SAML metadata standard= , InCommon and the global R&E federation community also rely on a numbe= r of metadata extensions such as SAML V2.0 Metada= ta Extension for Entity Attributes and SAML V2.= 0 Metadata Extensions for Login and Discovery User Interface Version 1= .0 (MDUI) to improve interoperability.
When interoperating with services registere= d in the Incommon Federation, you'll need to publish your Identity Provider= (IdP) or Service Provider (SP) metadata using Federation Manager.
A note to system administrators: This publi= shed metadata is what your = ;fellow Incommon = Federation participants rely on= to locate and integrate with your IdP or SP. A copy of metadata that may r= eside on your server has no bearing on interoperation within the Incommon Federation.
Can't find what you are looking for?