Date: Fri, 29 Mar 2024 06:15:41 +0000 (UTC) Message-ID: <1172129031.7537.1711692941051@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7536_1947835259.1711692941049" ------=_Part_7536_1947835259.1711692941049 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
These are frequently asked questions (FAQs) regarding the metadata-d= riven web pages.
For information about Security Assertion Markup Language (SAML), visit t= he SAML section of this wiki.= p>
An Identity Provider (IdP) is a SAML entity that authenticates and ident= ifies users. In a technical sense, an IdP produces SAML assertions containi= ng a security context for an authenticated user.
A Service Provider (SP) is a SAML entity that consumes SAML assertions f= or the purpose of provisioning a security context to applications just-in-t= ime.
A category is a group of SAML entities with similar characteristics. For= example, the Research and Scholarship Category is a group of SPs that suppor= t research and scholarly activities in the InCommon Federation.
The metadata-driven web pages are dynamic web pages whose content is der= ived entirely from InCommon metadata. Examples of metadata-driven web pages= include the entity info pages and the orga= nization info pages.
The metadata-driven web pages rely on metadata in JSON format. An automa= tic process converts XML metadata into JSON metadata once a day, so it may = take up to 24 hours for your changes to take effect. See the MD-driven Web Page A= rchitecture page in this wiki for details.
Oops, that means a broken link was mistakenly entered into metadata. Ple= ase drop us a line at admin@incommon.org and we'll take care of this.
Yes, of course, but the metadata-driven web pages are still in beta and = they are likely to move in the future. If they are moved, we will be carefu= l to install redirects if necessary, but it's your responsibility to mainta= in your own links.
We provide lists of all entities in Federation metad= ata. Individual entity info pages include information about a specific SAML= entity (an identity provider or a service provider) in Federation metadata= .
Each entity page contains:
MDUI elements are User Interface Elements in metadata that are used by downstream ap= plications to construct rich, dynamic user interfaces (UIs). Specifically, = UI elements in IdP metadata are used for the discovery and error pages at t= he service provider, while UI elements in SP metadata are used for the logi= n, consent, and error pages at the identity provider. The goal is to unify = the various user interfaces associated with cross-domain single sign-on, th= ereby enhancing the overall user experience.
Detailed instructions, including screen shots, are available on the User Interface Eleme= nts page in this wiki.
Currently, to insure accurate representation of IdPs on discovery interf= aces, the Federation operator is authoritative for the display names of ide= ntity providers. Therefore it is not possible for site admins to change the= display name of their IdP directly. If you think the display name of your = IdP needs to be changed, please contact admin@incommon.org.
If your service provider is listed in InCommon metadata, then there's an= entity page for it (if not, that's a bug). There is, however, a catch-all = "other" category for SPs that don't have display names. Most likely, your S= P falls into that category. You can fix this simply by providing a display = name for your SP. See the User Interface Elements page in this wiki for details.
By default, a service provider's name is its entityID
in me=
tadata. To change the name to something more readable, simply include an
Since the entity pages attempt to resolve an image resource that resides= in another security domain, some delay is expected. If you find this delay= to be annoying, please contact us (admin@incommon.org) and let us know.
We provide lists of all organizations in Federation meta= data. Individual organization info pages include information about a specif= ic organization in Federation metadata.
Each organization page contains:
All information on these pages is derived from InCommon metadata, and th= erefore the lists of organizations include only those InCommon particip= ants with published metadata. Visit the InCommon Participants page for = a complete list of all participating organizations.
If your organization is not currently a member of the InCommon Federatio= n (and therefore not represented on these info pages), please join the Fede= ration! All InCommon participants are eligible and encouraged to take advan= tage of all that federated identity and access management has to offer.