Page History

...

• The service enhances the research and scholarship activities of some subset of the InCommon community.
• The service requires a subset of R&S Category Attributes and requests only those attributes it absolutely requires. (See below.)
• The service does not require out-of-band negotiation and/or contracts with IdPs.
• The service conforms to a specific subset of the Recommended Practices published by InCommon.
  • The SP is a production SAML deployment.
  • The SP supports SAML V2.0 Web Browser SSO.
  • The SP refreshes and verifies metadata at least daily.
  • The SP's metadata has been provided to InCommon so that it can be published in a human-readable format on the InCommon public web site.  In addition to the metadata required of all InCommon SPs, the following information must also be provided:
    • human-readable service provider display name (mdui:DisplayName)
  • The SP provides appropriate contacts in the metadata.
  • The SP provides its requested attributes in metadata.  (Note that requests for attributes outside of the R&S set will likely require prior agreement with IdP Operators.)
  • The SP intelligently handles errors involving the release of requested attributes.

...

R&S category SPs may request other attributes, but IdP Operators will likely require a prior agreement before releasing those additional attributes.  It is highly recommended that SPs use a minimalist approach to attribute requests, requesting no attributes they do not absolutely need. In the future, if InCommon interfederates with federations in other parts of the world, IdPs in other countries may be operating under laws and regulations which require a true minimalist approach.

...