20151021 - Meeting minutes, Wednesday, October 21st, 2015 - OpenNCP integration with eID

OpenNCP integration with eID

 

 

Estimated - 13:00 to 14:00 CEST

Performed - 13:00 to 13:30 CEST

AGENDA

a) Status of eID

b) Next Steps

 

 

LOCATION

- Wiki+ WorkBench + AdobeConnect

PARTICIPANTS

Today's Meeting Participants:

Rui Alves (Unlicensed)

Alexandre Santos

Joao Cunha

michele.foucart

Ortwin Donak

@Robert Scharinger

 

Invited Members List:

S

Stéphane Spahni

Massimiliano Masi

Ioannis Petrakis

@Alice Vasilescu (DG-DIGIT - eID)

Soeren Bittins

Markus (Unlicensed)

@François

Natasha Carl

Daniele Crespi

@Tomé Vardasca 

Licinio Kustra Mano

Kostas Karkaletsis

 

MEETING NOTES

0. Overview

      • Work Scope

        • Understand the scope of the integration of eID (from e-SENS) into OpenNCP.
      • Time Scope: 
        • OpenNCP Release with LARMS integrated (Level 1) until End of July - Integrated.

        • OpenNCP Release with LAM integrated (Level 2) - ??


1. Relevant Documentation (What's gathered so far)

The eID approach: The different levels

 

Level (Requirements)ModePilotAction by PatAttributes 
Level 0Manual input in the portal.epSOSMinimum D3.6.2  

Level 1

(disconnected mode possible)

LARMS

?? (eSENS eHeath OpenNCP 2.3.0 – floting  componento any portal

Pat gives card, does not type; 

Surname given name gender unique (health) identifier; Varies with each country*

RISK: not 100% sure individual ID

Level 3

(connection to internet and to Country A is needed/national PKIs via centraized service)

LAMb+Pat action

 

Patient confirms (mobile key; Pins of the card)

 

Allows “signed consent”

Authetication is possible

Level 4

(Does not use local functions of the card, uses online “information”; access to PEP)

DCA  Distributed CrossB Authentication

Stork II

Patient confirms (mobile key; Pins of the card) in a PC at the PoCare)

(atributes in the “assertion are the key issue”)

Confirms with National PKI everything;

Confirmes eIDAS.

Level 5

.Advanced Mobile APP solution  (AMAPP)

 

Use their mobile phone for full autentication without card need

  



2. Meeting Minutes:

Alexandre Santos (briefing):

  • Three main points to discuss here today:

1) Presentation from last week of the eID on eHealth domain (meeting from e-SENS in Brussels presented by Masi).

  • Focus was status of each country on STORK 2 and eIDAS infrastructures.
  • Zoi stated that the eID solution Masi's presented from e-SENS may not be the only solution for eHealth domain.
  • Having something more that what we have now is on the horizon.

2) New components:

  • Soeren has connected to our NCP (meaning Portugal NCP);
  • New components are work in progress;
  • We didn't received yet the new components - the first we received had problems with the jar... JAVA problems.
  • We are not testing the new components where the certificates are signed...
  • For now no further developments from since last week.

3) ICT 2015

    • We did a demonstration of the eHealth pilot of e-SENS with live demo with the OpenNCP, eID and Non-Rep
    • With eID - we tested live - scenario: Italian patient in Portugal; We received an IT card from Marcello and were able to retrieve an IT PS from the PT portal with IT card - SUCCESS!

 

Rui Alves (Unlicensed): Timings for EXPANDATHON?

Alexandre Santos: They are working on their Portal to integrate the LAM. My understanding is: this week is a critical one. Until the end of this week we need to have something to implement...

CRITICAL to have components this week to have next weeks for implementations and testing...

 

Rui Alves (Unlicensed): Should we do some action or alert e-SENS about timings?

Alexandre Santos: I have been talking with Soeren Bittins about this. Also about an issue identified with IT card on the ICT.

For now, after this meeting, we should send an e-mail asking for the new components, because it should be almost ready and state it's going to be critical to have it ASAP.

Alexandre Santos: Interest on the e-SENS WP 5 to be able to pilot with some countries that have STORK infrastructure up and running - something that we may have in the future.

 

 

TO DO's:

3. AOB

 


NEXT MEETING