Title: Incompatible with 2FA? (Google Authenticator)
Last modified: August 22, 2016

---

# Incompatible with 2FA? (Google Authenticator)

 *  [benroberts](https://wordpress.org/support/users/benroberts/)
 * (@benroberts)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/incompatible-with-2fa-google-authenticator/)
 * This plugin works well but doesn’t seem to be compatible with other 2-factor 
   auth plugins (I’ve tried a couple of different 2FA plugins). Behaviour is that
   a the login dialog is updated with the additional fields, but a login is accepted
   even if the second factor is left blank or deliberately filled in correctly. 
   Is it possible that this plugin could be improved to co-exist with additional
   login security?
 * [https://wordpress.org/plugins/wpdirauth/](https://wordpress.org/plugins/wpdirauth/)

Viewing 1 replies (of 1 total)

 *  [GenealogyCoach](https://wordpress.org/support/users/samatva/)
 * (@samatva)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/incompatible-with-2fa-google-authenticator/#post-5656979)
 * The two-factor auth would need to be supported by the LDAP server, no? Otherwise,
   wouldn’t a second password be needed?

Viewing 1 replies (of 1 total)

The topic ‘Incompatible with 2FA? (Google Authenticator)’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/wpdirauth.svg)
 * [wpDirAuth](https://wordpress.org/plugins/wpdirauth/)
 * [Support Threads](https://wordpress.org/support/plugin/wpdirauth/)
 * [Active Topics](https://wordpress.org/support/plugin/wpdirauth/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wpdirauth/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wpdirauth/reviews/)

## Tags

 * [2fa](https://wordpress.org/support/topic-tag/2fa/)

 * 1 reply
 * 2 participants
 * Last reply from: [GenealogyCoach](https://wordpress.org/support/users/samatva/)
 * Last activity: [11 years, 1 month ago](https://wordpress.org/support/topic/incompatible-with-2fa-google-authenticator/#post-5656979)
 * Status: not resolved