mojira.dev
MCL-1532

Password not properly stored

The launcher remembers my password not correctly: It makes my password 10 times as long!
My password is some random numbers with an explanation mark behind it.

Linked issues

Comments 9

It doesn't store your password at all... I don't quite understand what you mean sorry. What precisely is the issue here? Is it not logging you back in between sessions?

Hey dinnerbone 🙂

What happens is: When i log in, and then reboot the launcher my login seems to fail. This happens with the old launcher too, and when i look up my password with it, it seems to be three times as long.
This happens with all launchers, even the ones that are not made by Mojang.
The error it gives: InvalidCredentialsException: Invalid token
although it was able to log in earlier with the exact same settings, i have to retype my password

Your password is not stored anywhere on disk. We don't do that, that's incredibly insecure. The old one did. We store a "token", a series of random characters which allows you log in one-time-only (and then given another one for use in the future). It's like a one time only password, that you keep getting again.

That you can't log in after closing the launcher... I don't know. Are you using more than one launcher perhaps? Maybe it has issues writing to disk? Maybe this was when our servers were down.

No, it has been there for about a month now. an Yes, i am using more launchers, but they shouldn't affect the %appdata%/roaming/.minecraft folder: they are set to another destination

I tried to reboot the launcher twice, without using any other launcher, same problem.

Most programs will show a set length of '*' characters for the password field, rather than the actual length of your password, because that would make it easier for someone to guess your password.

Here's a test for you: copy the clientToken and accessToken lines out of launcher_profiles.json and paste it somewhere. Log into Minecraft, close it, compare both those lines to see if they've changed. Open the launcher and log in again, and check again to see if they've changed. clientToken should stay the same, accessToken should change.

Is this still a concern in the current Minecraft version 1.7.2 / Launcher version 1.3.1 ? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

I'd have to check, but if I remember correctly it is.

Yes, the issue is still here, but it's partially fixed: it now logs in more often than not, but it has its unsuccessful moments...

The error my launcher gave me through the dev console:
[11:25:17 ERROR]: Exception whilst logging into profile
com.mojang.authlib.exceptions.InvalidCredentialsException: Invalid token.
at com.mojang.authlib.yggdrasil.YggdrasilAuthenticationService.makeRequest(YggdrasilAuthenticationService.java:50) ~[launcher.jar:?]
at com.mojang.authlib.yggdrasil.YggdrasilUserAuthentication.logInWithToken(YggdrasilUserAuthentication.java:107) ~[launcher.jar:?]
at com.mojang.authlib.yggdrasil.YggdrasilUserAuthentication.logIn(YggdrasilUserAuthentication.java:55) ~[launcher.jar:?]
at net.minecraft.launcher.Launcher.ensureLoggedIn(Launcher.java:224) [launcher.jar:?]
at net.minecraft.launcher.Launcher$2.run(Launcher.java:193) [launcher.jar:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [?:1.7.0_45]
at java.util.concurrent.FutureTask.run(Unknown Source) [?:1.7.0_45]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.7.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.7.0_45]
at java.lang.Thread.run(Unknown Source) [?:1.7.0_45]

migrated

(Unassigned)

Unconfirmed

bad-login, password

Retrieved