Resource Entitlement Management System Mikael Linden Janne Lauros CSC – IT Center for Science

Access to research datasets 0. Fully public access 1. Researcher has a role/group membership IdP managed/VO-managed 2. Researcher commits to datasets’ licence terms 3. Researcher fills in and submits an application - Dataset owner approves/rejects Or any combination of 1, 2 and 3. Resource entitlement management system (REMS)

Research group Members of the application The REMS concept 3. Circulate to approver 1. Apply for access Dataset 1 Dataset 2 DAC 1 Approver DAC 2 Approver Principal investigator Applicant Research group Members of the application IdP SP 4. Approve REMS Workflow Reports Entitlements 5. Access 2. Commit to licence terms Metadata on dataset 1&2

CASE: Nordic Control Database GWA data from 5500 samples from Estonia, Denmark, Finland and Sweden Nordic Centre of Excellence in Disease Genetics NCoEDG Dataset hosted by EGA, The European Genome-Phenome Archive (www.ebi.ac.uk/ega), a service of the European Bioinformatics Institute

CASE: process for applying access to the Nordic Control Database

Relying on the REMS access rights Identity Provider attributes Service Provider Identity Provider Service Provider entitlements attributes + entitlements attributes REMS Attribute Provider REMS IdP proxy (a) External attribute provider (b) IdP proxy (c) Or a custom REMS integration

The REMS implementation Funded by the ELIXIR ESFRI project A Java portlet on Liferay, using Vaadin framework Open source (LGPL) Discipline-independent Initially bioinformatics Interest also in linguistics and social sciences CSC is going to offer a REMS instance to other ELIXIR nodes Subject to a positive funding decision

REMS demo

Questions? See also the TNC2013 full paper in https://tnc2013.terena.org/core/presentation/18