This page gives software recommendations to service providers regarding the Metadata Extensions for Login and Discovery, often referred to as the mdui extensions.
Note that federations may (and are expected to) make further recommendations.
IdP 2.3 (and later) supports the use of these extensions in its login and error pages, and the default page makes use of some of them.
The uApprove consent engine, compatible with Shibboleth IdP 2.2 (and later), also makes uses of these elements. The consent page planned for the Shibboleth IdP 3.0 will make use of the mdui extension elements as well.
SPs following these recommendations assure their users of the best possible experience at the IdP. Federations are encouraged to discuss these recommendations and the corresponding recommendations for IdPs with their customers.
mdui Extension Elements
| Taglib support available in IdP | IdP Default Login Page | uApprove > 2.3 (with IdP > 2.3) | IdP 3.0 Consent Page |
|---|---|---|---|---|
| Yes | Yes | Yes | Planned |
| Yes | Yes | Yes | Planned |
| No | No | No | |
| Yes | No | Yes | Planned |
| Yes | No | Yes | Planned |
| Yes | Yes | Yes | Planned |
mdui Extension ElementsContent should be provided in one or more appropriate languages subject to federation requirements. |
A concise, user-recognizable display name should be provided. It is strongly recommended that the <mdui:DisplayName> element be treated as a required child element of the <mdui:UIInfo> element.
A brief description (100 characters or less) of the service should be provided.
On systems that support a pointing device (such as a mouse), the content of the <mdui:Description> element will pop up when the user hovers over the SP display name.
No recommendations are currently made.
A link to a more comprehensive information page may be provided. This page should expand on the content of the <mdui:Description> element.
A link to the SP's Privacy Policy may be provided.
Some federations (such as the InCommon Federation) strongly encourage a Privacy Policy by noting the omission of this element on their user interfaces. |
Usable logos have the following characteristics:
Logos that are too small are ignored, while logos that are too large will be scaled as best as possible.