Difference between revisions of "2016-bidding/CheckIn"

From EGIWiki
Jump to: navigation, search
Line 25: Line 25:
 
**Connectors for IdP supporting: SAML, ODIC, OAuth2, OpenID, X.509  
 
**Connectors for IdP supporting: SAML, ODIC, OAuth2, OpenID, X.509  
 
**Connectors for attribute authorities supporting: SAML 2.0 SAMLAttributeQuery, REST, LDAP  
 
**Connectors for attribute authorities supporting: SAML 2.0 SAMLAttributeQuery, REST, LDAP  
**Connectors for SP supporting: SAML, OIDC, OAuth2
+
**Connectors for SP supporting: SAML, OIDC, OAuth2  
 
***Secure GUI for the registration and management of OIDC clients  
 
***Secure GUI for the registration and management of OIDC clients  
 
**Rules engine  
 
**Rules engine  
 
***Rule based LoA mappings  
 
***Rule based LoA mappings  
***Rule based SP specific entitlements
+
***Rule based SP specific entitlements  
 
*Centralised IdP Discovery Service  
 
*Centralised IdP Discovery Service  
 
**Support for SP specific IdP filtering  
 
**Support for SP specific IdP filtering  
Line 37: Line 37:
 
**Delegated administration  
 
**Delegated administration  
 
**Web based control panel for creating custom enrolment flows  
 
**Web based control panel for creating custom enrolment flows  
**REST API
+
**REST API  
 
**Account linking  
 
**Account linking  
 
*Back-end database for the storage of user information and user profiles  
 
*Back-end database for the storage of user information and user profiles  
Line 63: Line 63:
  
 
*Identity providers who are integrated in CheckIn, only for issues concerning the CheckIn service  
 
*Identity providers who are integrated in CheckIn, only for issues concerning the CheckIn service  
 +
*Attribute providers who are integrated in CheckIn, only for issues concerning the CheckIn service
 
*End users who use CheckIn to authenticate in EGI  
 
*End users who use CheckIn to authenticate in EGI  
 
*Service providers about the interaction of the services with CheckIn proxy
 
*Service providers about the interaction of the services with CheckIn proxy

Revision as of 14:49, 17 October 2016

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


EGI Core services menu: Services PHASE I Services PHASE II Services PHASE III Bids Payments Travel procedure Performance


Go back to the EGI Core Activities Bidding page. 
  • Service name: CheckIn


Introduction

The CheckIn service is the AAI Platform for the EGI infrastructure. The CheckIn service provides the following capabilities:

  • Integration of IdPs (from eduGAIN and individual institutions) with the EGI services through an IdP/SP proxy
  • Credential translation service:
    • SAML2 <--> SAML2
    • SAML2 <--> OIDC
    • SAML2/OIDC --> X.509 through the connection with the RC Auth online-ca
  • Attribute harmonization and policy enforcing

Technical description

The CheckIn service is a critical component of the EGI infrastructure, in many workflows it will be a single point of failure. It is therefore important that it is deployed and operated in a distributed and high available architecture. The bid should include availability and continuity plan(s) for the technical service(s).

The components and the features of CheckIn are the following (developed and integrated in the EGI-Engage project):

  • Idp/SP Proxy based on SimpleSAMLphp
    • Connectors for IdP supporting: SAML, ODIC, OAuth2, OpenID, X.509
    • Connectors for attribute authorities supporting: SAML 2.0 SAMLAttributeQuery, REST, LDAP
    • Connectors for SP supporting: SAML, OIDC, OAuth2
      • Secure GUI for the registration and management of OIDC clients
    • Rules engine
      • Rule based LoA mappings
      • Rule based SP specific entitlements
  • Centralised IdP Discovery Service
    • Support for SP specific IdP filtering
  • User enrollment service based on CoManage
    • Support for user consent for the release of the attributes
    • Acceptance of the terms of use of EGI
    • Delegated administration
    • Web based control panel for creating custom enrolment flows
    • REST API
    • Account linking
  • Back-end database for the storage of user information and user profiles
    • Database cluster supporting streaming replication and Point-in-Time Recovery (PITR) for a period of six months (minimum)
  • Master portal for the integration with the RC Auth online CA
    • Master portal is the access point to online X.509 credentials for all EGI services

Coordination

The following activities of coordination are necessary for the provisioning of the activity:

  • With the IdP/SP for the integration in CheckIn
  • With the EGI Operations for the policy and operational requirements
  • With the Research Infrastructure, VREs and other e-infrastructure where harmonization activities are required

Operations

  • Operations in high-availability of all the components described at the beginning of this section
  • Minimum monthly availability must be: 99%
  • Support request for changes through the GGUS support unit

Support

Provide support to:

  • Identity providers who are integrated in CheckIn, only for issues concerning the CheckIn service
  • Attribute providers who are integrated in CheckIn, only for issues concerning the CheckIn service
  • End users who use CheckIn to authenticate in EGI
  • Service providers about the interaction of the services with CheckIn proxy

Service level targets

The deployment of the services must ensure:

  • Minimum availability/reliability: 99%/99%
  • Response to incident records in GGUS within support hours: Medium (see Description page)

Effort

TBD