jeansfish / rfc6749.zh-cn

A translation of simplified chinese for RFC 6749-The OAuth 2.0 Authorization Framework. RFC 6749 - OAuth 2.0授权框架简体中文翻译。

RFC6749.zh-cn

A translation in Simplified Chinese for RFC 6749-The OAuth 2.0 Authorization Framework.

RFC 6749-OAuth 2.0授权框架简体中文翻译。

TODO

总体翻译已完成，希望大家帮忙完善下哦。

开始阅读

rfc6749.zh-cn's Issues

Character flow figures haven't been translated.

For the layout of the figures, the content of them haven't been translated.

Have anyone know how to draw a beautiful character figure in Chinese?

Do me a favor please.

1.3.2节 "授权码" 的超链接有误

https://github.com/jeansfish/RFC6749.zh-cn/blob/master/Section01/1.3.2.md

这里"授权码"的这超链接指向为
https://github.com/jeansfish/RFC6749.zh-cn/blob/master/Section01/1.3.1md
应该修改为
https://github.com/jeansfish/RFC6749.zh-cn/blob/master/Section01/1.3.1.md

建议将翻译文档中的一些名词术语保留英文

建议将翻译文档中的一些名词术语保留英文，比如:
HTTP Basic

能发布一个单页的版本吗？

这样看起来有连续性

协议汉化的优化。

协议的文档中汉化 ，真的需要优化，行文很少有断句，不便于阅读。翻译质量有需要改进。
如在1.3.2中 原汉化部分 优化部分
The implicit grant is a simplified authorization code flow optimized
for clients implemented in a browser using a scripting language such
as JavaScript. In the implicit flow, instead of issuing the client
an authorization code, the client is issued an access token directly

(as the result of the resource owner authorization). The grant type
is implicit, as no intermediate credentials (such as an authorization
code) are issued (and later used to obtain an access token).

When issuing an access token during the implicit grant flow, the
authorization server does not authenticate the client. In some
cases, the client identity can be verified via the redirection URI
used to deliver the access token to the client. The access token may
be exposed to the resource owner or other applications with access to
the resource owner's user-agent.

Implicit grants improve the responsiveness and efficiency of some
clients (such as a client implemented as an in-browser application),
since it reduces the number of round trips required to obtain an
access token. However, this convenience should be weighed against
the security implications of using implicit grants, such as those
described in Sections 10.3 and 10.16, especially when the
authorization code grant type is available.

1.3.2。 隐式授权是简化的授权代码流程，该流程针对使用JavaScript之类的脚本语言在浏览器中实现的客户端进行了优化。 在隐式流程中，不是向客户端颁发授权代码，而是直接向客户端颁发访问令牌（作为资源所有者授权的结果）。 授予类型是隐式的，因为没有颁发中间凭证（例如授权码）（以后用于获取访问令牌）。
在隐式授予流程中颁发访问令牌时，授权服务器不会对客户端进行身份验证。 在某些情况下，可以通过用于将访问令牌传递给客户端的重定向URI验证客户端身份。 访问令牌可以向资源所有者或其他具有资源所有者的用户代理访问权限的应用程序公开。
隐式授予提高了某些客户端（例如，实现为浏览器内应用程序的客户端）的响应能力和效率，因为它减少了获取访问令牌所需的往返次数。 但是，应该权衡此便利性与使用隐式授予的安全隐患，例如在10.3和10.16节中描述的隐含授予，尤其是在授权码授予类型可用时。

大佬有考虑再翻译下OAuth2.1嘛

OAtuh2.1