Open wardhanster opened 7 years ago
Hi there, thanks for submitting this issue and for your patience. Usually, these issues are caused by your system time, either on your server or your client, not being in sync. Could you check that both of your systems are correct, to the second, to the official time? One site you can use is https://time.is/.
There should be no issues across timezones – the time is automatically corrected to UTC.
I have the same issue in #102 and my system time matches time.is to a second.
If you have to support Android devices, make sure you're using algorithm: sha1
I should mention my issue in #102 got resolved, maybe you were experiencing the same thing, @wardhanster?
@adrai I am new to 2FA. Can you tell me how to we use sha1 in this?
The default is always sha1 (https://github.com/speakeasyjs/speakeasy#totp). As long as you do not set the algorithm to sha256 or sha512 in combination with Android devices, everything is fine.
my speakeasy code and Google authenticator code are different and anyone tell me why, Please explain to me as easily as possible
First of all thanks for the amazing work you guys have put in. I am using speakeasy on a production project and it appears that google authenticator does not work with this library if "the OTP is generated via google auth app in a different timezone." the library works just fine with
Authy
I have my servers in Atlanta US and I was trying to access it from switzerland and I found about this issue. I am using speakeasy version 2.0.0 A quick response is much appreciated :) and thanks in advance