Skip to main content
Skip table of contents

Get started with Smart ID Desktop App

This article includes updates for Smart ID Desktop App 1.12.1.

The SSL certificate for the Hermod public URL must be valid.

Quick overview to using Smart ID Desktop App

Install Smart ID Desktop App

Install the Smart ID Desktop App using the .exe file. See Install and upgrade Smart ID Desktop App for details.

Windows multi-user environment

In a multi-user environment, a protocol handler registry key must be present for each user to launch the Smart ID Desktop App from a web browser. This registry key is required for every user to initiate the Smart ID Desktop App on a machine where the application is already installed.

To create a registry key in a Windows multi-user environment, do one of the following:

  • As a user, start Smart ID Desktop App to create the registry key by default on your machine.
  • As an IT admin, add a registry key to each user in a group policy:
    [HKEY_USERS\*user profile*\SOFTWARE\Classes\com.nexusgroup.plugout]
    @="URL:com.nexusgroup.plugout""URL Protocol"="" 

\*user profile*\ needs to be replaced by the actual user which the registry entry should be applied for.

Start using virtual smart cards

See Get virtual smart card (self-service user) for more information.

Activate tokens

Depending on how your organization has decided to onboard users, you might get an activation link or you can request a virtual smart card or other token via Smart ID Self-Service

Certificates and keys in PKCS#12 format can also be imported directly into Smart ID Desktop App. For more information, see Import PKCS#12 file into Smart ID Desktop App

Manage lifecycle of tokens

For common use cases that are covered by the Nexus Smart ID solution, see Virtual smart card - Use cases for the operator and Virtual smart card - Use cases for the self-service user.

About virtual smart cards in Smart ID Desktop App

Virtual smart cards in Smart ID Desktop App are based on Microsoft Virtual Smart Card (VSC) and Universal Windows Platform (UWP) technology and use the Trusted Platform Module (TPM) chip, which is available in many computers, rather than requiring a separate physical smart card and reader. The solution uses native Microsoft mini-driver for communication with the VSC. 

A virtual smart card that is provisioned with the relevant certificates, can be used by Microsoft Base Smart Card Cryptographic Service Provider (BaseCSP) for most Windows-related use cases. See Features of Smart ID Desktop App

Smart ID Desktop App is integrated to Hermod for message distribution between Smart ID Desktop App and remote provisioning / verification entities such as Smart ID Identity Manager and Smart ID Digital Access component

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.