OpenNCP integration with SMP

Aug 5, 2015

Estimated - 13:00 to 14:00 CEST

Performed - 13:00 to 14:30 CEST

AGENDA

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.
  ----------------

Today's Meeting Participants:

@Licinio Kustra Mano

@Joao Cunha

@Rui Alves (Unlicensed)

@Markus (Unlicensed)

@Uwe Roth

@François

@TE

@S

[holidays] @Stéphane Spahni

@Marcello Melgara

Invited Members List:

Massimiliano Masi

Alexandre Santos

Kostas Karkaletsis

Heiko Zimmermann

Ortwin Donak

Work Scope
- USE SMP to convey public information of TSL (Certificates, End Points) and International Patient Search Mask;
  - TSL files should be removed and replaced by SMP Signed Information files.
  - (Maybe not to delete the TSL EDITOR, explore TSL EDITOR to prepare the information to submit to the SMP )
    - INTEGRATE a REST client to CRUD the information...
  - About "International Patient Search Mask", how to include on the SMP configs
    - Can be a child on an XML node on the SMP file.
- USE SMP to the establishment of VPN?
  - Certificates, End Points and OpenSwan Config (PRIVATE)
- OUT OF SCOPE BY NOW - Automate the configuration of OpenNCP
Time Scope:
- New release OpenNCP 2.3.0, foreseen for September 2015. on hold
Relevant Documentation:
- SMP:

@Licinio Kustra Mano: overarching approach for the e-SENS document:
- epSOS Central Configuration Services - Specifications
  - It was never implemented. But even so, the specified solution is referenced in the epSOS Deliverables;
- epSOS Central Configuration Services - As IS
  - A simplified solution was adopted, but needs to be better described for further enhancements and improvements.
  - Improve Massi document... that was no officially released.....
- Gap between Specs. and As IS scenarios towards an OPERATION READY scenario
  - ...
- How can we use SMP/SML to close some of the gap and open issues
  - What current limitations or relaxations ca be resolved with moving to an SMP/SML.
@Markus (Unlicensed):
- This is an e-SENS task that is being supported by EXPAND/OpenNCP Community.
  - We MUST make sure that everyone understands that the request is an e-SENS pilot request and not something that the OpenNCP just decided to do.
- Good approach, instead of stop everything, work for clarifying what opportunities are there to use the SMP as bridge to remove relaxations adopted during epSOS.
@Joao Cunha Provide an overview on the work done so far: