at my work they’ve announced the autentification via sms will not be supported any more (Microsoft). I will be using the FP6 eOs (still need to take the step to transfer from my FP3 - delaying it a bit) and would like not to use Google or Microsoft or other Big Tech privacy unfriendly ON the telephone, only via browser, when needed. Can anyone advise me on an alternative authenticator-app that will work on e-Os? (Proton is only Android, iOs & linux, they state on their website)
On Fairphone 6 with /e/OS since about one year, I highly recommend Proton Pass which can do much more than generate TOTP numbers. It can actually also save Passkeys which is a life saver on a de-googled phone.
Well, all in all it depends what exactly your IT is going to roll out. Before my company changed again we used the Authenticator but not for one time passwords (OTP) but for push messages which popped up in the app stating which application wants access and from which location (based on IP address) this request came. Then you had to confirm that and pick the right number that was shown on the computer, too. While that might (or might not) be super safe we didn’t find ways how to handle this with alternative apps. Even more, back then this exact feature didn’t even work with the Authenticator on my FP2 with LineageOS, I had to go back to FPOS which didn’t get any updates anymore at that point in time. In a modern /e/OS that integration may be better, though.
So if it’s OTP then pick any of the named options, but there are chances that it might be something proprietary as well.
I’m also looking for a privacy-friendly authenticator that works well on /e/OS. A browser-based option would be ideal if the work setup allows it, since I’d rather avoid adding Google or Microsoft services to the phone.
I have been using it Aegis for a long time.
However I could not use Aegis for microsoft 365 authentication. Maybe you can also have a look at Proton Authenticator.
Microsoft (for work accounts) has two options for TOTP setup:
phonefactor: Key is sent directly to the respective Microsoft app. The setup step also requires Google services, which is unfortunate. Internally, it is standard TOTP though, and with root you can extract the secret to reuse it in other apps.
otpauth: Standard TOTP QR code is shown during setup. This is only available when the admin has enabled it, it is quite common that employers have it disabled.
So, if you never get the QR option during setup, bug your IT about it. In a smaller company you might get lucky.
I use self-hosted vaultwarden for getting all my 2FA codes and passkeys synced across devices, but can also recommend Ente Auth.