Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "EGI-Engage:TASK JRA1.1 Proposal for Levels of Assurance"

From EGIWiki
Jump to navigation Jump to search
Line 7: Line 7:


= References =
= References =
[[AARC MNA3.1:Recommendations on Minimal Assurance Level Relevant for Low-risk Research Use Cases https://aarc-project.eu/wp-content/uploads/2015/11/MNA31-Minimum-LoA-level.pdf]]
[AARC MNA3.1:Recommendations on Minimal Assurance Level Relevant for Low-risk Research Use Cases | https://aarc-project.eu/wp-content/uploads/2015/11/MNA31-Minimum-LoA-level.pdf]


= History of edits =  
= History of edits =  
First version from Peter Solagna 30-09-2016
First version from Peter Solagna 30-09-2016

Revision as of 11:28, 4 October 2016

EGI-Engage project: Main page WP1(NA1) WP3(JRA1) WP5(SA1) PMB Deliverables and Milestones Quality Plan Risk Plan Data Plan
Roles and
responsibilities
WP2(NA2) WP4(JRA2) WP6(SA2) AMB Software and services Metrics Project Office Procedures



Introduction

This wiki pages is a work in progress and it contains a draft proposal for the categorization of the levels of assurance in the scope of the EGI CheckIn service. The CheckIn service aggregates authentication and authorization information from different sources, which have different levels of assurance and may release only a subset of the required attributes. The combined information from the aggregated sources of authentication information results in an overall LoA that is embedded in the assertion sent to the services provider in the EGI Federation.


References

[AARC MNA3.1:Recommendations on Minimal Assurance Level Relevant for Low-risk Research Use Cases | https://aarc-project.eu/wp-content/uploads/2015/11/MNA31-Minimum-LoA-level.pdf]

History of edits

First version from Peter Solagna 30-09-2016