Pilot Description

LifeWatch-ERIC is a European Infrastructure Consortium providing e-Science research facilities to scientists seeking to increase our knowledge and deepen our understanding of Biodiversity organisation and Ecosystem functions and services in order to support civil society in addressing key planetary challenges.

LifeWatch-ERIC was established as a European Research Infrastructure Consortium by the European Commission Implementing Decision (EU) 2017/499 of 17 March 2017.

During its ESFRI stage, LifeWatch was composed by different national initiatives working on different services and solutions for the research community. During this new ERIC stage, LifeWatch ERIC requires a solutions to provide access to the different services in a common way, as well as organize the different defined groups and roles. Currently, the different LifeWatch services, Virtual Laboratories and Virtual Research Environment manage their own local users, with some exceptions that allows institutional IDs. The technology behind depends on the services, but they mainly support web-based authentication, with some exceptions using, for example, HPC resources.

This pilot activity aims to identify and enhance an existing AAI solutions to be adopted by LifeWatch ERIC as IdP, integrating already existing institutional or social identities in a federated way. This IdP solution will be used for the following purposes:

• To give access to restricted LW services. The services may be restricted because of processing power or storage demands.
• To protect user data and scripts that are stored on the infrastructure (unix home folders etc)
• To give access to data not yet in the public domain. (data in databases , project moratorium period )
• To distinguish between users uploading data to the system (RvLab , eLab, data explorer)
• To give access to openstack configuration interface and computing resources at infrastructure layer.
• To manage roles/groups and authorize them to access specific services.

Pilot goals

Some questions to answer:

• What are the goals of this pilot?

• Why is it in AARC project?

• How this pilot will improve AARC community?

• Why should I use this pilot instead of other solutions?

Description

Main objective of this section is to report detailed informations about pilot. 

Some questions:

• How this pilot works

• Reason to prefer this pilot instead of other existing tool

• Detailed Scope

• others

Components

This section will contain a lists of components used for this pilot.

It is not required to add a detailed description for each component, but 3 important parts are:

1. Add Link to component web page
2. Add a short description to explain its function (not more than 1 raw)
3. Explain why these components have been chosen

An example:

• Component A - Service provider
• Component B - Bring order to chaos
• Component C - Hide my precious treasure

Architecture

This section will provide 2 important parts:

• Graphic representations of pilot architecture

• Graphic representations of workflow

• Lists of all components of related pilot

Use Cases

This section should explain how this pilot works through use cases (at least 2).