SafeNet Drivers

Apr 14, 2026

What's New?

The most recent version of the SafeNet Authentication Client is now available and can be downloaded directly from our website as follows:

How to Download SafeNet Authentication Client?

  1. Select the version of the SafeNet Authentication Client required and click on the appropriate link. It will automatically download the client.
  2. Open the folder to view the downloaded file and launch the installation file.

  3. Click the SafeNet Authentication Client installation file, then follow the prompt to proceed with the installation. 

Which GlobalSign Products Require SafeNet drivers?

GlobalSign's PDF Signing and EV Code Signing Certificates are installed on USB tokens and require drivers to operate. Download links for various operating systems can be found below.

Windows Version Support

SafeNet Version Windows XP Windows Vista Windows 7 Windows 8 Windows 10 Windows 11
10.9-R2
10.8-R9
10.8-R8
10.8-R6
10.8-R5
10.8-R2
10.8
10.7
10.6
10.4
9.0

Downloads

Current Drivers:

Windows: 11, 10, & 8

Legacy Drivers:

Windows: 11, 10, & 8

Windows: 11, 10, 8 & 7

Windows: 10, 8 & 7

Windows: 10, 8 & 7

Windows: 10, 8 & 7

Windows: 10, 8 & 7

Windows: 10, 8 & 7

Windows: 10, 8 & 7

Windows: XP & Vista

NOTE: The new Safenet eToken 5110 (940-B) requires the latest driver (version 10.8-R8). 

Linux Version Support

NOTE: Linux requires the use of Fortify software during the certificate installation process.

SafeNet Version Linux RPM (Red Hat Package Manager) Linux Debian Linux Ubuntu 2004 Linux Ubuntu 1804
10.8
10.7

Downloads

Current Drivers:

Ubuntu​​​​​​​

CentOS

Linux Red Hat Package Manager (RPM)

Linux Debian 

Mac Version Support

NOTE: Mac OS requires the use of Fortify software during the certificate installation process.

SafeNet Version OS X 10.09 OS X 10.10 OS X 10.11 OS X 10.12 OS Catalina OS Big Sur Monterey
10.8 R1
10.8
10.2 Post GA R4
10.2 Post GA R3
10.0

Downloads

Mac OS

Any Issues?

If you are experiencing any of the below issues with the SafeNet Driver, please refer to the workaround:

  • The token is not being recognized.
  • Token not present in Adobe.

Workaround

  1. Within your Adobe Acrobat Pro DC application.
  2. Navigate to Preferences > Signatures > Identities & Trusted Certificates > More... 
  3. Select Digital IDs / PKCS#11 Modules and Tokens > Click Attach Module > Specify the patch of your PKCS#11 file ( /usr/local/lib/libetpkcs11.dylib )
  4. You will now see that your token is visible, as Adobe will be able to recognize this.

If you need any assistance with this workaround, please feel free to reach out to our Support Team. Additionally, we will be providing an update shortly, with the new release of MacOS SafeNet drivers.

Installation Guides

PDF SIGNING

CODE SIGNING

Related Articles

GlobalSign System Alerts

View recent system alerts.

View Alerts

Atlas Discovery

Scan your endpoints to locate all of your Certificates.

Sign Up

SSL Configuration Test

Check your certificate installation for SSL issues and vulnerabilities.

Contact Support