Legacy Mojang Authentication - Revision history

imported>LassiPulkkinen: Remove Category:Protocol Details.

2024-02-26T18:56:57Z

← Older revision		Revision as of 18:56, 26 February 2024
Line 302:		Line 302:
	[https://github.com/Kronos666/mclaunch-util-lib Java] \| Legacy full Yggdrasil wrapper in Java.		[https://github.com/Kronos666/mclaunch-util-lib Java] \| Legacy full Yggdrasil wrapper in Java.

	~~[[Category:Protocol Details]]~~
	[[Category:Minecraft Modern]]		[[Category:Minecraft Modern]]

2023-02-02T12:36:19Z

Refactored the "Requests" section and properly updated the fields in "Errors" section.

2022-11-10T12:49:17Z

← Older revision	Revision as of 12:49, 10 November 2022
(No difference)

2022-08-03T00:44:49Z

Added a new error I've got, if really needed I can provide some screnshots of it

← Older revision		Revision as of 00:44, 3 August 2022
Line 90:		Line 90:
	\|		\|
	\| Invalid salt version		\| Invalid salt version
			\| ???
			\|-
			\| <code>IllegalArgumentException</code>
			\|
			\| Access Token can not be null or empty.
	\| ???		\| ???
	\|-		\|-

2022-07-01T23:14:26Z

Undo revision 17628 by Stef (talk)

← Older revision		Revision as of 23:14, 1 July 2022
Line 1:		Line 1:
	Minecraft 1.7 introduced a new authentication scheme called '''Yggdrasil''' which completely replaces the [[Legacy Authentication\|previous authentication system]]. Mojang's other game, Scrolls, uses this method of authentication as well. Mojang has said that [https://twitter.com/KrisJelbring/status/453573406341206016 this authentication system should be used by everyone for custom logins], but [https://twitter.com/KrisJelbring/status/461390585086361600 credentials should never be collected from users]. For newer Microsoft accounts, see [[Microsoft Authentication Scheme]].		Minecraft 1.6 introduced a new authentication scheme called '''Yggdrasil''' which completely replaces the [[Legacy Authentication\|previous authentication system]]. Mojang's other game, Scrolls, uses this method of authentication as well. Mojang has said that [https://twitter.com/KrisJelbring/status/453573406341206016 this authentication system should be used by everyone for custom logins], but [https://twitter.com/KrisJelbring/status/461390585086361600 credentials should never be collected from users]. For newer Microsoft accounts, see [[Microsoft Authentication Scheme]].

	== Request format ==		== Request format ==

2022-07-01T22:52:20Z

← Older revision		Revision as of 22:52, 1 July 2022
Line 1:		Line 1:
	Minecraft 1.6 introduced a new authentication scheme called '''Yggdrasil''' which completely replaces the [[Legacy Authentication\|previous authentication system]]. Mojang's other game, Scrolls, uses this method of authentication as well. Mojang has said that [https://twitter.com/KrisJelbring/status/453573406341206016 this authentication system should be used by everyone for custom logins], but [https://twitter.com/KrisJelbring/status/461390585086361600 credentials should never be collected from users]. For newer Microsoft accounts, see [[Microsoft Authentication Scheme]].		Minecraft 1.7 introduced a new authentication scheme called '''Yggdrasil''' which completely replaces the [[Legacy Authentication\|previous authentication system]]. Mojang's other game, Scrolls, uses this method of authentication as well. Mojang has said that [https://twitter.com/KrisJelbring/status/453573406341206016 this authentication system should be used by everyone for custom logins], but [https://twitter.com/KrisJelbring/status/461390585086361600 credentials should never be collected from users]. For newer Microsoft accounts, see [[Microsoft Authentication Scheme]].

	== Request format ==		== Request format ==

2022-01-24T11:33:16Z

Notes that the server might also return "GoneException" when the account has been migrated already.

← Older revision		Revision as of 11:33, 24 January 2022
Line 101:		Line 101:
	\| Gone (410) - The requested resource is no longer available at the server and no forwarding address is known		\| Gone (410) - The requested resource is no longer available at the server and no forwarding address is known
	\| Account was migrated to Microsoft account		\| Account was migrated to Microsoft account
			\|-
			\| <code>GoneException</code>
			\|
			\| Gone (410) - The requested resource is no longer available at the server and no forwarding address is known
			\| Account was migrated to a Microsoft account
	\|}		\|}

2021-11-28T05:36:35Z

IllegalArgumentException is no longer the error when username/password is missing. Instead, the server throws a ForbiddenOperationException.

← Older revision		Revision as of 05:36, 28 November 2021
Line 76:		Line 76:
	\| Token does not exist.		\| Token does not exist.
	\| <code>accessToken</code> was used in another session that was issued AFTER this session.		\| <code>accessToken</code> was used in another session that was issued AFTER this session.
			\|-
			\| <code>ForbiddenOperationException</code>
			\|
			\| Forbidden
			\| Username/password was not submitted or password is less than 3 characters.
	\|-		\|-
	\| <code>IllegalArgumentException</code>		\| <code>IllegalArgumentException</code>
Line 81:		Line 86:
	\| Access token already has a profile assigned.		\| Access token already has a profile assigned.
	\| Selecting profiles isn't implemented yet.		\| Selecting profiles isn't implemented yet.
	\|-
	~~\| <code>IllegalArgumentException</code>~~
	\|
	~~\| credentials is null~~
	~~\| Username/password was not submitted.~~
	\|-		\|-
	\| <code>IllegalArgumentException</code>		\| <code>IllegalArgumentException</code>

2021-11-27T01:25:06Z

Add username field in refresh response

← Older revision		Revision as of 01:25, 27 November 2021
Line 206:		Line 206:
	},		},
	"user": { // only present if requestUser was true in the request payload		"user": { // only present if requestUser was true in the request payload
			"username": "user@email.example", // email for Mojang accounts or account username for legacy Minecraft accounts
	"id": "user identifier", // hexadecimal		"id": "user identifier", // hexadecimal
	"properties": [		"properties": [

2021-10-02T15:17:20Z

Success is not always 200, empty payload is not JSON

← Older revision		Revision as of 15:17, 2 October 2021
Line 15:		Line 15:
	If a request was successful the server will respond with:		If a request was successful the server will respond with:

	* ~~Status~~ code <code>~~200~~</code>		* A successful status code <code>2XX</code>
	* A [[wikipedia:JSON\|JSON]]-encoded dictionary according to the specifications below		* An empty payload or a [[wikipedia:JSON\|JSON]]-encoded dictionary according to the specifications below

	If however a request fails, the server will respond with:		If however a request fails, the server will respond with: