Authenticator Nightmare

Game said I needed to use authenticator. Fine. I have that on app. Had it for years.
However it said this time that I needed to download a new app.
New app required me to log in.
Google said my password in not secure and there was no option to keep original password. I couldn’t remove the Google insecure message without changing my password and could not access anything under the message until this had been done.
So I began to do this.
Then it said ~ Check the security code in your authenticator app.
Ehh? It’s saying get a code from your app to get access to your app? A code which you need access to your app to see? Can’t you guys see the problem here?
I mean who designed this mess?

So I remove the authenticator and try and set it up again from scratch.
Remove authenticator - change password to Battle Net via website - start again.
Set up authenticator. Use old or existing authenticator? Yes - obviously.
(I’m not buying a new phone just to play a game)

It asks for a serial code and password.

I have the password but I don’t have the foggiest idea what the serial code is. I don’t even remember having one?
So I go to Battle Net help to change it or tell the system I need a new one.
But all the help says is;
“Enter the serial code you had when you set up the authenticator”
YES BUT WHERE IS IT - WHAT IS IT - AND IF I’VE LOST IT HOW DO I RECOVER IT???
After nearly an hour I removed the authenticator for a second time and gave up.

Had authenticator on keyfob then phone since before 2011.
Would happily keep using it if setting it up wasn’t such a massive and exasperating time sink that sends the user around in circles.
Bad programming logic and really poor UI UX design

1 Like

In case it helps these are the instructions in the pinned post.

Continuing the discussion from Authenticator Mobile App Migration Deadline Approaching:

If not then hopefully someone can help you soon :four_leaf_clover:

I still use the old app, you just need to get past the corporate stuff trying to force you to change.

If you have uninstalled the old app, without noting down its serial and restore codes, then you will need a new authenticator. There is no way to recover your serial or restore codes, once the app has been uninstalled, if you didn’t already note them down.

A new authenticator does not mean a new phone. I dunno where you got that idea from. It just means you need to install the authenticator as new (which will generate a new serial and restore code), and not a reinstall (which will ask for your old serial and restore codes).

You will also need to remove the old authenticator from your account, which, if I remember correctly, will involve Blizzard sending a one time code via SMS to the phone number registered to the account. If you did not keep that phone number up to date, you may run into problems and require a GM intervention.

Its deliberately designed to be “not easy” to remove an “lost” authenticator. An easily removed authenticator is almost as bad as no authenticator at all, in terms of security.

“lost” in this case meaning one where you no longer have the serial and restore codes.

OP’s problems seems to have started with Google service they use to manage/save passwords and it warning that the used password has been either exposed, used in multiple services or is otherwise weak. It has nothing to do with Blizzard and Blizzard can’t be responsible for managing your own device (or learning how to use different features of the device).

The advice given by Google is valid though: never use same password in multiple services and make sure the passwords are strong enough.

Personally I have not used Google’s Password manager as I use another which works in more devices/operating systems/browsers.

Personally for me the move to stupid merged app was fairly smooth: install new app, login to it, authorize login, done, for now I get notifications about logins to both apps on my devices.

The problem with Google password manager is that it only works with google, so you have to either type it in to battle.net authenticator or other things you use, like steam, epic or any program.

I don’t fancy typing all those random letters with random caps into a password box for 5 minutes just to get in.

Hey Scritty,

I’ve never encountered this message, however checking Google’s FAQ, it looks like you can dismiss the warning. The page also explains why they may ask their users to change a password.

That being said, and in theory, all you should have needed to do was change your password, and log back in the old app. Once this was done, you should’ve received a message inviting you to migrate to the new app., which is an automatic process, and doesn’t require a code to do so.

As mentioned by Punyelf, please do read the pinned thread Authenticator Mobile App Migration Deadline Approaching for more information concerning the Authenticator migration.

If you still need help, you are always welcome to open a ticket.

1 Like

Appreciate the replies.
I suppose my issue was not seeing the serial number? If I’d had that I think I would have got through. I wasn’t aware there was a serial number. I’ve had an authenticator on my account for more than 10 years.
It seems likely I was given a serial number at some point (when I moved to the phone app - the keyfob has one printed on a label at the back - I still have it) but I have no recollection of that. It was many years ago.
Yes - Google started the problem/Not Blizzard. My lack of a serial number compounded it. I’ll try and install the app as new later.

Thanks for the helpful replies everyone. It is appreciated.

The serial number (and recovery code) of the Authenticator is available in the Settings of either application, but you shouldn’t need it unless you’re trying to disable your Authenticator, or if you’re trying to restore it after changing your phone (and aren’t using a cloud recovery system for your apps).

Off-topic, but Google’s password manager (like many others) support auto-fill in Android, though sometimes the apps have made using that difficult (eg. fields are not properly marked as password etc). So in most cases manually typing is not required.