Two Factor Authentication

Descripción

Acceso seguro en WordPress con este plugin de identificación de dos factores (TFA/2FA). Los usuarios para los que esté habilitado necesitarán un código de un solo uso para acceder. De los autores de UpdraftPlus – el plugin de copia de seguridad/restauración número 1 de WP , con más de dos millones de instalaciones activas.

¿Eres completamente nuevo en TFA? Si es así, consulta nuestras preguntas frecuentes.

Características (consulta las «Capturas de pantalla» para obtener más información):

  • Admite los protocolos estándar TOTP + HOTP (por lo que es compatible con Google Authenticator, Authy y muchos otros).
  • Muestra códigos QR gráficos para escanear fácilmente en aplicaciones en tu teléfono/tableta
  • TFA puede estar disponible por perfil (por ejemplo, disponible para administradores, pero no para suscriptores)
  • Cada usuario puede activar o desactivar TFA
  • TFA can be required for specified user levels, after a defined time period (e.g. require all admins to have TFA, once their accounts are a week old) (Premium version), including forcing them to immediately set up (by redirecting them to the page to do so)
  • Admite la edición de ajustes de portada, a través del shortcode [twofactor_user_settings] (es decir, los usuarios no necesitan acceso al escritorio de WP). (La versión Premium permite el diseño personalizado de cualquier diseño que desees).
  • Los propietarios de sitios pueden permitir «dispositivos de confianza» en los que los códigos TFA solo se pidan durante un número determinado de días (en lugar de cada acceso); p.ej. 30 días (versión Premium)
  • Funciona junto con «Theme My Login» (tanto formularios como widgets)
  • Incluye compatibilidad para los formularios de acceso de WooCommerce y Affiliates-WP
  • Incluye compatibilidad para formularios de acceso de Elementor Pro (versión Premium)
  • Incluye compatibilidad para todos y cada uno de los formularios de acceso de terceros (versión Premium) sin necesidad de codificación adicional al agregar tu código TFA al final de tu contraseña
  • No menciona ni solicita el segundo factor hasta que el usuario haya sido identificado como uno con el TFA activado (es decir, no se muestra nada a los usuarios que no lo tienen activado)
  • Compatible con WP Multisitio (el plugin debe estar activado en la red)
  • Interfaz de usuario simplificada y base de código para facilidad de uso y rendimiento.
  • Se añadieron una serie de controles de seguridad adicionales al código original
  • Códigos de emergencia para cuando pierdas tu teléfono/tableta (versión Premium)
  • Cuando utilizas el shortcode de portada (versión Premium), solicita al usuario que introduzca el código TFA actual correctamente para poder activar TFA
  • Funciona junto con «WP Members» (formulario de código abreviado)
  • Los administradores pueden acceder a los códigos de otros usuarios y activarlos/desactivarlos cuando sea necesario (versión Premium)

¿Por qué usar TFA / 2FA?

¡Lee esto! https://www.wired.com/2012/08/apple-amazon-mat-honan-hacking/

¿Cómo funciona TFA/2FA?

Este plugin utiliza el algoritmo estándar de la industria TFA/2FA TOTP o HOTP para crear contraseñas de un solo uso. Estos son utilizados por Google Authenticator, Authy y muchas otras aplicaciones OTP que puedes implementar en tu teléfono, etc.

Un código TOTP es válido durante un tiempo determinado. Cualquier programa que utilice (es decir, Google Authenticator, etc.) mostrará un código diferente de vez en cuando.

Notas del plugin

Este plugin comenzó a funcionar a principios del 2015 como una bifurcación amigable y una mejora del plugin de «identificación de dos factores» de Oscar Hane.

Capturas

  • Ajustes de todo el sitio

  • Ajustes de usuario (escritorio)

  • Ajustes de usuario (portada, a través de shortcode)

  • formulario de acceso de WP normal que solicita el código OTP (después de introducir correctamente el nombre de usuario/contraseña)

  • formulario de acceso de WooCommerce que solicita el código OTP (después de introducir correctamente el nombre de usuario/contraseña)

  • Lo que ve el usuario si abre un código OTP incorrecto en el formulario de acceso normal de WP

  • Lo que ve el usuario si abre un código OTP incorrecto en el formulario de acceso de WooCommerce

  • Dónde encontrar los ajustes de todo el sitio en el menú del escritorio

  • Dónde encontrar los ajustes personales del usuario en el menú del escritorio

  • Códigos de emergencia (versión Premium)

  • Ajustar los ajustes de otros usuarios como administrador (versión Premium)

  • Crea tu propio diseño para la página con shortcodes personalizados (versión Premium)

Instalación

Este plugin requiere la versión 5.3 de PHP o superior y es compatible con php-openssl o PHP mcrypt. La gran mayoría de las configuraciones de PHP tendrán uno de estos. Si no es así, pregunta a tu empresa de alojamiento.

  1. Busca «Identificación de dos factores» en el menú «Plugins» en WordPress.
  2. Haz clic en el botón «Instalar». (Asegúrate de elegir el correcto)
  3. Activa el plugin en menú ‘Plugins’ de WordPress
  4. Busca los ajustes de todo el sitio en Ajustes > Identificación de dos factores; busca tus propios ajustes de usuario en la entrada del menú de nivel superior «Identificación de dos factores».

Si deseas añadir una sección a la portada de tu sitio donde los usuarios pueden configurar sus ajustes de identificación de dos factores, usa este shortcode: [twofactor_user_settings]

FAQ

¿Qué es la identificación de dos factores (TFA/2FA)?

Básicamente, tiene que ver con proteger tus accesos, de modo que haya más de un eslabón en la cadena que deba romperse antes de que un intruso no deseado pueda ingresar a tu web.

By default, your WordPress accounts are protected by only one thing: your password. If that’s broken, then everything’s wide open.

«Two factor» means adding a second requirement. Usually, this is a code that comes to a device you own (e.g. phone, tablet) – so, someone can’t get into your website without getting hold of your device. You can get a longer answer from Wikipedia.

A veces también se le llama identificación multifactor en lugar de dos factores, porque alguien podría proteger sus sistemas con tantos factores como quisiera.

¿Por qué debería importarme?

Leer esto: https://www.wired.com/2012/08/apple-amazon-mat-honan-hacking/

¿Cómo funciona la identificación de dos factores (TFA/2FA)?

Dado que «identificación de dos factores» simplemente significa «un segundo algo es necesario para entrar», esta respuesta depende de la configuración particular. En el caso más común, se muestra un código numérico en tu teléfono, tableta u otro dispositivo. Este código se enviará a través de un SMS; esto depende del funcionamiento de la red de telefonía móvil. Este plugin no utiliza ese método. En su lugar, utiliza un algoritmo matemático estándar para generar códigos que solo son válidos una vez cada uno, o solo durante 30 segundos (según el algoritmo que elijas). Tu teléfono o tableta puede conocer el código después de haberlo configurado una vez (a menudo, simplemente escaneando un código de barras fuera de la pantalla).

Qué necesito configurar en mi teléfono/tableta (etc.) para generar los códigos?

This depends on your particular make of phone, and your preferences. Google have produced a popular app called «Google Authenticator», which is a preferred option for many people because it is easy to use and can be set up via just scanning a bar code off your screen – follow this link, and ignore the first paragraph that is talking about 2FA on your Google account (rather than being relevant to this plugin).

¿Qué pasa si no tengo un teléfono o tableta?

Many and various devices and programs can generate the codes. One option is an add-on for your web browser; for example, here are some apps and add-ons for Google Chrome. Wikipedia lists various programs for different computers.

Perdí mi dispositivo que tiene códigos de acceso o no funcionan. ¿Qué hacer?

Si tu contraseña solía funcionar, pero ya no lo hace, verifica que la hora en tu dispositivo que la genera sea precisa.

Si no puedes acceder y necesitas desactivar la identificación de dos factores, añade esto a tu archivo wp-config.php, usando FTP o el administrador de archivos en tu panel de control de alojamiento:

define('TWO_FACTOR_DISABLE', true);

Añadir a continuación de cualquier otra línea que comience con «definir».

Alternativamente, si tienes acceso FTP o cPanel a tu espacio de alojamiento web, puedes desactivar el plugin; consulta este artículo.

¿Por qué el plugin no admite el envío del código de dos factores por correo electrónico?

Si alguien tiene acceso a su cuenta de correo electrónico, entonces puedes enviar un código de restablecimiento de contraseña mediante los mecanismos de restablecimiento de contraseña integrados en WordPress. Por lo tanto, si el código de dos factores también se envió allí, la capacidad de leer su correo electrónico permite romper ambos factores y, por lo tanto, ya no es realmente una identificación de dos factores.

Algunos usuarios pueden tener identificación de dos factores en su cuenta de correo electrónico, pero esto no se puede conocer ni controlar desde dentro de WordPress, por lo que dar esta opción a los usuarios significa que el administrador no puede ver o hacer cumplir la identificación de dos factores. E incluso en este caso, el correo electrónico a menudo se envía entre servidores sin cifrar, por lo que es susceptible a ataques de intermediario más allá del control de WordPress.

¿Qué son HOTP y TOTP?

Estos son los nombres de los dos algoritmos matemáticos que se utilizan para crear los códigos especiales. Estos son algoritmos estándar de la industria, ideados por criptógrafos expertos. HOTP es menos popular, pero el dispositivo que genera los códigos no necesita saber la hora correcta (en cambio, los códigos se generan en una secuencia precisa). TOTP es mucho más popular y genera códigos que solo son válidos durante 30 segundos (por lo que su dispositivo necesita saber la hora). Recomendaría TOTP, ya que HOTP puede ser molesto si algo hace que las secuencias no estén sincronizadas.

¿Cuál es el shortcode que se debes usar para los ajuste de la portada?

[twofactor_user_settings]

¡Introduje deliberadamente una contraseña incorrecta y me deja acceder!

Tienes una extensión de administrador de contraseñas instalada en tu navegador web, con la contraseña correcta ingresada. Has reemplazado automáticamente tu contraseña incorrecta con la correcta de tu tienda guardada. Este comportamiento ha sido observado y confirmado por varios usuarios. Puedes verificarlo utilizando las herramientas de desarrollo web en tu navegador para ver los datos HTTP enviados a WordPress y observar qué contraseña está realmente en ellos. También puedes abrir un navegador web nuevo sin dicha extensión para volver a probar.

Ten en cuenta que el plugin de identificación de dos factores no tiene ningún mecanismo para comparar o aprobar contraseñas; esto lo hace el núcleo de WordPress. Si se envía la contraseña incorrecta, WordPress se encargará de ello y el acceso no continuará.

Reseñas

8 de septiembre de 2020
If I had one complaint, it's the use of a top-level menu item for the user settings. Should be on the user page or somewhere else, it doesn't warrant a top-level menu. But it's not worth removing a star for.
3 de abril de 2020
Had an urgent issue - support got in touch immediately and resolved it. Great low impact plugin and great support. Thank you.
29 de febrero de 2020
I rarely leave reviews but this plugin deserves it. I needed the ability to have the 2FA settings all done by the user on the FRONT END and not in the User Profile. This plugin does it and does it really really well. So good, I paid for it! Well done guys.
11 de noviembre de 2019
It helps so much to prevent unauthorized people gaining access. We had bad experience with plain login so far so this is great solution for us.
Leer todas las 64 reseñas

Colaboradores y desarrolladores

«Two Factor Authentication» es un software de código abierto. Las siguientes personas han colaborado con este plugin.

Colaboradores

«Two Factor Authentication» ha sido traducido a 14 idiomas locales. Gracias a los traductores por sus contribuciones.

Traduce «Two Factor Authentication» a tu idioma.

¿Interesado en el desarrollo?

Revisa el código , echa un vistazo al repositorio SVN o suscríbete al registro de desarrollo por RSS.

Registro de cambios

1.9.2 – 20/Mar/2021

  • TWEAK: When checking if a user has TFA enabled on a login page, perform the same sanitisation on the username as WP core, so that if the user mis-types their username (which WP accepts) e.g. by prefixing a space, then they will still be asked for their TFA code (instead of jumping straight to an error for not supplying one)
  • TRANSLATIONS: Added an Italian translation, thanks to Edoardo Di Leginio

1.9.1 – 15/Feb/2021

  • TWEAK: Correct the «for» attribute of the «mark as trusted» text label on the WooCommerce login form

1.9.0 – 09/Feb/2021

  • FEATURE: (Premium) If TFA is required for a user, and they have not yet set it up, then force them to be redirected to a configured URL
  • TWEAK: Replace the deprecated jQuery.click() and .change() methods

1.8.8 – 16/Jan/2021

  • TWEAK: Replace the deprecated jQuery.unbind() and .focus() methods
  • TWEAK: If the free version is active, then throw an error if trying to activate the Premium version, explaining what needs to be done

1.8.7 – 11/Jan/2021

  • TWEAK: Update jQuery document ready, click and submit styles to one not deprecated in jQuery 3.0, and replace :first pseudo-selector with .first()
  • TWEAK: Now marked as supporting PHP 5.6+ (now that PHP 8.0 is out)
  • TWEAK: Update to the latest version of the bundled updater library (paid versions), which adds integration with WP 5.5+’s auto-updater

1.8.6 – 15/Sep/2020

  • FEATURE: Add a ‘TFA’ column also to the Users screen in the WP network admin dashboard (multisite installs)
  • TWEAK: Update the bundled updater library (paid versions) to the current release

1.8.5 – 29/Aug/2020

  • TWEAK: Fix the «for» attribute of the «trusted» text label on the WooCommerce login form
  • TWEAK: If a website’s wp-login.php is available under multiple hosts without CORS enabled between them, then AJAX calls would fail; this is now resolved by using a relative URL instead
  • TWEAK: Update bundled updater libraries on Premium version (improving compatibility with WP 5.5+’s update settings)

1.8.4 – 26/May/2020

  • TWEAK: Updare .pot file; now both the first two parameters to _n() are also included in the aggregation process

1.8.2 – 23/May/2020

  • FIX: If the site owner was requiring a correct code to be supplied for activation, then this was also being required for de-activation
  • TWEAK: Introduce simbatfa_enforce_require_after_check filter, allowing developers to selectively disable the «require TFA after X days» check
  • TWEAK: Update .pot file

1.8.0 – 18/Apr/2020

  • FEATURE: Add support in the paid version for Elementor login forms
  • TWEAK: Updater in paid version now will make checks on availability without needing login
  • TWEAK: Update updater class to current release

1.7.4 – 19/Mar/2020

  • TWEAK: Adjust how the trusted field is referenced from JavaScript, fixing IE11 compatibility
  • TWEAK: Introduce the filter simba_tfa_required_for_user

1.7.3 – 03/Mar/2020

  • TWEAK: Provide non-plural alternative for trusted device phrase
  • TWEAK: Mark as supporting WP 5.4

1.7.2 – 13/Feb/2020

  • TWEAK: Update message about what to do with translations

1.7.1 – 14/Jan/2020

  • FIX: Missing file in 1.7.0 (free) release

1.7.0 – 14/Jan/2020

  • FEATURE: (Premium version): Add an optional TFA section to the WooCommerce account details section in «My Account»
  • TWEAK: Fix div tag balancing issue in settings output
  • TWEAK: Update WooCommerce integration to adjust to DOM changes in WooCommerce 3.8
  • TWEAK: Update .pot file

1.6.4 – 12/Nov/2019

  • TWEAK: On wp-login.php on WordPress 5.3, the password field was not hiding when the TFA field opened
  • TWEAK: Update .pot file
  • TWEAK: Add data-lpignore attribute to TFA field to indicate to LastPass that it is not a password field

1.6.3 – 18/Oct/2019

  • FIX: The ‘trusted users’ option display in the settings defaulted to showing as enabled, whereas in fact the default setting is disabled
  • TWEAK: Mark as compatible with WP 5.3

1.6.2 – 11/Sep/2019

  • FIX: On multisites, administration of site users who were not present on the main site was not possible
  • TWEAK: Introduce the WP action simba_tfa_activation_status_saved to allow developers to respond to activation status changes
  • TWEAK: Update updater class to 1.8 series

1.6.1 – 10/Aug/2019

  • TWEAK: Response to an attempt to turn TFA on can now include an «error» attribute if the attempt failed due to failure to supply the current code

1.6.0 – 08/Aug/2019

  • FEATURE: (Premium version) By using the parameter style=»require_current» with the shortcode twofactor_user_settings_enabled, the user will only be able to activate TFA if they enter the current TFA code
  • TWEAK: Remove the incorrect suffix «(Premium)» (double-suffix in the actual Premium version) that appeared in the plugin title in 1.5.6

1.5.6 – 06/Aug/2019

  • TWEAK: Allow customisation of a particular message via a filter simbatfa_message_you_should_verify
  • TWEAK: Replace «eachother» with «each other»

1.5.5 – 30/Jul/2019

  • TWEAK: Force a global context when creating the initial Simba_Two_Factor_Authentication object, to work around direct accesses from components that do not set the scope correctly

1.5.4 – 17/Jul/2019

  • FEATURE: (Premium version) – allow the site administrator to forbid users who have compulsory TFA to turn it off (supplementing the additional capability to prevent them logging in)

1.5.3 – 22/Jun/2019

  • TWEAK: When using your final emergency code (Premium version), and viewing your settings (which regenerated new ones), then if you did not follow the advice to reset your prviate key, you would get the same codes as before. This might be thought undesirable (though is not a security flaw, as the emergency codes are no more guessable the second time around than the first). This behaviour has now been changed.

1.5.2 – 08/Jun/2019

  • TWEAK: When php-mcrypt was not installed, pressing the «Reset private key» link in a user’s settings would cause an unnecessary PHP notice, and display a wrong «current code» for a few seconds.

1.5.1 – 05/May/2019

  • FEATURE: Support any login form (Premium version) via appending the TFA code onto the end of the password. This allows support even of login forms coded in a way that make integrations (that aren’t hacks or inordinate amounts of work-around code) impossible (e.g. PeepSo)
  • TWEAK: Minor wording tweak in the explanation of how TOTP works.

1.4.12 – 18/Apr/2019

  • TWEAK: Add a filter simba_tfa_localisation_strings allowing further customisation of front-end strings
  • TWEAK: Add an extra instructional message in the «Make two factor authentication compulsory» section (Premium) to explain how to cope with existing users
  • TWEAK: Cope with the user entering spaces in their two-factor code (TOTP protocol codes are numbers only, but some apps apparently display formatting and users are not aware)
  • TWEAK: Mark as supporting WP 5.2

1.4.11 – 08/Mar/2019

  • FIX: On multisites, the user search should search on all sites, not just the main one

1.4.10 – 01/Mar/2019

  • TWEAK: Introduce a filter, simba_tfa_management_capability, allowing the WP capability (default: manage_options) required by a user to manage the plugin to be changed. (Be careful – giving the ability to manage could potentially mean the ability to lock any user out).

1.4.9 – 20/Feb/2019

  • SECURITY: The security fix in version 1.4.7 was faulty and failed to completely fix the problem; it is now resolved in this release. Our apologies for the double update.

1.4.8 – 16/Feb/2019

  • FIX: On some multisite setups, the link to the site-wide administration settings went to the wrong place

1.4.7 – 06/Feb/2019

  • SECURITY: If a user’s WordPress account username was in the form of an email address, and if their actual account email address was something different, and TFA was set up on that account, and used the «username» (that looked like an email address) to login, then TFA controls upon login on that account would be ineffective. Other accounts were not affected (regardless of whether you login by email or not). This vulnerability was inherited from the original «Two Factor Auth» plugin that this plugin was forked from, and so is present in all versions before this one.

1.4.6 – 05/Feb/2019

  • FIX: When displaying a user’s trusted devices in the admin page, the time that a device was trusted until was not shown correctly (instead, it showed the current time)
  • FIX: Removing the first trusted device in a list did not always work
  • TWEAK: Display «(none)» when there are no trusted devices

1.4.4 – 04/Feb/2019

  • FEATURE: Trusted devices are now listed in the user’s admin page, allowing them to see and remove trust from their devices.
  • TWEAK: Updated .pot file

1.4.3 – 28/Jan/2019

  • FIX: The «Trusted devices» functionality (Premium) checkbox was not appearing when activated
  • TWEAK: Add a missing translation domain to a phrase

1.4.1 – 25/Jan/2019

  • FEATURE: Trusted devices: A site owner can now choose to allow particular user levels (e.g. admins, editors) to mark devices as ‘trusted’ and thereby exempt from needing to enter a TFA code for a chosen number of days. This feature is off by default and requires https (i.e. SSL) on the login form and cookies to be kept in the trusted device.
  • FIX: Fix a regression in 1.4.0 whereby when a site owner viewed another user’s current code, it could later self-update with the wrong user’s value
  • TWEAK: Add the robustness in parsing broken JSON present on the standard WP login form to other login forms
  • TWEAK: Various internal code documentation improvements
  • TWEAK: Suppress mcrypt deprecation notices in places where we would use an alternative if it was not present
  • TWEAK: Bumped the support requirement up to WP 3.4. I’m not aware of anything done to break it on 3.3, but this is the official requirement (it’s very hard to test old WP versions as they don’t run on modern webserver stacks)

1.4.0 – 24/Jan/2019

  • FEATURE: Where the current OTP code is displayed (during setup), this will now self-update automatically (i.e. without needing a manual press on the «update» link).
  • TWEAK: Various improvements to the layout and text of the setup page to help make the process more understandable
  • TWEAK: The current code is shown next to the UI option for enabling TFA
  • TWEAK: Prevent a PHP notice if AUTH_KEY was not defined (on some very old WP installs)

1.3.13 – 18/Dec/2018

  • SECURITY: Fix a logged-in CSRF vulnerability reported by Martijn Korse (www.bitnesswise.com). Due to a missing nonce check, if an attacker was able to persuade a personally-targetted victim who was currently logged in to their WordPress account to visit a personally-crafted (for the individual victim) page in the same browser session, then the attacker would be able to de-activate two-factor authentication for the victim on that WordPress site (thus leaving the targetted account protected by the user’s password, but not by a second factor – the absence of a request for a TFA code would be apparent on the user’s next login). This vulnerability was inherited from the original «Two Factor Auth» plugin that this plugin was forked from, and so is present in all versions before this one.
  • TWEAK: Some minor code-tidying
  • TWEAK: Update bundled Premium updater library to current version (1.5.10)

1.3.12 – 14/Dec/2018

  • TWEAK: Prevent a PHP debugging notice when $pagenow is not set

1.3.11 – 04/Dec/2018

  • FEATURE: Add a ‘TFA’ column on the Users screen in the WP admin dashboard to display TFA status, thanks to Enrico Sorcinelli.

1.3.10 – 30/Nov/2018

  • FIX: TFA codes were not being requested on the login form on a WooCommerce dedicated order payment page (i.e. /checkout/order-pay/123456/?pay_for_order=true&key=wc_order_blahblahblah) (meaning that if a user had TFA activated, login would fail).
  • TWEAK: Prevent a PHP notice if AUTH_SALT was not defined (on some very old WP installs)

1.3.9 – 30/Oct/2018

  • SECURITY: If you were not using the recommended option of requiring 2FA for XMLRPC requests, then an attacker could potentially also bypass requirements for 2FA on ordinary logins (i.e. only need the password). Such users will want to immediately update, though we recommend that all users do. This vulnerability was inherited from the original «Two Factor Auth» plugin that this plugin was forked from, and so is present in all versions before this one.

1.3.8 – 25/Oct/2018

  • TWEAK: Update the updater class in the Premium version to the current release (1.5.6)

1.3.7 – 15/Oct/2018

  • TWEAK: Try to mitigate plugins on the login page which cause JavaScript exceptions by enqueing our scripts earlier.

1.3.6 – 04/Oct/2018

  • TWEAK: Add attribute autocomplete=»off» on the WooCommerce login form TFA field (was already present for regular WP login form)
  • TRANSLATION: Added Portuguese (Brazilian) translation, courtesy of Dino Marchiori

1.3.5 – 02/Oct/2018

  • TWEAK: Some code-styling consistency clean-ups
  • TWEAK: Allow one more window’s tolerance by default for codes from devices running fast

1.3.4 – 11/Sep/2018

  • FIX: Sometimes a TML widget login form could fail to work because of a changed/unexpected DOM tree
  • FIX: Some further breakage in TML had occurred, causing login buttons to require to be pressed twice

1.3.3 – 31/Jul/2018

  • FIX: Restore support for «Theme My Login», which had been broken by unannounced changes in TML 7.x
  • TRANSLATIONS: Update .pot file

1.3.2 – 31/May/2018

  • TWEAK: Add the simbatfa_check_tfa_requirements_ajax_response and simbatfa_verify_code_and_user_result filters to allow over-riding of the response to the «TFA required?» question and the TFA check itself by developers

1.3.1 – 25/May/2018

  • FIX: The WooCommerce 3.3+ login form was requiring two clicks on the ‘Log In’ button
  • TWEAK: The progress spinner had disappeared on WooCommerce 3.3+

1.3.0 – 05/Apr/2018

  • FEATURE: (Premium version) Integration with the WP-Members login form, https://wordpress.org/plugins/wp-members/ . N.B. WP-Members does not pass on the real error message upon a login failure, but displays its own hard-coded message that the username/password were wrong; so you’ll see this even if it was really the TFA code that was wrong.
  • TWEAK: Change the permission check for editing other users (Premium version) to edit_users (instead of the previous update_plugins, intended just as a proxy for «is an admin»)
  • TWEAK: Stop using the deprecated jQuery.parseJSON method
  • TWEAK: Change a string that was not in a translatable form
  • TWEAK: Update the updater class in the Premium version to the current release (1.5.1)

1.2.35 – 28/Nov/2017

  • TWEAK: Upon front-end settings save, do jQuery(document).trigger(‘tfa_settings_saved’), allowing the user to respond to the action (e.g. reload page)
  • TWEAK: Suppress mcrypt deprecation notices on PHP 7.1 (we already know it is deprecated, and already use openssl if it is not installed)

1.2.34 – 08/Nov/2017

  • TWEAK: Remove calls to the deprecated screen_icon() function
  • TWEAK: Remove some unnecessary bundled translation files
  • TWEAK: Add some translation files not previously included in the Premium version
  • TWEAK: Update bundled Premium updater library to current (1.5.0)

1.2.33 – 09/Oct/2017

  • FIX: The available/required settings for super-admins on multisite installs were not saving (Premium feature)
  • FIX: When the admin fetched another user’s current QR code, it embedded the wrong username (which was a cosmetic issue only – the code itself was correct) (Premium feature)

1.2.32 – 06/Oct/2017

  • TWEAK: Update bundled updater in Premium to latest version (1.4.8)

1.2.31 – 05/Oct/2017

  • FEATURE: (Relevant to Premium version): Automatically generate new emergency codes when they run out, including upon view of settings if there are none (e.g. on upgrade from free to Premium)
  • TWEAK: Code-styling consistency tweaks

1.2.30 – 18/Sep/2017

  • FIX: TML shortcode forms were not working properly for non-TFA users

1.2.29 – 16/Sep/2017

  • FIX: Prevent double-show of TFA field on TML default login page (regression)
  • FIX: Restore functionality on TML shortcode forms (regression, likely due to changes in TML)
  • TWEAK: Restore the spinner to proper size on all forms
  • TWEAK: A few very minor code style clean-ups

1.2.27 – 29/Aug/2017

  • TWEAK: Add the new ‘PHP Requires’ header to readme.txt
  • TWEAK: Correct a couple of wrong translation domain references

1.2.26 – 08/Aug/2017

  • FIX: Do not request TFA code on TML reset password form (regression, likely due to changes in TML)
  • APOLOGIES: 1.2.25 was a faulty release that would block logins. You should immediately update.

1.2.24 – 05/Aug/2017

  • TWEAK: Update to the latest version of the updater library (Premium)

1.2.23 – 15/Jun/2017

  • TWEAK: Allow admins to reset users’ private keys (Premium)

1.2.22 – 23/May/2017

  • TWEAK: Update updater library to current version (Premium)
  • TWEAK: Use higher-quality spinner image
  • COMPATIBILITY: Mark as compatible with WP 4.8

1.2.21 – 22/Feb/2017

  • TWEAK: Update jquery-qrcode library to latest release (0.14.0)
  • TWEAK: Explicitly encode spaces in WordPress usernames (apparently resolves a problem with a particular iPhone app)

1.2.20 – 17/Feb/2017

  • TWEAK: Work around a bug seen with strlen() on one particular PHP install
  • FIX: The line purporting to show the current UTC time was in fact taking your WordPress timezone into account. It has now been adjusted to show both to avoid ambiguity.
  • FIX: 1.2.18 used a PHP 5.4+ only function, whereas we support PHP 5.3+

1.2.17 – 09/Feb/2017

  • FIX: Fix support for login widgets from Theme My Login

1.2.16 – 30/Jan/2016

  • FIX: Fix issue whereby if you were already logged in and managed to visit a login form, you would not be asked for a TFA code

1.2.15 – 23/Jan/2017

  • FEATURE: Add support for login widgets from Theme My Login
  • UPDATER: (Premium version): update to the latest updater class, including the new ability to automatically update

1.2.14 – 02/Jan/2017

  • TWEAK: Add missing internationalisation headers to the main plugin file

1.2.13 – 31/Aug/2016

  • TWEAK: Internationalisation implementation was not previously compatible with wordpress.org’s translation system

1.2.12 – 20/May/2016

  • FEATURE: Compatibility with https://wordpress.org/plugins/use-administrator-password/ – when TFA is enabled on an account, the TFA credentials of the user whose password was supplied are allowed (and required)

1.2.11 – 18/May/2016

  • TWEAK: Update bundled select2 to version 4.0.2
  • FIX: If the [twofactor_user_qrcode] shortcode (Premium version) was used without other short-codes, then the code would not display

1.2.10 – 31/Mar/2016

  • TWEAK: Prefer openssl, if present, to the deprecated mcrypt. Note that if you migrate a site from a server without openssl to a server without mcrypt, then because of mcrypt’s non-compliant padding, you will need to either install php-mcrypt on the new server, or disable TFA (via define(‘TWO_FACTOR_DISABLE’, true); in your wp-config.php) to allow users to be able to log in. This also applies if the source site did have openssl, but for users who hadn’t logged in since installing this update.
  • TWEAK: Make the $simba_two_factor_authentication_premium object globally available
  • COMPATIBILITY: Mark as tested on WP 4.5

1.2.8 – 12/Dec/2015

  • FEATURE: Add support for the Affiliates-WP login form
  • TWEAK: Defeat WooCommerce loading an old version of the select2 script onto the TFA settings page, and breaking the user selector (should work this time)

1.2.6 – 11/Nov/2015

  • TWEAK: Defeat WooCommerce loading an old version of the select2 script onto the TFA settings page, and breaking the user selector
  • TWEAK: Tested on WordPress 4.4
  • TWEAK: Use h1 for heading style on admin page, not h2
  • FIX: The «You’ll need to use TFA to login in future» link for users for whom TFA is compulsory (Premium) was to the wrong page

1.2.4 – 09/Nov/2015

  • TWEAK: Make window settings filterable

1.2.3 – 19/Oct/2015

  • FIX: Fix bug in 1.2.2 that could lock out users without TFA settings

1.2.2 – 16/Oct/2015

  • TWEAK: Display dashboard notice if TWO_FACTOR_DISABLE is defined in wp-config.php, to prevent time wasted wondering why nothing is happening

1.2.1 – 08/Oct/2015

  • FEATURE: (Premium version) – Require users (of configured roles) to use TFA (optionally after a configurable amount of time)

1.1.21 – 25/Aug/2015

  • TRANSLATIONS: Translation files can now be used (translators welcome!)
  • TRANSLATION: Swedish translation added, courtesy of Bo Sving

1.1.19 – 20/Aug/2015

  • TWEAK: Remove a pointless nonce check

1.1.18 – 01/Aug/2015

  • COMPATIBILITY: Tested with WP 4.3 (RC1) and WooCommerce 2.4 (RC1) – no issues found (i.e. previous releases believed to be already compatible)
  • FIX: When the admin is showing codes for other users, QR codes were not displaying correctly since 1.1.13

1.1.17 – 22/May/2015

  • TWEAK: Introduce convenience method for developers wanting to verify that TFA is active (Premium)
  • FIX: Fix operation of [twofactor_conditional] shortcode (Premium)
  • FIX: Fix fatal error introduced in convenience method in 1.1.16

1.1.15 – 13/May/2015

  • FIX: Fix conflict with ‘reset password’ form with «Theme My Login» plugin

1.1.14 – 12/May/2015

  • FIX: Add TFA support to the WooCommerce login-on-checkout form (previously, TFA-enabled users could not log in using it)

1.1.13 – 11/May/2015

  • TWEAK: Use jquery-qrcode to generate QR codes, replacing external dependency on Google
  • TWEAK: Update bundled select2 library to 4.0.0 release (was rc2)

1.1.12 – 22/Apr/2015

  • FIX: Fix corner-case where the user’s login looked like an email address, but wasn’t the account address. In this case, a OTP password was always requested.
  • FIX: When the username does not exist, front-end should not request TFA code.

1.1.11 – 21/Apr/2015

  • TWEAK: Prevent PHP notice if combining with bbPress
  • TWEAK: Added more console logging if TFA AJAX request fails
  • TWEAK: Add some measures to overcome extraneous PHP output breaking the AJAX conversation (e.g. when using strict debugging)

1.1.10 – 20/Apr/2015

  • SECURITY: Fix possible non-persistent XSS issue in admin area (https://blog.sucuri.net/2015/04/security-advisory-xss-vulnerability-affecting-multiple-wordpress-plugins.html)
  • FIX: Don’t get involved on «lost password» forms (intermittent issue with «Theme My Login»)

1.1.9 – 15/Apr/2015

  • TESTING: Tested with «Theme My Login» – https://wordpress.org/plugins/theme-my-login/ – no issues
  • TWEAK: Do a little bit of status logging to the browser’s developer console on login forms, to help debugging any issues
  • TWEAK: Add a spinner on login forms whilst TFA status is being checked (WP 3.8+)
  • TWEAK: Make sure that scripts are versionned, to prevent updates not being immediately effective
  • TWEAK: Make sure OTP field on WooCommerce login form receives focus automatically

1.1.8 – 14/Apr/2015

  • FIX: Fix an issue on sites that forced SSL access to admin area, but not to front-end, whereby AJAX functions could fail (e.g. showing latest code)
  • FIX: Version number was not shown correctly in admin screen since 1.1.5
  • TWEAK: Show proper plugin URI

1.1.7 – 10/Apr/2015

  • FIX: Fix plugin compatibility with PHP 5.6
  • FIX: TFA was always made active on XMLRPC, even when the user turned it off

1.1.6 – 09/Apr/2015

  • TWEAK: Change various wordings to make things clearer for new-comers to two-factor authentication.

1.1.5 – 07/Apr/2015

  • FEATURE: Admin users (Premium version) can show codes belonging to other users, and activate or de-activate TFA for other users.
  • PREMIUM: Premium version has now been released: https://www.simbahosting.co.uk/s3/product/two-factor-authentication/. Features emergency codes, personal support, and more short-codes allowing you to custom-design your own front-end page for users.
  • TWEAK: Premium version now contains support link to the proper place (not to wordpress.org’s free forum)
  • TWEAK: Added a constant, TWO_FACTOR_DISABLE. Define this in your wp-config.php to disable all TFA requirements.
  • FIX: Fix a bug introduced in version 1.1.2 that could prevent logins on SSL-enabled sites on the WooCommerce form when not accessed over SSL

1.1.3 – 04/Apr/2015

  • TWEAK: Provide «Settings saved» notice when user’s settings are saved in the admin area (otherwise the user may be wondering).

1.1.2 – 03/Apr/2015

  • FIX: Include blockUI JavaScript (the lack of which caused front-end options not to save if you did not have WooCommerce or another plugin that already used blockUI installed)
  • FEATURE: Don’t show anything on the WooCommerce login form unless user is using 2FA (i.e. behave like WP login form)
  • FEATURE: Added 9 new shortcodes for custom-designed front-end screens (Premium – forthcoming)

1.1.1 – 30/Mar/2015

  • Support added for multisite installs. (Plugin should be network-activated).
  • Support added for super-admin role (it’s not a normal WP role internally, so needs custom handling)
  • Tested + compatible on upcoming WP 4.2 (tested on Beta 3)
  • Re-add option to require 2FA over XMLRPC (without specific code, XMLRPC clients don’t/can’t use 2FA – but requiring it effectively blocks hackers who want to crack your password by using this weakness in XMLRPC)

1.0 – 20/Mar/2015

  • First version, forked from Oskar Hane’s https://wordpress.org/plugins/two-factor-auth/
  • Support for email «two-factor» removed (email isn’t really a second factor, unless you have multiple email accounts and guard where your «lost login» emails go to)
  • WooCommerce support added to the main plugin. Load WooCommerce JavaScript only on pages where it is needed.
  • Use AJAX to refresh current code (rather than reloading the whole page)
  • Added WordPress nonces and user permission checks in relevant places
  • Shortcode twofactor_user_settings added, for front-end settings
  • User interface simplified/de-cluttered