Knowledge Base

Setting up a Sectigo token takes four steps: retrieve your token password from the encrypted email, install the SafeNet Authentication Client, insert the token, and change the password. Do the first two before the hardware arrives and you will be signing the day it lands.

This article provides troubleshooting steps to resolve issues where a SafeNet USB Token is not detected on a Windows system. It covers remote access limitations, smart card reader driver issues, SafeNet Authentication Client installation problems, and hardware-related checks.

Use this article to identify a token-access or certificate-loss problem and seek help without taking actions that could destroy signing credentials.

Find guidance for tracking your Sectigo hardware token, addressing delivery problems, and investigating customs requirements.

Learn how to change and protect the user password for your Sectigo-supplied SafeNet token, and avoid unsafe password-recovery attempts.

Sectigo sends a shipment notification and a separate encrypted token-password email when your hardware token ships. Use independent checks before opening protected content or responding to unexpected requests.

Use these checks to locate the encrypted token-password email for your Sectigo hardware token order or get help if it remains missing.

Sectigo protects your hardware token password using Microsoft Purview Message Encryption; follow the access option available for your email account to open the protected message.

When your certificate order includes a Sectigo-supplied hardware token, you receive a physical USB token, a shipment notification, and a separate encrypted email containing your token password. 1

This article explains how to locate a certificate's thumbprint in the SafeNet Authentication Client on Windows. The thumbprint is often needed for authentication, troubleshooting, or code-signing.