[MCL-1705] Logging in with the old launcher system invalidates the session/tokens from the new launcher

The session or access tokens or something from the new launcher system get invalidated every time I log in with the same account with a version of the old launcher system (including 3rd party launchers).

Steps to reproduce:

Start the new launcher and log in normally.
Close the launcher. (You can start the new launcher again, and you will be automatically logged in as is supposed to happen. Close the launcher.)
Log in using the old vanilla launcher, or a 3rd party launcher such as MultiMC, using the same account. Close the game/launcher.
Start the new launcher again, you will be thrown out and you need to retype your email and password and Log in again. (It says that you are logged in in another profile, and when I click Play, it throws me out with a "InvalidCredentialsException: Invalid token." error)

This is pretty frustrating, because it means that I need to log in again practically every time I start the new launcher, because I play a lot with older versions/instances (FTB/modded minecraft, using MultiMC).

Linked issues

is duplicated by 1

MCL-2065 Access tokens are automatically invalidated when a non-Yggdrasil launcher (such as FTB) authenticates with Mojang Resolved

relates to 2

MCL-1657 Invalid token on launcher start Resolved

MCL-1513 Access token gets invalidated after logging in on a different computer Resolved

Comments 5

kumasasa 2013-11-03T09:12:18Z

~~Old launcher / 3rd party launcher uses the old Username / Passwort system so the aquired token~~ ~~has to be~~ ~~invalidated at the authentication server.~~
~~Thus working as intended.~~

migrated 2013-11-03T11:07:06Z

Oh? How come it has been somehow magically fixed in/before launcher version 1.3.1 then? Well, anyway, as stated, it now works as I had hoped it would, where the old and new launchers don't affect each other anymore.

kumasasa 2013-11-03T11:21:20Z

Well, let's call it a ninja fix.

migrated 2014-01-02T17:21:31Z

Confirmed still broken in 1.3.7.

migrated 2014-01-02T17:35:08Z

I know that it isn't a direct fix, more of a workaround, using 3rd party products, but personally I have switched over to using MultiMC5. It is still considered pre-release, but it does work perfectly fine for me.

So basically if you are playing FTB for example, you can import the packs into MultiMC5, which uses the new login system. (and imo, is nicer to use than the vanilla launcher in some other aspects as well) That way you are not using the old login system anymore, (except when downloading a new version of the pack with the FTB launcher, and then import that into MultiMC again) and thus shouldn't run into this issue that often.