|
|
|
|
|
by Brybry
1645 days ago
|
|
Blizzard's Battle.net does, or at least did at one point. In 2020 my friend couldn't add a new credit card to his account because browsers updated their same-site cookie behavior. They were setting their JSESSIONID cookie wrong when doing oauth behind-the-scenes which caused a nice 302 redirect loop.
For whatever reason the API calls required both *.battle.net and account.blizzard.com. |
|
You have to activate them for the login but you can deactivate afterwards.