Difference between revisions of "2016-bidding/CheckIn"

From EGIWiki
Jump to: navigation, search
(Support)
 
(13 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Template:Op menubar}}{{Core_services_menubar}} {{TOC_right}}  
+
{{Template:Op menubar}}{{Core_services_menubar}} {{TOC_right}} '''Go back to the [[EGI Core Activities Bidding#PHASE_II_May_2016-December_2017|EGI Core Activities Bidding page]].'''  
'''Go back to the [[EGI_Core_Activities_Bidding#PHASE_II_May_2016-December_2017|EGI Core Activities Bidding page]].'''  
 
 
 
* Service name: Message brokers
 
  
 +
*Service name: CheckIn
  
 +
<br>
  
 
= Introduction  =
 
= Introduction  =
Line 12: Line 11:
 
*Integration of IdPs (from eduGAIN and individual institutions) with the EGI services through an IdP/SP proxy  
 
*Integration of IdPs (from eduGAIN and individual institutions) with the EGI services through an IdP/SP proxy  
 
*Credential translation service:  
 
*Credential translation service:  
**SAML2 &lt;--&gt; SAML2
+
**SAML2 &lt;--&gt; SAML2  
**SAML2 &lt;--&gt; OIDC
+
**SAML2 &lt;--&gt; OIDC  
**SAML2/OIDC --&gt; X.509 through the connection with the RC Auth online-ca
+
**SAML2/OIDC --&gt; X.509 through the connection with the RC Auth online-CA
 
*Attribute harmonization and policy enforcing
 
*Attribute harmonization and policy enforcing
  
= Technical description =
+
The activity supports as well some legacy services for the authorization and authentication of users in EGI:
 +
* Classic catch-all CA
 +
* Catch-all and for dteam VO VOMS
 +
 
 +
= Technical description =
 +
 
 +
The CheckIn service is a critical component of the EGI infrastructure, in many workflows it will be a central service that enables access to users to the distributed services offered by EGI resource centres. It is therefore important that the CheckIn service 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
 +
 
 +
Other services not related to CheckIn:
 +
*Catch-all VO membership management for small research teams and the long tail of science, as well as for infrastructure VOs including DTEAM: a VOMS service for the X509 credentials and other attribute authorities to support user grouping with other authentication technologies.
 +
*Catch-all X.509 certification authority for homeless users
 +
 
 +
== 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  ==
  
The CheckIn service is a critical component of the EGI infrastructure, in many workflows it will be a single point of failure. It is threfore 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).
+
*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
  
The components and the features of CheckIn are the following (developed and integrated in the EGI-Engage project):
+
== Support ==
* 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
 
* User enrollment service based on CoManage
 
** Support for user consent for the release of the attributes
 
** Acceptance of the terms of use of EGI
 
** Account linking
 
* Back-end database for the storage of user information and user profiles
 
* 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==
+
Provide support to:  
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 ==
+
*Identity providers who are integrated in CheckIn, only for issues concerning the CheckIn service
* Operations in high-availability of all the components described at the beginning of this section
+
*Attribute providers who are integrated in CheckIn, only for issues concerning the CheckIn service
* Minimum monthly availability must be: 99%
+
*End users who use CheckIn to authenticate in EGI
* Support request for changes through the GGUS support unit
+
*Service providers about the interaction of the services with CheckIn proxy
  
== Support ==
+
== Maintenance ==
  
Provide support to:
+
*Requirements gathering
* Identity providers who are integrated in CheckIn, only for issues concerning the CheckIn service
+
*Documentation
* End users who use CheckIn to authenticate in EGI
+
 
* Service providers about the interaction of the services with CheckIn proxy
+
== Software as a service ==
* Second level support for the RC Auth online-CA
+
In the bid, please provide also information about the possibility to provide the service to external consumers as a Software as a Service. If the provisioning of the activity as a SaaS implies additional effort or other costs, please report these costs separately, not as part of the overall budget of the bid.
 +
 
 +
= Service level targets  =
 +
 
 +
The deployment of the services must ensure:
  
= Service level targets =
 
The deployment of the services must ensure:
 
 
*Minimum availability/reliability: 99%/99%  
 
*Minimum availability/reliability: 99%/99%  
*Response to incident records in GGUS within support hours: Medium (see [https://wiki.egi.eu/wiki/FAQ_GGUS-PT-QoS-Levels#Medium_service Description page])  
+
*Response to incident records in GGUS within support hours: Medium (see [https://wiki.egi.eu/wiki/FAQ_GGUS-PT-QoS-Levels#Medium_service Description page])
 +
 
 +
= Effort  =
  
= Effort =
+
Bids planning a effort between 12 and 18 Person Months/year would allow these services and activities to be addressed appropriately.
TBD
 

Latest revision as of 09:44, 25 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

The activity supports as well some legacy services for the authorization and authentication of users in EGI:

  • Classic catch-all CA
  • Catch-all and for dteam VO VOMS

Technical description

The CheckIn service is a critical component of the EGI infrastructure, in many workflows it will be a central service that enables access to users to the distributed services offered by EGI resource centres. It is therefore important that the CheckIn service 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

Other services not related to CheckIn:

  • Catch-all VO membership management for small research teams and the long tail of science, as well as for infrastructure VOs including DTEAM: a VOMS service for the X509 credentials and other attribute authorities to support user grouping with other authentication technologies.
  • Catch-all X.509 certification authority for homeless users

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

Maintenance

  • Requirements gathering
  • Documentation

Software as a service

In the bid, please provide also information about the possibility to provide the service to external consumers as a Software as a Service. If the provisioning of the activity as a SaaS implies additional effort or other costs, please report these costs separately, not as part of the overall budget of the bid.

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

Bids planning a effort between 12 and 18 Person Months/year would allow these services and activities to be addressed appropriately.