Battle.NET account + Blizzard Authenticator + today = fail

[Mystic]

So, anyone else seeing this behavior starting this evening?

Login servers were "busy" for a short bit this evening. After they became available again, I was unable to log in my normal way.

I use keyclone, and have it set up (with workaround) to enter my battle.net account info, and the specific individual accounts are saved from the last usage, so all I have to do is enter my password, and then enter my blizzard authenticator key at the next prompt. After that I'm logged in on all five simultaneously. This has worked flawlessly for a long time now.

Tonight, after the login servers became "unbusy", now only one specific account is logged in, the other four fail with a message something like "account credentials failed". After some experimentation it is revealed that EACH individual login instance now requires its OWN DIFFERENT authenticator number (not the physical key, but the numbers it generates). This means you can no longer log in all five (or 10) at the same time, but now must log in one, wait for about 8 seconds for the authenticator key to generate a new number, then log in the next, etc. until you get all of your accounts logged in.

Anyone else experiencing this with their battle.net account + blizzard authenticator this evening?

[SFbase]

Ya I noticed that this morning! I thought that it was a fluke on my part. But man, this is gonna suck.

[zanthor]

Authenticator has been turned into a 1 time pad. 1 key = 1 attempt, if you botch the password the keys gone, if you try to log in 5x with broadcast, 4 get denied.

Fuck.

[falsfire3401]

I was under the impression it always worked like this. I think I once (months and months ago) tried logging in all three accounts with the same key code from the authenticator and it failed, so the whole time I've had it I've been patiently waiting the 20 seconds or whatever for a fresh code for each account...

[Jubber]

lol false. yeah its bungled right now. I have not been able to transmit the same code since the servers came back up. It is very annoying.

[Moorea]

my subs are now expired but for many months until late september I always sent the same code to all 5 windows and logged all at once - they better fix this bug if it's not possible anymore - someone with a valid sub should file a bug report with them ?

[burningforce]

hmm thought it was me that was having the problems.

not fun, log in one character, wait 20 seconds then do the other character and repeat as neccisary hehe

[moosejaw]

Very fubar. This blows.

[Lazyassguy1776]

Yup.. this is BS... I thought I had capps lock on or something.

[zanthor]

http://forums.worldofwarcraft.com/th...827954&sid=1#0

Different forum, same approach.