Advanced search
SSI eIDAS Bridge reference implementation
The SSI eIDAS bridge is a pilot focusing on providing a cross-border identity solution compliant with the eIDAS trust framework. It opens a new way of implementing the eGovernment’s once-only…
SOLUTIONCreated: 15/04/2020
Legal Deliverables
In the context of the eIDAS bridge project, we performed an analysis on how eIDAS can legally support digital identity and trustworthy DLT-based transactions in the Digital Single Market, and this is…
CUSTOM PAGECreated: 14/04/2020
Technical Deliverables
This page contains the technical deliverables that have been created during the development of the project. The activities included: The development of software requirements for the specification of…
CUSTOM PAGECreated: 14/04/2020
EUID Wallet Framework and eIDAS bridge?
Hi channel, I'd be really interested to hear the thoughts of this group as to whether the latest reference framework and architecture for the European Digital Identity wallet reinforces and supports the work here at eIDAS bridge or not. Seemingly, the framework has made no specific choice as to the…
DISCUSSIONCreated: 23/02/2022
Stork 2.0 - v.0.9 - PEPS - compilation error
mvn clean followed by mvn install in PEPS project folder fails with following error: [INFO] ------------------------------------------------------------- [ERROR] COMPILATION ERROR : [INFO] ------------------------------------------------------------- [ERROR] /C:/ide/stork/ms-part2/MS-Part2/Software…
DISCUSSIONCreated: 25/11/2015
Would it be possible to use it for ECI?
Hi, The online collection signature uses the most user hostile solution that can be to verify that citizen that signs are real citizen: the dreaded captcha. Using stork (assuming it can be legally be used as a proof of id) would probably be more user friendly. Do you think it would be possible from…
DISCUSSIONCreated: 18/10/2012
Incorrect title for ColleagueRequest and APSelector pages
In the new version (0.5_rev3) of the reference implementation the shown title is now "JavaScript disabled" instead of the more proper messages (that were used in previous version). This happens for following pages (even though JavaScript is not disabled): http://peps:8888/PEPS/ColleagueRequest http…
DISCUSSIONCreated: 01/12/2010
Bug in class SignSW in SAML engine
final String isu = certificate.getIssuerDN().getName(); if (serialNum.equalsIgnoreCase(serialNumber) && isu.equalsIgnoreCase(issuer)) { alias = aliasCert; find = true; } isu.equalsIgnoreCase(issuer) compares the complete DN of a certificate as String. However, the String returned by certificate…
DISCUSSIONCreated: 18/10/2010
If displaying the error status, it should be the most specific one which corresponds to the error message
According to D5.8.1b Interface Specification v1.2.3_rev5.doc: If the subordinate status code is included in the response, then the status message must be the one corresponding to the subordinate status code, not the top-level status code. Our test team has the following suggestion: if the status…
DISCUSSIONCreated: 02/08/2010
Error number displayed is not a number
Our test team has discovered the following problem: For error messages returned from IdP, PEPS shows urn:oasis:names:tc:SAML:2.0:status:Responder as error number. Steps to reproduce (reference implementation 0.4.2): proceed to login page and provide invalid password. Then the following text is…
DISCUSSIONCreated: 06/07/2010
Incorrect error message when SAMLToken validation fails
When an SAMLToken validation fails (e.g. when used keys and certificates do not match), an incorrect message is shown to user: Error generating SAMLToken instead of Error validating SAMLToken The problem is in AUCPEPSManager.processAuthenticationRequest where correct message is logged but wrong…
DISCUSSIONCreated: 02/07/2010
Error message key (colleagueRequest.invalidCountryCode) is shown instead of error message
E.g. when the cpeps.countrycode in peps.xml is incorrect, the following error appears: Address bar: http://peps:8888/PEPS/ColleagueRequest;jsessionid=B51C0A2DEB22BD7761E551... Output: An error (no. 39) has occurred: colleagueRequest.invalidCountryCode. Please click send to proceed. Version…
DISCUSSIONCreated: 02/07/2010