...
This page describes how an SP metadata administrator adds user interface elements to metadata. These elements are used by IdP implementations to enhance their user interfaces. See the section on software support for a complete list of supported applications.
| Info | ||
|---|---|---|
| ||
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. |
As of the introduction of Baseline Expectations for Trust in Federation in 2018, all user interface elements are required, except where noted.
Contents:
| Table of Contents | ||
|---|---|---|
|
...
A brief SP Description (140 characters or less) of the service may be provided. On computers that support a pointing device (such as a mouse, e.g.), the description will pop up when the user hovers over the SP Display Name.
The <mdui:Description> element is an optional child element of the <mdui:UIInfo> extension element but SP operators are encouraged to supply this informationSP Description is optional, but recommended.
| Anchor | ||||
|---|---|---|---|---|
|
...
The SP Information URL is used to create a link to a service information page. The content of this page should expand on the content of the SP Description field. The Information URL is often presented to the user on the IdP's login page or perhaps the consent page.The <mdui:InformationURL> element is an optional child element of the <mdui:UIInfo> extension element but SP operators are encouraged to supply this information
SP Information URL is optional, but recommended.
| Anchor | ||||
|---|---|---|---|---|
|
...
The SP Privacy Statement URL is used to create a link to a Privacy Statement targeted at end users. Like the Information URL, the Privacy Statement URL is often presented to the user on the IdP's login page or consent page.
The <mdui:PrivacyStatementURL> element is optional (it is a child element of the <mdui:UIInfo> extension element) but will become mandatory under Baseline Expectations. SP operators are strongly encouraged to supply this information.
| Warning | ||
|---|---|---|
| ||
The importance of a Privacy Statement can not be overstated. Users will be instructed to consult the SP's Privacy Statement, lack of which will cause some users to decline attribute release. |
Your POP may already contain statements regarding privacy. One approach, therefore, is to refactor the relevant sections of your POP into a Privacy Statement targeted at the end user.
...
| title | The Relation Between your POP and the Privacy Statement |
|---|
Since you only have one POP, it necessarily applies to all of your SP deployments. In that sense, the granularity of the POP is not sufficient for those sites supporting multiple SPs. On the other hand, your Privacy Statement refers to a single SP deployment.
Please consider content that will be helpful to users, such as detailing the information released to each service. Here are links from GÉANT (the pan-European network) and REFEDS (the international collaboration of federation operators) with some suggestions and guidelines.
- https://wiki.geant.org/display/eduGAIN/How+to+write+the+Privacy+Policy
- https://wiki.refeds.org/display/CODE/Privacy+policy+guidelines+for+Service+Providers
The CTAB provides the following ideas for what you might include:
- Link to whatever privacy policy you have in your Participant Operational Practices (POP)
- Refer to privacy policies available through the EDUCAUSE Higher Education Information Security Council (HEISC):
- HEISC Information Security Guide: https://spaces.at.internet2.edu/display/2014infosecurityguide/Privacy
- Develop a web page that links to established organizational policies related to privacy and include that URL in your metadata. These policies can include data sharing, FERPA release, acceptable use policy (AUP), among others
...
- .
| Anchor | ||||
|---|---|---|---|---|
|
SP Logo URL
The SP Logo URL is a service logo for building graphical user interfaces.The <mdui:Logo> element is optional but will become mandatory under Baseline Expectations (it is a child element of the <mdui:UIInfo> extension element). There are applications that can leverage this element in metadata. A consent interface, for example, may use a visual cue (i.e., a logo) instead of or in addition to the SP Display Name.
...
Generally useful logos will have the following characteristics:
- the The logo should have a transparent background
- the The logo should have a landscape orientation (width > height)
- the The logo should have a minimum width of 100 pixels
- the The logo should have a minimum height of 75 pixels and a maximum height of 150 pixels (or the application will scale it proportionally)
- Contrast should be considered carefully and logos should have enough contrast to support presentation on a white background (e.g., avoid a situation where your logo could be presented as white foreground on on white background)
Logos that meet the minimum width and height requirements can be scaled down by the application as needed. Logos that do not meet the minimum width and height requirements may be ignored by applications.
...