You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »


You can register your GEANT project or related service with the GEANT SAML proxy, so that it can use the existing authentication options such as eduGAIN, social media, guest IdPs, etc.

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

 Please send the following information to aai-is@lists.geant.org:


InformationDescriptionExamplestored in/mapped to (internally)
Technical contact
  • authentication issues
  • security issues
  • privacy issues

Can be a list

support@it.geant.orgcontacts['technical']
Support contact

"Generic" support questions for the actual service

  • how does it work

Usually the application administrators or the teams that run it.

Can be a list.

support@it.geant.orgcontacts['support']
Service name

Very short name to be shown in user interfaces.

GÉANT Wikiname
Service description

Longer descriptive text, for instance with details like:

  • intended audience
  • its status (production, testing)
  • when it was set up
  • the software type/version it runs

Can contain URLs

Atlassian Confluence wiki, production instance.description
Service URLThe actual URL to the main servicehttps://wiki.geant.orgurl
MetadataValid SAML2.0 metadata

a URL to the XML metadata (preferred), or an XML metadata file.


Please note that a list of all connected services will be made publicly available. This mean that your service can not be "hidden" or anything.

As a result, services are required to have a valid TLS configuration (including their SAML endpoints) using certificates from a trusted CA.

Supplied information

The SAML proxy will always provide the following attributes to its downstream services:

FIXME: Do we send OID only? Or OID+name?

SAML attributeexample valueremarks
uidfederated-user-1234Unique user ID, always available.
mailuser@domainDefaults to the string 'invalid_email_needs_updating' if none was provided by the upstream IdP
displayNameRobert WagnerDefaults to the string 'first_name last_name' or similar if bit aren't provided by the upstream IdP
isMemberOf
  • GN_Services:GN Project Participants

  • GN4Phase3:WPs:WP9

  • GN4Phase1:SAs:GN4-1_SA3-T4

Multivalued attribute listing the CAMS group memberships.

Service monitoring

At some stage there will be some monitoring set-up, to help ensure the service is conforming to basic requirements. The monitored items are expected to include:

  • Reachability of the Service URL
  • Configuration of the web server's TLS stack, using the SSLlabs test.
  • Clock skew, using HTTP Date header

Any alarms that are generated by these checks will be sent to the technical contact(s) that you configured.

  • No labels