-
-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client and Server generating different TOTP #649
Comments
@rahul-gharat I have the same problem =/ |
I'm also seeing this in one of my services that uses this package |
Hi, As a workaround I used browserify to compile otplib node module and used it at client side. Now it is working fine. |
Do you have any clue to what version the issue might be on, or what version I should use if I follow the steps you mentioned above |
I am using [email protected] from npm |
I'm too. |
TOTP generated at client and server for the same secret at the same time is different.
(OTP not getting validated).
I tried to play with step and window parameters but didnt worked.
Client Machine has IST timezone and the server has UTC.
I tried to check epoc time at both machines, it is same. (UTC Timestamp is same)
Can someone please help me with this? maybe i am missing something.
Thanks in advance
The text was updated successfully, but these errors were encountered: