You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following a feature request on Facebook, it could be a good idea to check for the cookie before asking for TOTP.
The TOTP check is hooked on wp_authenticate_user (through wp_authenticate_username_password ) which has priority 20, while wp_authenticate_cookie, on the same hook, has priority 30. This means that an error is returned because of the TOTP before the cookie is check.
An easy solution would be to manually check for wp_authenticate_cookie within our auth function.
The text was updated successfully, but these errors were encountered:
I don't know the details of how Google does it for their logins beyond that they do set long lived cookie in browser when 2FA is successful. That then eliminates the need to enter the 2FA code for a long time. I'm assuming that's built into their API, but I can't really find and developer documentation on it. https://support.google.com/accounts/answer/2544838?hl=en
In the process of releasing version 1.2 I'm checking this issue but can't really figure out what the problem is. The cookie verification does work even with the plugin enabled. All of the sites I use it on have me logged-in for a month.
I re-read my own comment though and it looks like I dug something up but can't figure out what I was thinking! Is there really a problem here?
Following a feature request on Facebook, it could be a good idea to check for the cookie before asking for TOTP.
The TOTP check is hooked on
wp_authenticate_user
(throughwp_authenticate_username_password
) which has priority20
, whilewp_authenticate_cookie
, on the same hook, has priority30
. This means that an error is returned because of the TOTP before the cookie is check.An easy solution would be to manually check for
wp_authenticate_cookie
within our auth function.The text was updated successfully, but these errors were encountered: