We are setting up a new MFA VPN in our organization, and many people in the company already use Google Authenticator, so we'd like them to be able to use that. However, authenticator reports that the data in the QR code is invalid. (It accepts the code if you manually type it in, so this isn't an interval or clock issue.) The secret encoded in the QR code I'm scanning ends with a bunch of === and it appears that Google Authenticator doesn't like %3D in that string. I've been told that this is a new problem that was introduced in the 3.2.0 update last month, but I don't have independent confirmation of that.
Is Sophos working with Google to iron this out? Is there a way to change the lengths of our secrets so they fit more neatly in base64 and don't end up with === at the end? We're pretty much committed to going with this Sophos appliance now, so I'm hoping there's a resolution on the near horizon...
Also, I'm brand new here, so if there's a better place to ask a question like this, advice on that would be appreciated.
This thread was automatically locked due to age.
