| Info |
|---|
This article includes updates for Smart ID Desktop App 2.0. |
...
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:
...
| Note |
|---|
\*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 operatorand 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.
...