Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Smart card authentication errors in Full Disk Encyrption (FDE)

    • Updated:
    • 2 Mar 2015
    • Product/Version:
    • Endpoint Encryption 3.0 Full Disk Encrypti
    • Endpoint Encryption 5.0
    • Platform:
    • Windows 7 32-bit
Summary

Learn the common issues on smart card authentication and their corresponding solutions.

Details
Public

Below are the common problems in FDE smart card authentication:

When using FDE smart card authentication with a registered user, you are rebooted back to the FDE authentication screen or you receive an error that there is no smart card registered for the user.

Here are the possible causes of the issue:

  • You have a Personal Challenge policy with a null policy value.
  • A PolicyServer administrator or authenticator is created without assigning them a password.

Immediate workaround

As a workaround, do the following while determining the root cause of the issue:

  1. On the pre-boot authentication screen, select Fixed Password from Authentication menu.
  2. Enter your PolicyServer User Name and PIN to access the smart card.

After applying the immediate workaround, do the following to identify the cause of your issue and execute the corresponding procedure.

Check for a Personal Challenge with a null policy value

  1. Log into the PolicyServer MMC.
  2. Access the policy group where the device is located.
  3. View the policy Full Disk Encryption > PC > Login > SelfHelp > PersonalChallenge > PersonalChallege.

    If you do not have the second PersonalChallenge policy, it means that this is not the cause of your issue.

    If you have a PersonalChallenge policy that is null, which means it has no question entered, delete the policy or enter a value.

  4. Sync the device with the PolicyServer and attempt to authenticate with the smart card.

Check for an administrator with no password

Follow any of the following options to verify this cause:

Option 1. Run the query below on your SQL Servers to view any User Name with no password in your database.

Use MobileArmorDB
Go
select userid from mobilearmoruser where usertype <> 0 and (adminpassword is null or adminpassword = ' ' )
union
select userid from mobilearmoruser u inner join usersgroups ug on u.userindex = ug.userindex where (u.usertype <> 0 or ug.usertype <> 0) and (adminpassword is null or adminpassword = ' ')

Option 2. Use the Recovery console.

  1. Log into the device as a PolicyServer administrator.
  2. Select the Access Recovery Console button, which is visible for five seconds after logging into FDE as an administrator.
  3. Select Users from the menu on the left.
  4. On the Users screen, click the user names displayed. A user without a password has the password field displayed in yellow.
  5. Access the MMC and locate the user. This could be an Enterprise Administrator/Authenticator or a Group Administrator/Authenticator.
  6. Do any of the following:
    • Remove the user.
    • Right-click the user and select Change Administrator Password.
  7. Sync the device with the PolicyServer to apply the changes.
  8. Authenticate with the smart card again.

You receive "Password expiration notice" when logging in with your smart card. This happens when the policy ChangePasswordEvery has been applied to the smart card user.

The policy for password expiration should not affect a smart card user, however, it is recommended to set this policy to the maximum value.

If the expiration period is reached, the user will be prompted to register the smart card using the same smart card and PIN. Otherwise, an administrator can log on to the device and access the Recovery Console to extend the user password expiration.

To prevent this from happening again, the policy ChangePasswordEvery should not be applied to the users when configuring a policy group. You can set this to the maximum allowed value of 5000.

To resolve the issue:

  1. Confirm the last communication to PolicyServer using Cisco VPN Client (IPSec) or internal IP address. If none of the above requirements is met, the device may be locked because it fails to communicate with the PolicyServer within the specified period of time.
  2. Check the PIN properties.
  3. Check the username on PolicyServer. Remember that this is case-sensitive.
  4. Check the device group membership.
  5. Vefiry proper insertion of the smart card.
  6. Confirm the Device ID and initiate a Remote Help.

This is a designed functionality of FDE. When authenticating to FDE as an administrator, the administrator policies are sent down to the machine. Therefore, if the next authentication is in a disconnected state, the policies remain as those of the admin.

It is recommended that the Enterprise PolicyPhysicalToken Required is set to "Yes". Alternatively, the administrator authenticating to the device should use a smart card instead of a fixed password.

Premium
Internal
Rating:
Category:
Configure; Troubleshoot; Deploy; Install; Migrate
Solution Id:
1059883
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.