Unable to log on to Windows using Java 72k eToken after authenticating successfully at preboot

Technical Articles ID: KB74223
Last Modified: 2024-01-06 09:35:04 Etc/GMT

Environment

Drive Encryption (DE) 7.X

SafeNet Authentication Client (middleware client)

NOTE: SafeNet Inc has purchased Aladdin Knowledge Systems Ltd.

Java 72k eToken

For details of DE 7.x supported environments, see KB79422 - Supported platforms for Drive Encryption 7.x.

Problem

After a user has successfully authenticated at preboot, authentication fails at the Windows logon when the user uses the Java 72k eToken to authenticate.

After entering the password for the Java 72k eToken, the user is asked to insert the Smart Card.

Removing and reinserting the smart card allows the user to successfully authenticate and access Windows.

Cause

Investigation of this issue has shown that the problem is based on a reset issue within the vendor's middleware. The problem is that the smart card reader isn't reset, so access to the smart card isn't given. The only option to manually reset the reader is to physically remove the smart card. This user action causes the reader to reboot and allows the smart card to be detected correctly.

Solution

An updated middleware is now available to resolve the problem.

On the operating systems where this issue is reported, update the middleware to Safenet Authentication Client 8.1.

Access the "SafeNet Technical Support or Drivers and Utilities" section to obtain the update at the Customer Support Portal.

Affected Products

Languages:

This article is available in the following languages:

Knowledge Center

Unable to log on to Windows using Java 72k eToken after authenticating successfully at preboot

Environment

Problem

Cause

Solution

Affected Products

Languages:

Title

Title

Knowledge Center

Unable to log on to Windows using Java 72k eToken after authenticating successfully at preboot

Environment

Problem

Cause

Solution

Affected Products

Languages:

Choose your region

Title

Title