RSA Authentication Agent 7.3.3 for Windows prompt does not appear after the first reboot of Windows 10 when McAfee SafeBoot is installed
Originally Published: 2018-02-20
Last Modified: 2022-06-20
Article Number
Applies To
RSA Product/Service Type: Authentication Agent for Windows
RSA Version: 7.3.3
Issue
- When McAfee SafeBoot (now known as McAfee Drive Encryption [DE]) is installed on a machine running Windows 10 that also has the RSA Authentication Agent 7.3.3 installed, every time the machine is booted. the RSA SecurID prompt does not display.
- Once logged in, if a user locks the machine and unlocks it, it starts prompting for RSA SecurID credentials and the user authenticates successfully.
- Subsequent logins work as expected.
- The SecurID prompt does not appear after the first reboot on Windows 10.
- Tried changing the Credential Manager setting and enabling Exclude the Third-party Credential Providers.
- This behavior has been tested on multiple machines and recreated consistently.
- Exclude the Microsoft Password Credential Provider = Not configured
- Exclude the RSA Credential Provider for disconnect auth = Not configured
- Exclude the RSA Smart Card Credential Provider = Not configured
- Exclude the Third-party Credential Providers = Enabled
- The auto registration client is installed.
Cause
DE/EEPC does not currently support any third-party Windows credential provider integrations. These third-party credential providers are conflicting with the DE/EEPC credential provider because, on Windows systems, it is not possible to chain the DE/EEPC credential provider.
Resolution
The customer needs to engage McAfee to find a workaround. It might be possible to configure SafeBoot to not use its' MfeEpeCredentialProvider, but that needs to be handled by McAfee.
The RSA Authentication Agent 7.3.3 for Windows is functioning as designed.
Related Articles
Selective authentication with RSA Authentication Agent 8.0 for Web for IIS where challenge groups are not working 37Number of Views Offline lockout does not get cleared by online authentication using RSA Authentication Agent 7.2.1 for Windows 49Number of Views Node secret mismatch error when authenticating with an RSA Authentication Agent for Windows when NetMotion is installed 271Number of Views RSA MFA Agent for Windows logs a warning that "System cannot access location data for this computer" 36Number of Views How to use Microsoft Windows command prompt to validate the checksum values of RSA Authentication Manager files 85Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide
Don't see what you're looking for?