...
You can register your service with the GEANT SAML proxy, so that it can use the existing authentication options such as eduGAIN, social media, guest IdPs, etc.
We need to following data for your service:
The SAML proxy has the Research and Scholarship entity category, and as a result downstream services should not conflict with this, and use similarly compatible protocols:
For instance:
Service Providers that are operated for the purpose of supporting research and scholarship interaction, collaboration or management, at least in part.
Example Service Providers may include (but are not limited to) collaborative tools and services such as wikis, blogs, project and grant management tools that require some personal information about users to work effectively. This Entity Category should not be used for access to licensed content such as e-journals.
And:
The Service Provider is a production SAML deployment that supports SAML V2.0 HTTP-POST binding.
Required information
| Information | Description | Example |
|---|---|---|
| Technical contact |
| support@it.geant.org |
| Support contact | "Generic" support questions for the actual service
Usually the application administrators or the teams that run it. | support@it.geant.org |
| Service name | Very short name to be shown in user interfaces. | GÉANT Wiki |
| Service description | Longer descriptive text, for instance with details like:
| Atlassian Confluence wiki |
| Service URL | The actual URL to the main service | https://wiki.geant.org |
| Metadata | Valid SAML2.0 metadata | a URL to the XML metadata (preferred), or an XML metadata file. |
Note that a public list of all connected services will be made publicly available. This mean that services can not be "hidden".