Difference between revisions of "Current status of pilot"
| Line 34: | Line 34: | ||
''Include explanation about the changes performed and reasons behind.'' | ''Include explanation about the changes performed and reasons behind.'' | ||
*<span style="color:red"> no updates? </span> | *<span style="color:red"> no updates? </span> | ||
| − | * <span style="color:red"> Or perhaps, now that we have more knowledge about S&N, Lookup and Fine Grained Powers Validation, we might want to refine the metrics on that? </span> | + | * <span style="color:red"> Or perhaps, now that we have more knowledge about S&N, Lookup and Fine Grained Powers Validation, we might want to refine the metrics on that?</span> |
| + | * <span style="color:red"> Mention that an additional questionnaire (limited in size) will be added, focussing on technical adequacy, process of connecting and deploying, and documentation. Not related to DBA pilot goals or success criteria, but to collect lessons learned for Chapter 3 of D4.7.</span> | ||
[[Goals and success criteria|Next chapter: 3. Goals and success criteria]] | [[Goals and success criteria|Next chapter: 3. Goals and success criteria]] | ||
Revision as of 11:38, 21 December 2021
Back to main page of D4.7 Initial Running Phase Report
Back to previous Chapter: 1. Introduction
2.1 Catalogue of services and status
To include the National side of catalogue of services. Describe per case what was intended and what has actually been achieved.
Example:
A table with name of the service, URL, description, any type of limitations (for example: access for registered users with an existing profile only), including availability limitations (examples: from April to September or Monday to Friday, 9:00 to 17:00). Additionally, any other interesting information about the service could be included
2.2 Strategy to mitigate infrastructure delays
Describe strategies that have been put into place until now, in order to prevent delays.
- bypass eIDAS authentication and add manual entry for eIDASLegalPersonIdentifier
- develop components between DT and DO to reduce dependency on DO development resources
- use existing infrastructure (SEMPER NODE) for piloting purposes and to deploy DE4A Connector
- temporarily use dummy IdP (ATLAS) with eIDAS
- use simulated data source and eProcedures
- Establish a demonstration of the DE4A Connector and DE/DO Mocks before starting usage in Member States
- Mention that NL will create a temporary and highly focussed MVP fix for the NL DO to be able to pilot the S&N pattern
2.3 Achieved interoperability status
To provide an overview of all possible DE/DO combinations and display the extend to which interoperability is possible
- NL: DO, DT, DR, DE operational; eIDAS operational
- AT: DO, DT, DT operational; DE operational but connected to eIDAS in March 2022; eIDAS operation with version 2.5, profile 1.2
- RO: DO, DT, DR, DE operational (DE=simulated); eIDAS operational
- SE: DO, DT, DR, DE operational (DE/DO simulated); eIDAS operational per January 2022
2.4 Updates in Metrics
To describe (if any) changes in metrics compared to the previous deliverable. Use D4.6 section 2.2 as a basis.
Include explanation about the changes performed and reasons behind.
- no updates?
- Or perhaps, now that we have more knowledge about S&N, Lookup and Fine Grained Powers Validation, we might want to refine the metrics on that?
- Mention that an additional questionnaire (limited in size) will be added, focussing on technical adequacy, process of connecting and deploying, and documentation. Not related to DBA pilot goals or success criteria, but to collect lessons learned for Chapter 3 of D4.7.