Battle.NET account + Blizzard Authenticator + today = fail

[alcattle]

The reason the servers are busy is the note on the log in page that came up after maintenance. I have not logged into Battle.net yet, and I still have not tried the dongle, might after open the box soon

[shaeman]

It sucks, and I hope they fix it, but I'll take the security of the authentication over convenience any day.
Let's face it, if a keylogger gets your battlenet password they've got access to all your accounts with no extra work.
Is 1-2 minutes really worth risking all your chars.

[lordmythic]

I thought this was normal, ever since I received my Authenticator a month ago this is how it worked for me. It would NOT accept the code at the same time on all accounts. I always have to wait for the next code to appear.

[Svpernova09]

Someone in #isboxer petitioned a GM, and the GM instructed him to post in Technical Support, Here's the link: http://forums.worldofwarcraft.com/th...33766552&sid=1

I'll try to keep it and Fur's thread up on the first pages. This is incredibly frustrating. And until they fix this. I would NOT merge to a battle.net account.

It sucks, and I hope they fix it, but I'll take the security of the authentication over convenience any day.
Let's face it, if a keylogger gets your battlenet password they've got access to all your accounts with no extra work.
Is 1-2 minutes really worth risking all your chars.

I don't think this is what anyone here is upset about, what we're upset about is the fact that it's worked 1 way forever (I've been on battle.net accounts using 1 authenticator code since I merged in March) , and now all of a sudden it doesn't work this way anymore, and there was no notice at all.