It should be... one time code.. per account.
Not one code per battlenet account.
Printable View
It should be... one time code.. per account.
Not one code per battlenet account.
I don't mind the one code per account thing, just give us a countdown timer on the device so I know when the new number will be refreshed.
Push.......wait ....... push......... wait........push New Number!!!! repeat.....
Seems you all are upset ONLY because something changed and no one at bliz said shit about it. My take on it is this, my computer really hates me when I log all 5 at once anyway, but I can do it. I don't, I just log them all one at a time. Sure it takes a while to do, but once you log in with a key code, it instantly refreshes it. You may be lucky enough to have the option of the battlenet passwoord but quit crying over something that not only increases security, but is completely trivial lol :)
Ps. I'm pooping at work right now! Lol
^^ This. I am going to open a new line on my ATT account and get an iPhone. Mobile armory and all my iTunes videos, Woot!Quote:
Originally Posted by Fursphere
Edit: I have to remember to write down the authenticator serial in case the phone crashes though. :)
I love the mobile armory!Quote:
Originally Posted by moosejaw
Iphone order complete. LoL
Edit: Can anyone recommend a good carry case/sleeve for the iPhone? I know, a little off topic.
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?
Sort of a related question: after I convert all my accounts to one Bnet acccount will I be bill once per month for all my subs or will I still get billed 5 seperate times per month?
Can I create seperate Bnet accounts for each of my persent Accounts, if I do are there any ramifications to this approach, Will I not be able to transfer charaters between them or multibox if they are seperate Bnet accounts?
Thanks
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.
Each WOW account is still billed separately.Quote:
Originally Posted by Targ
hopefully.
logging in is a pain now >.<
While not really a sleeve or case I suggest InvisiShield, it was the best $24 I spent protecting the face of my iPhone and it lasts forever. An additional benefit was that it seem to make the touch-screen more sensitive.Quote:
Originally Posted by moosejaw
I just switched to the iPhone authenticator and like you said Fur, it's great knowing just how long you have before it expires!Quote:
Originally Posted by Fursphere
Just for grins I setup my browser to log in to Bnet along with logging into the actual game. I logged into WoW on one account (only tried 1) and then quickly tried to log into Bnet with the same mobile authenticator key and the login attempt was unsuccessful.
The extra piece of mind is nice.
if they leave it as is they need to at least make it so you can switch wow account without having to log out (and somehow changing realm stopped working for me too after first login when I switched)
I noticed that I had to use every other authenticator code in order for it to work for me.
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.Quote:
Originally Posted by Anastasiya
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?
http://www.securityinfowatch.com/fil...9_RSA_Card.jpg
All very nice, but what are now the facts. (besides the iphone geek stuff :)
What I understood is
- merging 5 accounts to 1 Bnet account means 5 different numbers (on single Authenticator) are needed to log in, which means login time for 5 accounts = 2.5 min+
- One authenticator for more than one Bnet account works.
How is the behaviour then ?
Can I log into 2 different Bnet accounts simultaneously with one authenticator generated number ?
Here is your answer Bloodcloud (quoted from page 4 of this thread)
Quote:
Originally Posted by Vecter
so the solution is to create 5 Battle.net accounts.
any restrictions on this or blizzard saying you HAVE to HAVE only one B.net account ?
http://us.battle.net/faq/index.html
does not imply that I have to.Hirelooms are bind to account and not to battle.net account anyway. so no immediate advantage.Code:Q: I play World of Warcraft using multiple accounts -- why should I merge all of them into the same Battle.net account?
A: One of our long-term goals for Battle.net is to introduce community and communication features that will make it beneficial for players to have all of the accounts and games they play associated with their own, single online identity. Merging all of your World of Warcraft accounts into one Battle.net account will enable you to take full advantage of these features in the future.
how does it work now ?Quote:
Originally Posted by Vecter
Did the "FIX" this now as well ?
can you confirm that simultanious login is still working on multiple B.net accounts with the same Authenticator token and code ?
I just tried using 2 B.net accounts and it in fact DOES WORK. The same authenticator code used for both and they both successfully logged in.Quote:
Originally Posted by Bloodcloud
So is there any reason not to setup 5 different B.net accounts?
Will I not be able to transfer toons between B.net accounts or will I be banned for boxing using different B.net accounts?
There is no "good" reason to set up more than one.. you will still have to enter the authenticator ID individually. Putting them all on one account is best. If you have more than eight, make another one for that reason only. It is much easier for You to manage the accounts when they are all on the same bnet account.Quote:
Originally Posted by Targ
For example, once they are linked, when you go to account management at the Bliz site, there is now a drop down list with all your accounts. So doing things like transfers and such are way less hassle than before.
I wanted to add, one benefit i have already had for having all my accounts on one bnet account. When i got my Grunty pet at blizcon, I entered my "bnet account name" and got the pet on ALL my accounts. I'm not sure if in the future they will do similar things, but maybe betas will work that way? Anyway, I think having separate Bnet accounts will complicate things for you more than the inconvenience of entering each accounts info separately while logging in the game. IMO
NOTE: If you plan to do any TRANSFERS, do it BEFORE you merge. IF you have more than one Bnet account you have to wait 30 days before you can transfer between them.
Quote:
Originally Posted by Lyonheart
You missed the post about this. It in fact does not require multiple tokens from the authenticator to log into different b.net accounts. I have 2 b.net accounts and tried this morning and had to only use 1 token to log into both accounts at the same time. Why this is is anyones guess and could either mean Blizzard didnt think about this scenario or the change to logging into multiple accounts under a single b.net was unintentionally changed to its current 1 token - 1 account method.
so this means that It could be a BUG/Fluke - THAT it currently works and blizz might fix it ?Quote:
Originally Posted by Vecter
actually setting up different B.Net accounts is no different from the current setup. You have your individual "account names" and use the token only once per account per login.
in a joined scenario you use the token for 5 logins on the same account.
pets: In other words if you want to have pets on all accounts by a single code and features alike, the less B.Net accounts you have the better
The only difference with one account vs multiple B.net accounts is the 60 day wait for transfers after the initial account merge. Keep that in mind.
That's what I was thinking. Or hoping, anyway.Quote:
Originally Posted by Bloodcloud
I suppose if you were to have multiple B.Net accounts, you can have an authenticator on each account.
If it was the same authenticator, like I have for my current 5 accounts, you'd likely have the same log in issues.
If it was a different authenticator per account, you'd have to enter a number on each authenticator (ie not broadcast/keyboard repeat), but there wouldn't likely be a 2.5 minute log in process either.
Quote:
Originally Posted by Vecter
something I read MAY be the issue, "Due to a security feature, a generated key is good once per account."
when you merge 5 accounts "Into one Bnet account" your login NOW becomes just 1 account
your account, One, two, three, four, five... they used to be separate... now with one Bnet account
your login for EVERY account is now Screwed@myaccounts.ouch and since you can aperrantly only use
1 code per login.... you have to Login 5 times with Screwed@myaccounts.ouch...
if someone with 2 B.net accounts can use the same authenticator on each "Login" and it works...
this sounds like a true statement..
Man I hope not!
I think the reactions here would be the same even if they announced it.Quote:
Originally Posted by ghonosyph
For those of us that have decent enough hardware to log in multiple characters at once, it isn't trivial when it takes 3 minutes of spamming your authenticator to log in, it's aggravating.
I just started my 4th and 5th account back in Sep and still using my RAF. (Trying to milk it for all its worth.)
I have many issues already with the whole mandatory B.Net (read x-box live meets myspace) thing but now I have to hold off even longer to make the choice between multiple B.Nets or one individual one. The whole time my RAF time is clicking away.
As a side note I was talking with one of my network security friends today and he was explaining how the Authenticators work.
Had I read this thread I would have gotten more in depth but one thing I did pick up was the fact that the Authenticator in itself is fairly secure. However:
Each Authenticator has an individual algorithm that is mirrored to an exact copy on the server which has been tied to each individual account (or B.net dependent on what you purchased) What most people don't know is that the Key prior, the current key and the next key will all work in that 60 second period (only one of any of those three would be accepted I believe though). (This is most likely due to Blizz planning ahead for latency or natural lazy "slow" human response time)
That being said what most of you are having issues with, the one code for one login, likely results from the code was used and now the sever side authenticator is looking for the next code.
As a side note to all you I-phone junkies:)
When I asked him about the cell phones authenticator apps he began laughing, the authenticator itself is secure but what people don't realize is by putting it on thier cell phone it has now just become less secure as I-phones etc...(constantly connected when turned on) are fairly easy to hack.
I will talk with him this weekend and try to find out more.
Let me know if there is anything you want me to ask him.
Remember he is a network security guy not a Blizz employee but he does know his stuff.
~Aes
Quote:
Originally Posted by Aesthier
I think that has been thoroughly determined as the point of the thread ;)
That didn't use to be the case though.
The safest bet, as far as logging in in the shortest period of time will be one B.Net account per wow account, with one authenticator per pairing.
From a blizzard point of view, each is essentially saying, "I live in a dorm, and several of us play wow. We each have our own account and own authenticator even if our IP address is always the same".
Sure Blizzard will easily figure out the accounts are linked, in that they have the synchronized key inputs and the same billing/owner information.
Essentially, going this route means nothing has changed.
This would cost 5 authenticators instead of 1, but even if they changed it to "a code is valid only once, even across multiple B.Net accounts", which seems likely if this was an intended change, with 5 authenticators you could enter the game in under a minute instead of 2.5 mins.
One authenticator and 5 B.Net accounts might work too. From an above poster is currently does. If the increased security is an intended feature, I'd suspect this will stop working at some point in the future.
I guess you could velcro/attach each authenticator to a piece of plastic/cardboard or whatever, and then just use the first one for account one etc.
Going with separate B.Net accounts per account essentially keeps the same hassles as the current system and specifically chooses to miss out on the features implemented with the B.Net account changes, such as easier account management. Not sure if that is worth more then the log into game hassles or not.
1234567890
I actually have 3 wow accounts on battle.net1 and 1 wow account on battle.net2. I was intending to transfer from the 2nd battle.net account to the first battle.net account...but if I do so then my login process gets worse. Now it is better to have a ratio of one battle.net to one wow account. There are no known benefits to having multiple wow accounts on the same battle.net account.
Due to how I slowly ramped up the number of accounts I have. My current team is 3 characters spread out over 2 battle.net accounts. I use a blizz authenticator and IS. Prior to the change, I could login to battle.net1-toon1, battle.net1-toon2, and battle.net2-toon1 with the same code. I did have to wait at times for the box to popup on all of them, but once it did...it always worked.
Now, I will get battle.net2-toon1 always logged in. Battle.net1-toon1 or battle.net1-toon2 will log on...and it does change which one "wins". I have to wait for a new code to get the one that was left out into game. The same blizz/iphone authenicator can be assigned to multiple battle.net accounts.
I can consistently reproduce this. It is annoying.
Well what I am wondering is if the whole authenticator the only real reason not to combine all the accounts on one B.Net.
I know the next major concern is someone hacking your B.Net account and having access to "all" ones accounts.For me though that's not such a big deal as it initially appears.
Another major concern is Accidental banning of one account will ban your B.net but if I remember correctly the blues confirmed that banning one WoW account does not ban all the accounts on the B.Net.
Other than those is there anything really nasty about it?
For Example how does it affect RAF if its all on One B.net?
I wouldn't think RAF would be affected at all.
There is still a referring account which would be one of your accounts, not all of them.
ugh, just when i was thinking about farming the headless horseman's mount...
as a point of interest
the keyfob authentication server is most likely separate from WoW's login servers
basically, when you login, the generated number is passed off to the keyfob auth server along with your keyfob serial number for verification
the main login server confirms your password and waits for the authentication response from the keyfob server, if both pass, then it lets you in
the way they had it set up before, the keyfob server would return a "pass" at any time during the 30 seconds when the generated number is valid
what they have now is the keyfob server would forcibly invalidate the key once it is used
the keyfob server technology is likely external proprietary and blizzard would have no direct control over the code
the best we can hope for is probably a "per keyfob serial number" option to turn the forced invalidation on/off