Yes, it's your choice to put in some extra effort to work around this and, if you manage it, we're not going to stop you but! We really can't account for how Steam will react to this. In addition, Steam really wants you to just use SteamGuard. For one, given the letters, it sounds like Steam may use something other than TOTP (HOTP, maybe? That's another popular one) and we only support TOTP in 1Password. Hey, Much though I'd love to say yes (I hate having any 2FA outside of 1PW and SteamGuard bugs me too), I don't think this is something we're likely to do. I'm aware that this is an extremely rare use-case scenario, but can the app be updated to support Steam Guard (or character string based 2FA outputs)? I tried to replicate this with Steam Guard, but:ġ) The 1Password code generator correctly recognizes that the output is 5-characters long.Ģ) It outputs numbers instead of letters. I then took the whole otpauth://totp/BattleNet: secret URL and pasted it in 1Password's One-Time Password field, and received back a functioning, correct code that helps me login to my account. I deactivated my Authenticator from my phone, installed WinAuth on my computer, generated an Authenticator app within it and verified it with Blizzard, then exported the Authenticator app information from WinAuth in plaintext. Today I finally found a workaround for the first. Two main longstanding apps that got in the way of that were the Authenticator from Blizzard, and Steam Guard from Valve. Something I've been trying to do lately is consolidating all my 2FA within the 1Password app.
0 kommentar(er)
