Hacker News Reader

Comment by omneity | Hacker News Reader

This is simply not true. Just today an app asked me to use Microsoft Authenticator, and scanning the QR code with Google Auth and Authy didn’t work, earning me an “Invalid QR code” error and forcing me to install the app from MS.

View on HN

I don't think there's a formal spec for the otpauth URI yet [0], even if there is a spec by Google [1], so this may just come down to MS adding some incompatibility to force usage of their authenticator, or the app using some proprietary authentication scheme that is not otpauth.

There's nothing complicated about otpauth provisioning URIs i.e. what's encoded into the QR code.

[0]: https://shkspr.mobi/blog/2022/05/why-is-there-no-formal-spec...

[1]: https://github.com/google/google-authenticator/wiki/Key-Uri-...

You assume that because you were not able to overcome whatever error/s you encountered with Google Auth and Authy, that you were being forced to use MS Authenticator.

Pretty uncharitable interpretation on your end. I am a developer and went to the extent of verifying the content of the QR code and the optional URL for manually adding it. No OTP code in there.

Try to be nicer next time.

I truly did not mean to come off as rude. The 'content of the QR code' would've revealed the actual seed and so would corroborate your assumption if you did, in fact, verify as much. I merey stated a troubleshooting fact. No offense intended.

My bad for misunderstanding the tone of your comment. I likely wouldn't have gone off in this direction if you asked me what measures I took to check the OTP code in a collaborative/constructive way rather than expressing doubt they way you did. Either way, all good.

Reply on news.ycombinator.com