Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-41092: Users are unable to MFA login to the Windows machines

Authentication Service ,  

28 September,20 at 11:07 PM

Problem: Users are unable to MFA login to the Windows machines

Cause: User added a Connector for a NEW NON Prod On-Prem PAM installation in a Child Domain since the tenant URL was not set in the Production Zones which caused this issue as it now saw two connectors with different tenant URL's.

Resolution: Please use the local admin account to run dzflush and then dzrefresh to rebuild the cache in order to login with MFA successfully.

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-20210: Common Questions Regarding Centrify DirectControl and CoreOS article[How To] Enable Symantec VIP MFA for Centrify Server Suite on Linux Part I articleKB-11071: Logging Into a Windows Machine that is MFA Enabled, the Message is Seen "Unable to load profile: Profile does not exist" article[How To] Enable Symantec VIP MFA for Centrify Server Suite on Linux Part III article[HOWTO] Guide to Enabling MFA for PowerShell Remoting article[How To] Enable Symantec VIP MFA for Centrify Server Suite on Linux Part II articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-20836: Tenant Migration FAQ for joint customers of Centrify and Idaptive