Difference between revisions of "2019-bidding/online-ca"

From EGIWiki
Jump to: navigation, search
m (Protected "2019-bidding/online-ca" ([edit=bidding] (indefinite)))
(Replaced content with "{{Template:Deprecated}}")
Line 1: Line 1:
{{Template:Op menubar}} {{TOC_right}} {{EGI_services_and_SM_support_menubar}}
'''Go back to the [https://wiki.egi.eu/wiki/EGI_Services_and_Service_Management_Support:Bidding EGI Services Bidding page].'''
= Service name: Online CA (RCauth)  =
== Introduction  ==
The Online CA capability is a Token Translation Service (TTS) provided through RCauth.eu, generating X.509 certificates upon user request and making long-lived X.509 proxies available through a delegation service.
The Online CA is a critical component to enable access to the EGI infrastructure by a wider range of users. This activity must be operated in tight collaboration with the EGI Check-in Activity.
== Technical description  ==
The components that are part of this core activity are:
*'''Delegation component''': provides the actual token translation between SAML and X.509.
**Highly sensitive component that requires a secure hardware setup including adequate physical security.
**Based on the CIlogon product, and the integration work done in AARC
*'''Certificates signing component''': is the certificate-generation component
**Certificate creations must be protected by hardware security modules
*The delegation component and certificate signing component must be run in accordance with the [https://www.eugridpma.org/guidelines/online-cas IGTF Guidelines for Online CAs]and be capable of at least operations under model (A).
Policy requirements:
*The Online CA must be certified as an at least an IOTA CA in IGTF, and may provide other assurance profiles, subject to eligibility.
*The delegation service must be REFEDS [https://refeds.org/research-and-scholarship R&S]and [https://refeds.org/sirtfi Sirtfi]compliant
*The service should be registered as a Service Provider in a national federation participating to eduGAIN
== Coordination  ==
The Online CA activity will have to coordinate with the following stakeholders:
*IdPs: register where necessary new IdPs
**IdPs must self-certify that they are fulfilling the [https://refeds.org/sirtfi REFEDS Sirtfi]requirements and must be confirmed by either their registrar federation or explicitly by agreement with RCauth that they fulfil the [https://refeds.org/research-and-scholarship REFEDS R&S]requirements
**Online CA operator must collect and manage the repository of explicitly connected IdPs based on the paperwork submitted by these IdPs based on their self-assessment
*SPs: integrate with one or multiple Master portals
In case the OnlineCA contributes to an multi-e-infrastructure OnlineCA service, this may require an additional level of coordination with other entities contributing to the OnlineCA service:
*The EGI Online CA activity must accommodate and be able to act in unison with and under the control of any Policy Management Authority that hold the administrative control over the CA service, its Policy, and its relevant accreditations.
*The EGI Online CA activity must be able and willing to accommodate technical means to securely communicate with other parties that jointly provide the same Online CA service.
*Use of the service component provided by the EGI Online CA activity shall be non-discriminatory and available to all eligible users of the Online CA activity as managed by its Policy Management Authority.
== Operations  ==
*Operation of the delegation component and the online CA in high availability and in compliance with the IGTF and EGI security policies.
*Creating an Availability and Continuity Plan and implementing countermeasures to mitigate the risks defined in the related risk assessment
== Maintenance  ==
*Maintenance of probes to test the functionality of the service
*Requirements gathering
== Software Compliance  ==
*Unless explicitly agreed, software being used and developed to provide the service should:
**Be licensed under an open source and permissive license (like MIT, BSD, Apache 2.0,...).
***The license should provide unlimited access rights to the EGI Foundation and EGI federation member organisations.
**Have source code publicly available via a public source code repository (if needed a mirror can be put in place under the [https://github.com/EGI-Foundation EGI organisation in GitHub].) All releases should be appropriately tagged.
**Adopt best practices:
***Defining and enforcing code style guidelines.
***Using Semantic Versioning.
***Using a Configuration Management framework such as Ansible.
***Taking security aspects into consideration through at every point in time.
***Having automated testing in place.
***Using code reviewing.
***Treating documentation as code.
****Documentation should be available for Developers, administrators and end users.
== IT Service Management compliance  ==
* Key staff who deliver services should have foundation or basic level ITSM training and certification.
** ITSM training and certification could include FitSM, ITIL, ISO 20000 etc.
* Key staff and service owners should have advanced/professional training and certification covering the key processes for their services.
* Providers should have clear interfaces with the EGI SMS processes and provide the required information.
* Providers should commit to improving their management system used to support the services they provide.
== Support  ==
Support will be provided through EGI Helpdesk.
Support hours: eight hours a day, Monday to Friday – excluding public holidays of the hosting organisation(s).
Examples of requested support:
* e-infrastructure service providers, e.g. CRL publishing
* EGI Security: e.g. credentials revocation
* Incident support: to the integrated master portal (end users should not contact directly the OnlineCA, since users' requests for support are directed to the master portal
== Service level targets  ==
Service must be provided with an availability and reliability of 95%.
Response to tickets in EGI Helpdesk within support hours: [[FAQ_GGUS-PT-QoS-Levels#Medium_service|Medium]].
== Effort (EGI-related activities)  ==
Bids planning a total effort for EGI-related work of 5 Person Months/year would allow these services to the extent required for the EGI infrastructure and activities to be addressed appropriately.
== Effort (EOSC-related activities)  ==
Partners are encouraged to submit details of activities and proposed costing of effort for EOSC related activities. This may include activities related to development of new functionality required by EOSC communities (e.g. in the case of RCauth, distributed setup and supporting other EOSC Portal communities) in addition to activities delivering services to these communities.
== References  ==
More information about the Online CA service are available at [http://rcauth.eu/ RCauth homepage]

Latest revision as of 17:56, 20 November 2019

Alert.png This article is Deprecated and should no longer be used, but is still available for reasons of reference.