-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add description for tidb_auth_token
authentication
#15818
Conversation
1e852d2
to
a55008e
Compare
a55008e
to
aea7c4f
Compare
/cc bb7133 |
security-compatibility-with-mysql.md
Outdated
|
||
`tidb_auth_token` 是一种基于 [JSON Web Token (JWT)](https://datatracker.ietf.org/doc/html/rfc7519) 的无密码认证方式,用于 TiDB Cloud 内部用户认证。不同于 `mysql_native_passsword`、`caching_sha2_password` 等使用密码的认证方式,创建 `tidb_auth_token` 用户时无需设置并保存自定义的密码;使用 `tidb_auth_token` 进行登录时使用签发的 token 进行登录,可以简化用户的认证过程并提升安全性。 | ||
|
||
JWT 由 header、payload 和 signature 三部分组成,每部分使用 base64 编码之后拼接成一个字符串,中间用点号(`.`)分开。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
文档中混用了 'header'、'payload' 这些英文的大小写(首行大写),我感觉放在中文文档里面这么用比较怪异,是不是全首字母大写比较好?可以请文档的同事提一下建议。
security-compatibility-with-mysql.md
Outdated
|
||
### `tidb_auth_token` | ||
|
||
`tidb_auth_token` 是一种基于 [JSON Web Token (JWT)](https://datatracker.ietf.org/doc/html/rfc7519) 的无密码认证方式,用于 TiDB Cloud 内部用户认证。不同于 `mysql_native_passsword`、`caching_sha2_password` 等使用密码的认证方式,创建 `tidb_auth_token` 用户时无需设置并保存自定义的密码;使用 `tidb_auth_token` 进行登录时使用签发的 token 进行登录,可以简化用户的认证过程并提升安全性。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
用于 TiDB Cloud 内部用户认证
comment 同上
9c374cd
to
4928719
Compare
4928719
to
b134276
Compare
Co-authored-by: bb7133 <bb7133@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@bb7133: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: qiancai The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
In response to a cherrypick label: new pull request created to branch |
In response to a cherrypick label: new pull request created to branch |
In response to a cherrypick label: new pull request created to branch |
What is changed, added or deleted? (Required)
Add description for
tidb_auth_token
, which can be used not only inside TiDB Cloud, but also by normal tidb users.Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions (in Chinese).
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?