Token Support

This section focuses mostly on Windows as the most popular operating system.

Tested tokens

• Estonian ID Card
• Finnish ID Card
• Latvian ID Card
• Lithuanian ID Card
• Belgian ID Card
• Luxembourgian LuxTrust Smartcard
• Aladdin eToken

General installation instructions

• Install your country specific eID driver software.
• Install Chrome Token Signing Software for giving eSignatures in Google Chrome.
  • You can find the latest version at https://github.com/open-eid/chrome-token-signing/releases
• Restart Chrome
• Insert smart card to the reader
• Try testing at https://hwcrypto.github.io/hwcrypto.js/sign.html

Estonia

• Install Estonian ID-Card software (https://www.id.ee/en/article/install-id-software/). Chrome Token Signing Software is already included in the main installer.
• Restart Chrome
• Everything should work out of the box.

Limitations

• EstEID RSA 1024 first generation cards support only SHA1 and SHA224

Lithuania

• Install CryptoTech Software (http://www.nsc.vrm.lt/downloads.htm)
  • Lithuanian old pre 2012 card with works with Gemalto Classic Client 4.4.06
• Install Chrome Token Signing Software
• Restart Chrome
• Try signing. Everything should work out of the box.
  • You can test at https://hwcrypto.github.io/hwcrypto.js/sign.html

If signing fails, then make sure your certificates have been loaded to the Windows Certificate Store

• If you try signing and it fails with the error: no_certificates
• Open Windows Certificate Store (certmgr.msc)
• See if your certificates have been loaded under the Personal certificates section
• If your certificates are not loaded then restart CryptoCard Monitor
• You should see the following message: "A new smart card has been detected. Certificates from the card have been registered to Windows Certificate Store"

Limitations

• Does not support SHA224
• Lithuanian first generation cards support only SHA1

Latvia

• Install Latvian eID middleware (https://www.eparaksts.lv/en/eid-card/downloads/eid-card-middleware)
• Install Chrome Token Signing Software
• Restart Chrome
• Try signing. Everything should work
  • You can test at https://hwcrypto.github.io/hwcrypto.js/sign.html

Enabling PKCS#11 (optional)

You can configure Chrome Token Signing extension to use Latvian PKCS#11 driver

• Open Chrome extensions page at chrome://extensions/
• Open Token Signing options page
• Tick "Force Pkcs11 backend on Windows"
• Find Latvian PKCS#11 driver file OTLvP11.dll (most likely here C:\Windows\SysWOW64\OTLvP11.dll)
• Copy the full path of the driver file to the extension's input field "PKCS#11 module path on windows" (for example: C:\Windows\SysWOW64\OTLvP11.dll)

Limitations

• Does not support SHA224
• Does not support SHA384
• Does not support SHA512

Finland

• Install Finnish eID Card Reader Software (https://dvv.fi/en/card-reader-software)
• Install Chrome Token Signing Software
• Restart Chrome
• Try signing. Everything should work
  • You can test at https://hwcrypto.github.io/hwcrypto.js/sign.html

Belgium

• Install Belgian eID Software (https://eid.belgium.be/en)
• Install Chrome Token Signing Software
• Restart Chrome
• Try signing. Everything should work

Luxembourg

• Install LuxTrust Middleware (drivers.luxtrust.lu)
• Install Chrome Token Signing Software
• Restart Chrome
• Try signing. Everything should work

Aladdin USB eToken

• Install SafeNet Authentication Client Software
• Install Chrome Token Signing Software
• Restart Chrome
• Try signing. Everything should work