-
4 July 2016 - updated 4 years ago -
2 comments
For real Web integration, eIDAS has to work in the Browser. Currently it doesn't. We try to find a compromise:
https://www.w3.org/community/hb-secure-services/
Tags:
Comments
Log in to post comments
Andrea SERVIDA,
10/07/2016 10:50
Indeed, Browser vendors play a key role to support user's choice in selecting the trust service they wish to use. We acknowledge this key role and on website authentication, for instance, we have already launched a conversation http://ec.europa.eu/newsroom/dae/document.cfm?doc_id=14976
Lionel Antunes,
06/07/2016 12:50
This W3C initiative is welcome, although it comes a bit late. Various solutions to access cryptographic hardware tokens from a browser have been developed and deployed in the last years. These solutions are in use today and they do support, for instance, the creation of eIDAS qualified electronic signatures from a browser. See for instance the eIDAS token specifications: https://www.bsi.bund.de/EN/Publications/TechnicalGuidelines/TR03110/BSITR03110-eIDAS_Token_Specification.html