News

ID-card digital signing module changes in Chrome web browser

23.04.2014

Starting from Chrome version M35, Linux users have to start using a new digital signing module when signing with ID-card in that web browser.  Same applies to those who use aforementioned combination in information systems.  The important change for information systems is that the communication between module and ID-card is now asynchronous.

Starting from this year the support for NPAPI based plug-in's in Chrome will be phased out, this also includes our ID-card web browser signing module used since 2010.  Additional information regarding the changes to Chrome can be found at: http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html.

First (may 2014, Chrome version M35) the support for NPAPI based plug-in's is removed in Linux distributions and probably in the second half of the year the same will happen in Windows. Additional information can be found here: https://groups.google.com/a/chromium.org/forum/#!msg/chromium-dev/xEbgvWE7wMk/D_07G2lftacJ

To support the new digital signing module there are changes to idCard.js JavaScript library used for digital signing in web browsers. The new idCard.js version (0.20) has parallel support for both old and new digital signing modules. When switching from older JavaScript library you should also consider the API changes resulting from asynchronous use of the new digital signing module.

Its also possible to test on our digital signing module test page: https://openxades.org/web_sign_demo/

End-user changes for digital signing in Chrome web browser will come with ID-software version 3.9


ASK FOR HELP

If you didn't find an answer to your question, send it to our team.



  • See instructions
  • Please estimate your ability to use the computer, so that we can provide you with the best guidance

         

  • Verification failed

How can we improve the article and be more helpful?
Send Close