...
Div | ||
---|---|---|
| ||
|
By now you’ve probably heard about Is my service eligible for the Research & Scholarship (R&S) Category and naturally your first question is: Is my service eligible for R&S? The best way to gauge an answer to that question is to browse ? The authoritative answer is in the Research & Scholarship (R&S) Category document. You can guage a quick answer, though, by browsing the official list of R&S SPs. There you will find:
...
If your service overlaps with the above list of Research & Scholarship services, we encourage you to apply for R&S. Here’s a sequence of steps that will get you there:
- Browse the official list of Review Requirements for R&S SPs and IdPsService Providers, below.
- Review the R&S Application Form
- Read the authoritative Research & Scholarship Entity Category specification
- Read the InCommon Participation Agreement, especially section 9 of that document, which deals with privacy
- Review the Deployment Considerations for R&S document
- Review your entity info page for consistency, clarity, and completeness
- Talk to your Site Administrator about becoming a Delegated Administrator of your service metadata
- Update your metadata (or have your metadata updated) as needed
- Submit the R&S Application Form
...
- Service metadata must be submitted to InCommon and published in a human-readable format on the InCommon public web site.
- The Service Provider refreshes and verifies metadata at least daily.
- The Service Provider is a production SAML deployment that supports the SAML V2.0 HTTP-POST binding (one of numerous SAML V2.0 endpoints in metadata).
- The Service Provider provides both an MDUI
DisplayName
and an MDUIInformationURL
(two User Interface Elements in metadata). - The Service Provider provides both Technical and Administrative contacts in metadata.
- The Service Provider provides requested attributes in metadata. (It is highly RECOMMENDED that the requested attributes in metadata be a subset of the R&S attribute bundle, otherwise a bilateral agreement with each IdP may be required.)
InCommon-certified R&S Service Providers must also meet the following privacy requirements, as do all InCommon Service Providers:
- The Service Provider requests only those attributes required to operate the service.
- The Service Provider will not use attributes for purposes that fall outside of the service definition.
...