Open KBITSERVICES opened 3 years ago
Not all authenticators support all variations of periods, digits, algorithms and number of secret bits. So I'd start with testing the most common combination: 30 second periods, 6 digits, sha1, 80 bits. I see you're using 60 second periods so I bet that's the problem.
Just to add to this as I've come across a similar issue. I've had to push the algorithm being used down to SHA1 for the most broad compatibility, as to date, the Microsoft authenticator app still won't work with SHA256 or SHA512.
Using a 6 digit code and 30s period.
Hi,
i'm using the following code to generate QRCode for TOTP:
My Problem is that if i scan the Code with Microsoft Authenticator i get an other code as Google Authenticator.
Googles Code is correct, microsoft's isnt.
Can you help please?