MCL-4934Launcher forgets login token when switching Wi-Fi networks
When switching Wi-Fi networks, the Launcher seems to forget the login token, forcing you to login again.
To Reproduce:
1. Make sure you are logged in on the launcher screen.
2. Close the launcher
3. Connect to a different Wi-Fi network
4. Reopen the launcher
5. It should bring up the username screen, and will not allow you to login until reentering your credentials
Linked Issues
is duplicated by1
Created Issue:
Launcher forgets login token when switching Wi-Fi networks
When switching Wi-Fi networks, the Launcher seems to forget the login token, forcing you to login again.
To Reproduce:
1. Make sure you are logged in on the launcher screen.
2. Close the launcher
3. Connect to a different Wi-Fi network
4. Reopen the launcher
5. It should bring up the username screen, and will not allow you to login until reentering your credentials
Attachments3
is duplicated by
Duplicate of MCL-4934
I don't know if this is related to
MCL-4898or not.I've been able to replicate this same issue using two networks (not necessarily just wifi networks).
At first glance, it looks like access tokens are being linked to IP's now. Not sure if that's intentional. I remember being able to change networks without any issue.
However, I don't have a proxy nor two wired connections with a different IP to confirm that the IP change is the issue and not some other factor.
This seems to be fixed in 1.6.66 however I am not sure.
I just confirmed that this is still an issue in 2.0.320-stage. This time with a proxy (switching between two different IP addresses) rather than switching across networks. This might be something with the authentication servers, either intentional or not.
Yeah I've still seen this happen in 1.6.69. Not sure what's causing it.
Unsure if this is fixed in 1.6.70
Confirmed in 1.6.70
does this ever happen in 2.0? Not sure if fixed
Yes, still an issue, though it's probably intentional.
This doesn't happen to me in 2.0.806, switching between wired and wireless networks (with ips of 192.168.1.5, and 192.168.1.7)
Probably the tokens are assigned to a single IP
Seems to still happen in version 2 when joining new wi fi networks
The issue, technically, is that, as soon as you switch your IP address, the session and the login token gets invalidated.
I'm not sure if this has been fixed in 2.0.1049. Can anyone confirm?
I'm not sure if this is still a problem in version 2.1.1216. Can anyone confirm that this has been fixed?
I suppose this problem would also occur in a home WiFi or other shared WiFi with multiple clients, so that different devices get reassigned different IP addresses? Or is it only the public IP address that matters? In which case it would only happen when the broadband provider assigns a different public IP address to the customer router.
Because I get the problem when reconnecting to my own WiFi network, not just when connecting to a different WiFi network.
That means the bug is hard to replicate for me.
Sorry for all the small comments.
Cannot reproduce anymore, switching between Wifis does not log the user out anymore.