...
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
Add brief description of the service, how and where service should be used, typical or key use cases or scenarios (for various groups/levels of end users) and other relevant overview information
Users
...
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:
- An Identity Provider Persistence Service which allows SPs to launch an authentication request to the the last used IdP associated with a device/browser.
- An implementation of SAML Identity Provider Discovery which persists choices in the Persitence Service (1)
- 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:
- SPs integrating the Persistence Service
- SPs integrating the Discovery Service
- End users relying on the service for Discovery and Persistence
Contacts
All operations, business development and stakeholders contacts
...
| Service Manager | Deputy Service Manager | L1 support | L2 support | L3 support |
|---|---|---|---|---|
Service Delivery Model
Add explanation about organisation of service delivery
Service Elements
Service Elements, with brief descriptions (or links) to products, resource types or instances and technical components or software stack, and indications of their types - if they are developed internally (in-house), OSS, or commercial off-the-shelf products or software. Service elements are grouped in two categories:
Technology Infrastructure
Add list and description of products and resources used to deliver main functionalities of the service. Add service technical architecture - i.e. it is good to have a conceptual architectural diagram and topology diagram.
Supporting Infrastructure
The service consists of the following main components:
- Commercial CDNs used to deliver web artifacts (JS, HTML, CSS) to end user browsers
- Frontend software https://github.com/TheIdentitySelector/thiss-js
- 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 is 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 statusAdd list and descriptions of products and resources used to deliver supporting services such as specialized monitoring and measuring systems, configuration management system, issue/request (ticket) management system, reporting system, etc.
Cost Benefit Analysis (CBA)
Provide URL to the last valid CBA.