Frequent issues with MFA - Invalid verification code about google-authenticator-libpam HOT 6 CLOSED

the time should be synchronised

Did you confirm it? ntpdate -q pool.ntp.org?

It really sounds like either your computer or the app(?) you're using has the wrong time set.

What is generating the code on the client side?

from google-authenticator-libpam.

The delay isn't too great:
[root@cms slee]# ntpdate -q pool.ntp.org
server 139.180.160.82, stratum 2, offset -0.025777, delay 0.04787
server 67.219.100.202, stratum 2, offset -0.026687, delay 0.05949
server 162.159.200.123, stratum 3, offset -0.025012, delay 0.03571
server 103.76.40.123, stratum 3, offset -0.025579, delay 0.04906
1 May 09:54:55 ntpdate[177428]: adjust time server 139.180.160.82 offset -0.025777 sec

Issues is happening with Devolution Remote Desktop Manager, Putty, WinSCP and Linux SSH. It seems to be less problematic with Linux SSH though.

I get different error codes such

• Did not receive verification code from user
• Invalid verification code
• Too many concurrent login attempts. Please try again.

from google-authenticator-libpam.

The time set on the phone may be wrong too. You never said what is generating the code on the client side.

from google-authenticator-libpam.

Problem occurs with MFA code obtained on the Google authenticator app on the phone, Devolution Remote Desktop Manager and application on Desktop.

from google-authenticator-libpam.

Issue is related to the time discrepancy between the laptop and time server. Devolution RDM and desktop application are using the same time, and MFA codes are the same. MFA code obtained from terminal server and phone works with issues.

I'll need to sync my laptop with an NTP server. Thanks for the guidance.

from google-authenticator-libpam.

Heh. Thanks for the followup.

You're not the first to have it be due to time not being set correct: https://twitter.com/thomashabets/status/1133780752582217728

from google-authenticator-libpam.