SafeNet IDPrime Virtual Mac 2.0.0
Issue Month: June 2026
Build Details
-
Server: 3.1.0
-
Mac Client: 2.0.0.958
Product Description
SafeNet IDPrime Virtual (IDPV) is a PKI-based software authenticator that uses latest innovation in software-based smart token technology to combine the strong two-factor security of a smart card. It is cost effective and convenient for the software authentication. IDPV emulates the functionality of physical smart cards used for authentication, email, data encryption, and digital signing to enable the use cases such as VDI, BYOD, backup, and mobility on any device. It secures user private key on HSM with user authentication from OIDC compatible Identity providers (IDPs).
Release Description
SafeNet IDPrime Virtual Client v2.0.0.958 includes new features and enhancements.
New Features and Enhancements
-
AES Compatibility for Luna HSM 7.8.2: The client now supports AES-based cryptographic operations.
-
Backward Compatibility Support: Backward compatibility is retained for IDPV Server 2.9 and Luna HSM firmware versions earlier than 7.8.2, ensuring that existing deployments continue to function without requiring configuration changes.
Advisory Notes
Before deploying this release, note the following high-level requirements:
- Once a smart card token has been used to log in with IDPV Client version 2.0.0, it can no longer be authenticated using earlier versions of the IDPV Client. Downgrading the client after the token has been used is not supported.
Localization Support
Operating System is localization based. Therefore, it is automatically managed.
The currently supported languages are:
-
English (default)
-
German
-
French
Default Password
Virtual IDPrime cards are supplied with the following default token password: "000000" (6 zeros) and the Administrator Password must be entered using 48 zeros.
Password Recommendations
We strongly recommend changing all device passwords upon receipt of a token/ smart card as follows:
-
User PIN should include at least 8 characters of different types.
-
PIN character types should include upper case, lower case, numbers, and special characters.
For more information, refer to the 'Security Recommendations' section in SafeNet IDPrime Virtual Server-Client Product Documentation.
Compatibility Information
Middleware
- SafeNet Authentication Client 10.9 R1 (10.9.4565)
Virtual Smart Card Features
Below table specifies the various features that are supported by IDPV:
| Features: | Device: SafeNet IDPrime Virtual |
|---|---|
| Number of Keys | 15 max |
| RSA Key Size | 2048 bit, 3072 bit, and 4096 bit |
| RSA Padding | PKCS#1 v1.5 |
| Hash and Signature Schemes | • SHA-2 512-bit • CKM_SHA1_RSA_PKCS_PSS • CKM_SHA256_RSA_PKCS_PSS • CKM_SHA384_RSA_PKCS_PSS • CKM_SHA512_RSA_PKCS_PSS |
| Supported APIs | PKCS#11 V2.20, PKCS#15, MS CryptoAPI and CNG(CSP,KSP), PC/SC |
| Supported cryptographic algorithms | 3DES (deprecated and will be phased out), AES, SHA-256, RSA upto 2048/3072/4096, RSA PSS |
Compatibility with Third-Party Applications
Following third-party applications are supported:
| Solution Type | Vendor | Product Version |
|---|---|---|
| Browsers | Chrome | v148.0.7778.174 |
| Safari | v26.5 | |
| Outlook | v16.10.103.3 | |
| Apple Mail | Sequoia (15) |
Compatibility with Thales Applications
Virtual IDPrime cards can be used with the following products:
- SafeNet Authentication Client 10.9 R1 (10.9.4565)
Resolved Issues
This section lists the issues that have been resolved in this release. The following table defines the severity of the issues listed in this section.
| Severity | Classification | Definition |
|---|---|---|
| C | Critical | No reasonable workaround exists. |
| H | High | Reasonable workaround exists. |
| M | Medium | Medium level priority problems. |
| L | Low | Lowest level priority problems. |
Resolved Issues
Below are the issues that have been resolved in this release.
| Issue | Severity | Synopsis |
|---|---|---|
| IDPV-12242 | M | Summary: IDPV Mac client hibernation issues |
| IDPV-12096 | M | Summary: User is unable to connect IDPV on MAC due to error 'preferred_username' not found within JWT |
Known Issues
This section lists the known issues that exist in this release. The following table defines the severity of the issues listed in this section.
| Severity | Classification | Definition |
|---|---|---|
| C | Critical | No reasonable workaround exists. |
| H | High | Reasonable workaround exists. |
| M | Medium | Medium level priority problems. |
| L | Low | Lowest level priority problems. |
Known Issues
Below are the known issues that exist in this release.
| Issue | Severity | Synopsis |
|---|---|---|
| ASAC-2227 | M | Summary: When two tokens are connected, one of the token's settings are not accessible in the SAC tool. Workaround: Work with one connected token at a time. |
Related Product Documentation
The following documentation on ThalesDocs is associated with this release:
We have attempted to make the documentation complete, accurate, and useful, but we cannot guarantee them to be perfect. When we discover errors or omissions, or they are brought to our attention, we endeavor to correct them in succeeding releases of the product.
