User Interface Elements in Metadata
| Info | ||
|---|---|---|
| ||
As of the implementation of InCommon expects to roll out the Baseline Expectations program in early 2018. This program will make some 2018, additional user interface elements are mandatory (these are noted below). InCommon, however, 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 these input fields for user interface elements:
| User Interface Element | Required? | Recommended? |
|---|---|---|
| Display Name | Yes | Yes |
| Description | No | Yes |
| Information URL | No | Yes |
Privacy Statement URL |
...
Yes | Yes | |
| Logo URL |
...
| Yes | Yes |
By submitting these fields, the administrator adds the corresponding user interface elements to metadata. See the following help pages for guidance:
REFEDS's Simple Steps for Successful Federated Login also provides good general information for improving your users' experience.
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.
...