Authentication(Chinese) - Revision history

imported>TkTech: TkTech moved page Authentication(Chinese) to User:Lzs/Authentication(Chinese): Abandoned incomplete page, moving back to the originating user's namespace.

2019-03-14T15:56:20Z

TkTech moved page Authentication(Chinese) to User:Lzs/Authentication(Chinese): Abandoned incomplete page, moving back to the originating user's namespace.

← Older revision	Revision as of 15:56, 14 March 2019
(No difference)

imported>TkTech: TkTech moved page Authentication(Chinese) to User:Lzs/Authentication(Chinese): Abandoned incomplete page, moving back to the originating user's namespace.

2019-03-14T15:56:20Z

TkTech moved page Authentication(Chinese) to User:Lzs/Authentication(Chinese): Abandoned incomplete page, moving back to the originating user's namespace.

← Older revision	Revision as of 15:56, 14 March 2019
(No difference)

imported>TkTech: TkTech moved page Authentication(Chinese) to User:Lzs/Authentication(Chinese): Abandoned incomplete page, moving back to the originating user's namespace.

2019-03-14T15:56:20Z

TkTech moved page Authentication(Chinese) to User:Lzs/Authentication(Chinese): Abandoned incomplete page, moving back to the originating user's namespace.

← Older revision	Revision as of 15:56, 14 March 2019
(No difference)

imported>TkTech: TkTech moved page Authentication(Chinese) to User:Lzs/Authentication(Chinese): Abandoned incomplete page, moving back to the originating user's namespace.

2019-03-14T15:56:20Z

TkTech moved page Authentication(Chinese) to User:Lzs/Authentication(Chinese): Abandoned incomplete page, moving back to the originating user's namespace.

Show changes

imported>Lzs: /* Refresh */

2017-07-30T21:24:39Z

Refresh

← Older revision	Revision as of 21:24, 30 July 2017
(No difference)

imported>Lzs: /* Refresh */

2017-07-30T21:24:39Z

Refresh

← Older revision		Revision as of 21:24, 30 July 2017
Line 161:		Line 161:
	: 多个 <code>/authenticate</code> 在很短的时间内对相同账户的请求 (在短时间内考虑 3 个请求)，即使有正确的密码，最终将导致一个 <code>Invalid credentials.</code> 响应。这一错误在几秒钟后就会消失。		: 多个 <code>/authenticate</code> 在很短的时间内对相同账户的请求 (在短时间内考虑 3 个请求)，即使有正确的密码，最终将导致一个 <code>Invalid credentials.</code> 响应。这一错误在几秒钟后就会消失。

	== ~~Refresh~~ ==		== 刷新 ==

	~~Refreshes a valid~~ <code>accessToken</code>~~. It can be used to keep a user logged in between gaming sessions and is preferred over storing the user's password in a file~~ (~~see~~ [[lastlogin]]).		刷新一个有效的 <code>accessToken</code>。它可以用来让用户在游戏会话之间登录并且优先在文件中存储用户的密码 (查看 [[lastlogin]]).

	=== 端点 ===		=== 端点 ===

imported>Lzs: /* 响应 */

2017-07-30T21:23:01Z

响应

← Older revision	Revision as of 21:23, 30 July 2017
(No difference)

imported>Lzs: /* 响应 */

2017-07-30T21:23:01Z

响应

← Older revision		Revision as of 21:23, 30 July 2017
Line 156:		Line 156:
	目前每个帐户只能拥有一个配置文件，不过在未来的计划中每个账户可以拥有多个配置文件。如果用户没有附加Minecraft许可证的情况下试图登录到一个有效的Mojang账户，身份验证将会成功，但响应不会包含 <code>selectedProfile</code> 字段，并且 <code>availableProfiles</code> 数组将为空。		目前每个帐户只能拥有一个配置文件，不过在未来的计划中每个账户可以拥有多个配置文件。如果用户没有附加Minecraft许可证的情况下试图登录到一个有效的Mojang账户，身份验证将会成功，但响应不会包含 <code>selectedProfile</code> 字段，并且 <code>availableProfiles</code> 数组将为空。

	~~Some instances in the wild have been observed of Mojang returning a flat~~ <code>null</code> for failed refresh attempts against legacy accounts. It's not clear what the actual error tied to the null response is and it is extremely rare, but implementations should be wary of null output from the response.		在某些情况下，观察到Mojang对遗留帐户的刷新尝试失败时返回一个<code>null</code>。目前还不清楚空响应的实际错误是什么并且非常罕见。但是，实现上应该警惕响应的空输出。

	~~This endpoint is severely rate-limited~~: ~~multiple~~ <code>/authenticate</code> ~~requests for the same account in a short amount of time~~ (~~think~~ 3 ~~requests in a few seconds~~)~~, even with the correct password, will eventually lead to an~~ <code>Invalid credentials.</code> ~~response. This error clears up a few seconds later.~~		这个端点是频率限制;
			: 多个 <code>/authenticate</code> 在很短的时间内对相同账户的请求 (在短时间内考虑 3 个请求)，即使有正确的密码，最终将导致一个 <code>Invalid credentials.</code> 响应。这一错误在几秒钟后就会消失。

	== Refresh ==		== Refresh ==

imported>Lzs: /* 响应 */

2017-07-30T21:21:57Z

响应

← Older revision	Revision as of 21:21, 30 July 2017
(No difference)

imported>Lzs: /* 响应 */

2017-07-30T21:21:57Z

响应

← Older revision		Revision as of 21:21, 30 July 2017
Line 156:		Line 156:
	目前每个帐户只能拥有一个配置文件，不过在未来的计划中每个账户可以拥有多个配置文件。如果用户没有附加Minecraft许可证的情况下试图登录到一个有效的Mojang账户，身份验证将会成功，但响应不会包含 <code>selectedProfile</code> 字段，并且 <code>availableProfiles</code> 数组将为空。		目前每个帐户只能拥有一个配置文件，不过在未来的计划中每个账户可以拥有多个配置文件。如果用户没有附加Minecraft许可证的情况下试图登录到一个有效的Mojang账户，身份验证将会成功，但响应不会包含 <code>selectedProfile</code> 字段，并且 <code>availableProfiles</code> 数组将为空。

	~~在某些情况下，观察到Mojang对遗留帐户的刷新尝试失败时返回一个~~<code>null</code>~~。目前还不清楚空响应的实际错误是什么并且非常罕见。但是，实现上应该警惕响应的空输出。~~		Some instances in the wild have been observed of Mojang returning a flat <code>null</code> for failed refresh attempts against legacy accounts. It's not clear what the actual error tied to the null response is and it is extremely rare, but implementations should be wary of null output from the response.

	~~这个端点是频率限制;~~		This endpoint is severely rate-limited: multiple <code>/authenticate</code> requests for the same account in a short amount of time (think 3 requests in a few seconds), even with the correct password, will eventually lead to an <code>Invalid credentials.</code> response. This error clears up a few seconds later.
	: 多个 <code>/authenticate</code> ~~在很短的时间内对相同账户的请求~~ (~~在短时间内考虑~~ 3 ~~个请求~~)~~，即使有正确的密码，最终将导致一个~~ <code>Invalid credentials.</code> ~~响应。这一错误在几秒钟后就会消失。~~

	== Refresh ==		== Refresh ==
Line 189:		Line 188:
	<syntaxhighlight lang="javascript">		<syntaxhighlight lang="javascript">
	{		{
	"accessToken": "random access token", // ~~hexadecimal~~		"accessToken": "random access token", // 十六进制
	"clientToken": "client identifier", // ~~identical to the one received~~		"clientToken": "client identifier", // 与接收到的相同
	"selectedProfile": {		"selectedProfile": {
	"id": "profile identifier", // ~~hexadecimal~~		"id": "profile identifier", // 十六进制
	"name": "player name"		"name": "player name"
	},		},
	"user": { // ~~only present if requestUser was true in the request payload~~		"user": { // 只有在请求有效载荷中requestUser为true时才出现
	"id": "user identifier", // ~~hexadecimal~~		"id": "user identifier", // 十六进制
	"properties": [		"properties": [
	{		{
	"name": "preferredLanguage", // ~~might not be present for all accounts~~		"name": "preferredLanguage", // 可能不适用于所有帐户
	"value": "en" // ISO 639-1?		"value": "en" // ISO 639-1标准，中文使用zh表示
	},		},
	{		{
	"name": "twitch_access_token", // ~~only present if a twitch account is associated~~ (~~see~~ https://account.mojang.com/me/settings)		"name": "twitch_access_token", // 只有在与twitch帐户相关联时会出现 (查看 https://account.mojang.com/me/settings)
	"value": "twitch oauth token" // OAuth 2.0 ~~Token; alphanumerical; e~~.g. https://api.twitch.tv/kraken?oauth_token=[...]		"value": "twitch oauth token" // OAuth 2.0 令牌；字母数字混合；e.g. https://api.twitch.tv/kraken?oauth_token=[...]
	// ~~the Twitch API is documented here~~: https://github.com/justintv/Twitch-API		// 这里记录了Twitch的API: https://github.com/justintv/Twitch-API
	}		}
	]		]