In order to realize the vision of a Single pan-European Electronic Identification & Authentication Area, some open, common specifications and corresponding building blocks need to be agreed by all involved parties, to put in practice the electronic Identity Management (eIDM) infrastructure which fulfils the STORK requirements and thus facilitate mobility and enhance the Digital Single Market and commercial services. One of these requirements is the consideration of the autonomy and responsibility of each of the Member States to pursue their own eIDM goals and make appropriate arrangements thereto remain unchallenged (principle of subsidiarity) in consideration of existing national technical, organizational and legal aspects, including possible no-gos.
D5.6 PEPS and Middleware demonstrators, by Diana Berbecaru, Bernd Zwattendorfer, Ivo Sumelong, Tim Schneider, Renato Portela, Ricardo Ferreira, Joaquin Alcalde-Moraño, John Heppe
This document accompanies the PEPS and Middleware common software as well as their demonstrators. It describes where and how to use or even to download them.
D5.7.3 Functional Design for PEPS, MW models and interoperability, by Diana Berbecaru, Eva Jorquera, Martine Schiavo, Adrian Johnston, Antonio Lioy, Arnaldur F. Axfjörð, Carlo Luyten, Carlos Ribeiro, Clemens Orthacker, Daniel Martínez, Joaquín Alcalde-Moraño, Luís Felix, Marc Stern, Mario Stoltz, Matthias Schwan, Renato Portela, Sigurður Másson, Tarvi Martens, Thomas Rössler, Wolfgang Bauer.
This document specifies functionally what the STORK Platform will do. Thus it specifies the data (definition and messages) and processes or functionalities. This version is also meant to guide a detailed discussion between all participants, and will be revised accordingly, and also including the specifications of the interface with (MS-)specific functionalities.
D5.8.3 Technical Design for PEPS, MW models and interoperability, by John Heppe
This document specifies the technical design, of which the mayor parts are described in 5 annexes
D5.8.3a Software Architecture Design, by Diana Berbecaru, Eva Jorquera, Joaquin Alcalde-Moraño, Renato Portela, Wolfgang Bauer, Bernd Zwattendorfer, Jan Eichholz, Tim Schneider
This document describes the architecture of the systems that compose the common functionalities of the STORK platform. This description is made from various points of view, each described in a separate chapter. The relevant points of view are applied to each of the two systems: PEPS and MiddleWare (MW), this last one including the Virtual IDP. Each of these systems is described in a separate chapter subdivided in subchapters. As this document is an annex of D5.8.3 Technical Design, please refer to the abstract on the mother document.
D5.8.3b Interface Specification, by Joaquín Alcalde-Moraño, Jorge López Hernández-Ardieta, Adrian Johnston, Daniel Martinez, Bernd Zwattendorfer, Marc Stern, John Heppe
This document specifies the interfaces between PEPS and V-IDP implementations, the interfaces between the Common functionalities of the PEPS and Member State specific functionalities, and the corresponding VIdP interfaces for middleware countries. Thus it specifies the data (definition and messages) and communication protocols.
D5.8.3c Software Design for PEPS architecture, by Diana Berbecaru, Joaquín Alcalde-Moraño, Jorge López Hernández-Ardieta, Renato Portela, Ricardo Ferreira
This document presents the Software design of the PEPS architecture. It pretends to specify the behaviour of the components, in such a way that programmers can work with it. The view which was offered by D5.8.3a, by business process, is now complemented with views by components and classes. This document pretends to specify the behaviour of these components, in such a way that programmers can work with it.
D5.8.3d Security Principles and Best Practices, by Marc Stern
This document aims at the description of security requirements that have to be fulfilled by the interoperability layer developed in the STORK project. As the STORK project is concerned with interoperability issues between governmental institution within the EU, personal data of EU citizens are processed, transmitted and temporarily stored by the interoperability layer. Hence, the assets to protect in STORK are personal information of citizens, issued by governmental or other institutions. Security in this context is concerned with the protection of these assets. A security-specific impairment of the assets typically includes the loss of asset confidentiality, loss of asset integrity or loss of asset availability. The STORK interoperability layer must provide sufficient security functions that counter the identified threats. This document gives a detailed description of identified threats, derived security objectives and necessary security functions that shall be implemented by the STORK system. The threats, objectives and functions define a sound set of security requirements to be fulfilled by the STORK system.
D5.8.3e Software Design for MW architecture for MW architecture, by Ivo Sumelong, Armin Lunkeit, Bernd Zwattendorfer, Tim Schneider
The document describes the components for the MW model. The focus is on the integration of the Austrian and German modules, its combination to a common interoperability layer and a modular architecture to extend the system (referred to as Modular Authentication Relay Service MARS).
D5.9 STORK Basic Building Blocks and infrastructure for eID, by Diana Berbecaru, Bernd Zwattendorfer, Ivo Sumelong, Tim Schneider, Renato Portela, Ricardo Ferreira, Joaquin Alcalde-Moraño, John Heppe
This document accompanies the PEPS and Middleware common software as well as their demonstrators. It describes where and how to use or even to download them.