20150930 - Meeting minutes, Wednesday, September 30th, 2015 - OpenNCP integration with eID
OpenNCP integration with eID
Sep 30, 2015
Estimated - 13:00 to 14:00 CEST
Performed - 13:00 to 13:45 CEST
AGENDA
a) Status of eID
b) Next Steps
LOCATION
- Wiki+ WorkBench + AdobeConnect
Development Board: https://openncp.atlassian.net/secure/RapidBoard.jspa?rapidView=1
AdobeConnect:
http://ec-wacs.adobeconnect.com/openncp/
Room Passcode: ask @Rui Alves (Unlicensed) or @markus.kalliola
----------------
If you have never attended an Adobe Connect meeting before:
Test your connection: http://ec-wacs.adobeconnect.com/common/help/en/support/meeting_test.htm
Get a quick overview: http://www.adobe.com/products/adobeconnect.html
Adobe, the Adobe logo, Acrobat and Adobe Connect are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.
----------------
PARTICIPANTS
Today's Meeting Participants:
@Alexandre Santos
@Joao Cunha
@Rui Alves (Unlicensed)
@S
@michele.foucart
@Stéphane Spahni
@Massimiliano Masi
@Ioannis Petrakis
@Alice Vasilescu (DG-DIGIT - eID)
@Ortwin Donak
@Soeren Bittins
[holidays] @Markus (Unlicensed)
Invited Members List:
@TE
Daniele Crespi
@Robert Scharinger
@Tomé Vardasca
@Licinio Kustra Mano
@Kostas Karkaletsis
MEETING NOTES
0. Overview
1. Relevant Documentation (What's gathered so far)
The eID approach: The different levels
Level (Requirements) | Mode | Pilot | Action by Pat | Attributes |
|
|---|---|---|---|---|---|
Level 0 | Manual input in the portal. | epSOS | Minimum 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:
@Soeren Bittins: Unforeseen delay with components. Not related to the L2 components itself.
DSig Module used in STORK 2. Breaking the auto-deployment process.
Use in the meantime the Fraunhofer DSig. Not sure about CH or Turkey but should work on all countries.
We are sorry for the delay, Hopefully this week we will have new developments (tomorrow maybe).
@Massimiliano Masi:
@Soeren Bittins: We will provide local configuration just for deployment.
TRC issuer - is now a L3 problem and not L2 - distributed cross-border authentication.
@Alexandre Santos:
@Soeren Bittins: Time for testing.
@Alexandre Santos: change TRC-STS to "talk" to LAM.
@Soeren Bittins: There might be a change in NCP-A. L3 there will be changes in both NCP-A and B.
@Alexandre Santos:
@Soeren Bittins:
TO DO's:
3. AOB
NEXT MEETING