This page contains service description outlining how and where service should be used, targeted users, service delivery model and service elements and topology.

RESPONSIBLE: Information provided in this page is initially populated by the development team (during the transition phase), and revised based on the need or in a yearly service check by service_name Service Manager, with exception of CBA which remains the responsibility of business development team.

Service Description

The RA21 Discovery and Persistence Service (aka thiss.io) is an implementation of the RA21 recommendations for Identity Provider discovery and persistence. The service consists of the following parts:

  1. An Identity Provider Persistence Service which allows SPs to launch an authentication request to the the last used IdP associated with a device/browser.
  2. An implementation of SAML Identity Provider Discovery which persists choices in the Persitence Service (1)
  3. An MDQ implementation covering at least eduGAIN SAML metadata and implementing extensions for metadata search.

Users

The users of the RA21 Discovery and Persistence Service are:

  1. Service Providers integrating the Persistence Service.
  2. Service Providers integrating the Discovery Service.
  3. End users relying on the service for Discovery and Persistence.

Contacts

All operations, business development and stakeholders contacts


Service OwnerDeputy Service OwnerL1 supportL2 supportL3 support
 
   

Service Delivery Model

Add explanation about organisation of service delivery

Service Elements

The service consists of the following main components:

  1. Commercial CDNs used to deliver web artifacts (JS, HTML, CSS) to end user browsers.
  2. Frontend software https://github.com/TheIdentitySelector/thiss-js, to be implemented by Service Providers. 
  3. A backend consisting of an MDQ implementation with search extensions enabled (currently pyff.io).

Technology Infrastructure

cf above - diagram TBD

Supporting Infrastructure

All software components except the CDN are configured and maintained using cosmos+puppet infrastructure at https://github.com/TheIdentitySelector/thiss-ops. Documentation in the docs directory. Monitoring is done using nagios generated automatically from service configuration. Additional monitoring is done using pingdom. Status.io is used to communicate service status.

Cost Benefit Analysis (CBA)

Provide URL to the last valid CBA.