Not sure if I’m wrong , somebody correct me if that is the issue. So the new authenticator lives in the app. You must be logged into the app to be able to recover the authenticator (even if that options is available now, do not see it). So in this scenario I have saved the authenticator recovery serial and code. I got a new phone (old phone no longer available) and I install the Blizzard app, unlike the previous one were the authenticator was standalone and I was able to recover , with this new method I can’t because I have to log in, and to be able to log in I have to get an authentication code. So I’m stuck. Can’t recover because you have to log in and to be able to log in you need the authenticator running. So the only solution is to disable the authenticator, but to do that you have to have a phone number in the account (no voip numbers allowed just paid ones) and then remove authenticator with an sms code to log into web account interface and then install attach new authenticator. If you do not have a phone in the account you have to go through support and answer a ton of questions that you hope you remember or saved this info. Not even an email link is sent to your email to recover the account. So I tested the account with no authenticator to see if Blizz will send an email verification when it detects a long in from a new system or completely unknown IP (steam and everybody else does this). Nope does not happen. If security was a main point here you will at least give the users with no authenticator an email notification with a code when a log in happens from a new IP or system. This is one hell of a mess with this new integration app and authenticator. I just went through this headache to recover my account because of this exact point, and had to answer a history of questions to get support to remove the authenticator from my account.
If I’m wrong here please correct me, Is there a way to recover the authenticator with the new app when you have the serial and backup code ( I do not see any option to do so) just wants you to log in
Cant you just log in to your account and disable it ? If you loged in before it should remember you and not ask for the code, it dosent ask me if i log in to my account
This is largely due to them texted you an SMS recovery code. VOIP numbers can not always get SMS messages, and sometimes they have exorbitant fees associated with it, if they can receive codes.
This actually is ANOTHER type of two factor authentication. Which is actually over-ridden by Password Token Authenticators like the app currently does.
The only recovery options, I’m aware of. Assuming you’re not logged in/remembered on a web-browser (which is arguably bad for you as far as security goes, depending on the situation).
Would be to directly call or email support directly.
My advise to YOU and anyone else who is in your situation.
Would be to log in, and update ALL of your account recovery info and questions, then write your answers down on a Sticky Note or note on your computer for easy access later if you need it. That or write it down in a physical journal you would have handy near your computer.
It’s a solution I had to do recently with NORD.
ALSO, if it’s an option Cricket Wireless is like $45usd/month with a single line, with unlimited data plans. So that would be able to bypass this thing entirely as well.
It might even be cheaper if you do the limited data option.
It’s worth mentioning because Steam and other platforms are considering doing something similar, and requiring 3rd party tokens or their main token as it’s more secure.
Heck I have to go through your hoops to reactivate my SWTOR, after I got a new phone…I just haven’t yet because it’s a big hassle.
Same. I can’t remember the exact process mind you but it’s been over year got rid of a galaxy 7 for and iPhone… I just remember it not causing me any stress or issues.
I’m showing a scenario were you no longer have your old phone and it is a new system. But you do have your authenticator recovery info on hand. You are locked out completely with the new authenticator buried inside the app. So you have to resort to contacting tech support. Were as before it was just a matter of installing the authenticator in the new device and entering the recovery info.