User Interface Elements in Metadata
Meeting Baseline Expectations
InCommon will phase in the Baseline Expectations program through much of calendar year 2018. Over time, this program will make some user interface elements mandatory (these are noted below). InCommon recommends adding all of these user elements to your metadata; in particular those that will become mandatory. For more information, see the Baseline Expectations wiki page.
User interface elements in Federation metadata are used by downstream applications to construct rich, dynamic user interfaces (UIs). Specifically, user interface elements in IdP metadata are used for the discovery and error pages at the SP, while user interface elements in SP metadata are used for the login, consent, and error pages at the IdP. The goal is to unify the various user interfaces associated with cross-domain single sign-on, thereby enhancing the overall user experience.
The InCommon Federation Manager has the following input fields:
- Display Name
- Information URL
- Privacy Statement URL (will become mandatory under Baseline Expectations)
- Logo URL (will become mandatory under Baseline Expectations)
By submitting these fields, the administrator adds the corresponding user interface elements to metadata. See the following help pages for guidance:
To better understand how the user interface elements are used, the InCommon Federation entity information pages display the values of all user interface elements on dynamic web pages. The information pages are refreshed daily, in parallel with InCommon metadata.
The SAML V2.0 Metadata Extensions for Login and Discovery specification defines an
<mdui:UIInfo> extension element in SAML metadata. InCommon supports the following child elements of the
An example follows: