...
All of the input fields below except Display Name are optional for IdPs.
| Info | ||
|---|---|---|
| ||
InCommon expects to roll out will phase in the Baseline Expectations program in early through much of calendar year 2018. This 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. |
IdP Display Name
Typically, the IdP Display Name field will be presented on IdP discovery service interfaces. In practice, if the <mdui:DisplayName> element does not exist in metadata, applications usually fall back on the <md:OrganizationDisplayName> element. The latter is a poor substitute for the IdP Display Name, however, since it assumes an organization deploys at most one IdP.
...
The <mdui:PrivacyStatementURL> element is OPTIONAL, but will eventually become MANDATORY mandatory under Baseline Expectations. It is recommended that IdPs use this URL to point directly (or indirectly through another document) to the IdP's Attribute Release Process.
...
An IdP operator SHOULD supply an <mdui:Logo> element in metadata. A logo will help disambiguate duplicate or similar IdP Display Names on the discovery interface. but will eventually become MANDATORY mandatory under Baseline Expectations.
...