Battle.NET account + Blizzard Authenticator + today = fail

[Oswyn]

Here's something I noticed today. I log in using my battlenet account name and password for all accounts. I then put it the authenticator code one at a time using a new code for each account.

The first account logs in fine. I let the authenticator refresh and enter the code, it fails to log in. The only way for me to do it is to do the entire login process separately with each account using new authenticator codes. Does that make sense?

Any way, I'm wondering if the issue is not with the authenticators at all, but with the battlenet login. Can anyone without an authenticator, but with battlenet confirm that you can login simultaneously?

[Anastasiya]

Hey Osywn

are you logging in to all your accounts at the same time.. then entering each Auth number one at a time?

or are you logging on to each accout one at a time and then putting in a Auth number for that account before moving on to the next account?

Each Auth number only has a 60 sec life span, before a new one is generated. So if you log all your accounts at the same time you need to use the same Auth number for all of the accounts. This should be easily done by what ever keybrodacasting program you are using.

[Oswyn]

Hey Osywn

are you logging in to all your accounts at the same time.. then entering each Auth number one at a time?

or are you logging on to each accout one at a time and then putting in a Auth number for that account before moving on to the next account?

Each Auth number only has a 60 sec life span, before a new one is generated. So if you log all your accounts at the same time you need to use the same Auth number for all of the accounts. This should be easily done by what ever keybrodacasting program you are using.

Yeah I wasn't very clear at all in my post, head was somewhere else. Yes, I was logging into all accounts at once using password and then entering a newly generated auth number for each account. The first login worked. But the rest did not. The only way I could get it to work is to login with password and auth one account at a time.

[Damageinc333]

There is a way they could make all this work well for us and not compromise security. They could use the same system as the bank of america eink creditcard fob. There is no internal clock or 30second windows. You press the button, it spits out a key. You press it again it spits out the next key. The server does a "calibration" the first time you set it up asking you to enter 2 keys back to back, this lets it know where it is on the 'chain'. I suppose if you press the key a bunch of times incrementing the number without actually entering it to the server, this could cause it to lose its place and it would have to recalibrate. I have never had that happen yet. Is this system the way the iphone app works?

[Prepared]

Here's something I noticed today. I log in using my battlenet account name and password for all accounts. I then put it the authenticator code one at a time using a new code for each account.

The first account logs in fine. I let the authenticator refresh and enter the code, it fails to log in. The only way for me to do it is to do the entire login process separately with each account using new authenticator codes. Does that make sense?

Any way, I'm wondering if the issue is not with the authenticators at all, but with the battlenet login. Can anyone without an authenticator, but with battlenet confirm that you can login simultaneously?

I think the problem you're experiencing here is that if the Authenticator Code box remains up too long. Maybe 60 seconds or two minutes, not sure of the exact time, but the password that was previously entered becomes invalid. You have to cancel the authenticator box and re-enter the password and then new authenticator code.

According to the last page of this post made by a WoW player, the change makes sense to stop the keyloggers from getting access to your account with your authenticator code within 60 seconds:
http://forums.worldofwarcraft.com/th...sid=1&pageNo=2

Maybe it is for some other security reason that Blizzard has in place but with a ton of accounts like I have, this battle.net authenticator change really causes me a long time to login now. Apparently the change made with battle.net accounts and the authenticator was made on purpose to stop the keyloggers from gaining access to accounts within 60 seconds. That is, a different code for second login was necessary from the same authenticator to login to the battle.net account. It makes sense to me as this could cut down on support calls to Blizzard when someone loses their account with authenticator access to a keylogger. Multiboxers are in a far less number than the normal 1 account login with battle.net. So it would make sense from Blizzards perspective to reduce unauthorized access at the expense of a small number of players inconvenience.

[Prepared]

There is one way around all of this. Create multiple battle.net accounts. I've confirmed the same authenticator attached to multiple battle.net accounts allows the same code to be used at the same time. So if you have 5 WoW accounts for example, instead of creating just one battle.net account and merging all of those to the one battle.net, create 5 battle.net accounts. Merge each WoW account to each battle.net account and the authenticator that was attached to each WoW account will automatically be attached to each battle.net account. When Keyclone, Octopus or whatever you use to start WoW up with, you enter the account name with the separate battle.net account logins. The issue of having the same authenticator code used at the same time goes away because you have separate battle.net accounts. I've confirmed this. However, Blizzard could possibly change this is in the future but for now it works by logging in at the same time without any issues.