-
-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WinAuth can no longer be used as an option to import the Blizzard Authenticator #962
Comments
This is still an issue. Blizzard Authenticator is going away soon and all 2FA is being disabled. The Battle.net app must be used. |
I see. Good to know, since I'm using SMS 2FA right now. Thanks for the heads up 👍 |
I'm not too familiar with the Battle.net system. With the discontinuation of the Battle.net Authenticator, does this mean that the 8-digit codes are going away, or is that still an option? |
AFAIK (and don't quote me on this), no, it's not going away. The 8-digit code is still a thing, it's just that you have to use the "Battle.net" mobile app. It seems that they're simply consolidating the two apps, that's all. Hopefully the SMS 2FA will continue to work, because I don't plan on using their stupid app. |
Describe the bug
See title
To Reproduce
The provided steps to import the Blizzard Authenticator, as described under the "Option 2 (Windows only)" section, which I have submitted originally myself, no longer work. Blizzard changed their authenticator so that now it is part of their "Battle.net" mobile app. Apparently this messes up WinAuth's ability to import the necessary data.
I've written a new set of steps in an attempt to adjust to these new changes, but was hit with an error message. Here are the steps to recreate the error message:
Note: This will log out all devices that are currently logged-in to your "Battle.net" account.
Expected behavior
I expect not to get an error message.
App Version
1.22.0
Additional context
I know that the problem is with the WinAuth app. I just wanted to inform you about it, since, for many user who are not comfortable with python (including myself) this was the only viable option to import the Blizzard authenticator.
The text was updated successfully, but these errors were encountered: