Skip to content
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

TiDB supports high-privilege accounts #18378

Closed
gejibin opened this issue Jul 6, 2020 · 5 comments · Fixed by #24416
Closed

TiDB supports high-privilege accounts #18378

gejibin opened this issue Jul 6, 2020 · 5 comments · Fixed by #24416
Assignees
Labels
feature/accepted This feature request is accepted by product managers priority/P1 The issue has P1 priority. type/feature-request Categorizes issue or PR as related to a new feature.

Comments

@gejibin
Copy link

gejibin commented Jul 6, 2020

Feature Request

在公有云上,给TiDB用户创建一个高权限的账号,权限与root账号一样,但是该高权限账号有如下限制:

  1. 不能删除root账号,修改root密码。
    2.不能删除内置账号,哪些是内置账号可以通过配置文件指定。

这样,用户可以通过高权限的账号做自己的任何操作,同时不影响服务提供方(公有云)运维tidb数据库。

目前,aurora和polarDB均支持这种高权限的账号。

On the public cloud, create a high-privilege account for TiDB users. The permissions are the same as the root account, but the high-privilege account has the following restrictions:

  1. Can not delete the root account and change the root password.
  2. It is not possible to delete the built-in account, which can be specified through the configuration file.

In this way, users can do any of their operations through a high-privilege account without affecting the service provider (public cloud) operation and maintenance of the tidb database.

Currently, both aurora and polarDB support such high-privilege accounts.

@gejibin gejibin added the type/feature-request Categorizes issue or PR as related to a new feature. label Jul 6, 2020
@zhangjinpeng87
Copy link
Contributor

@gejibin Would you mind to participate in the development of this feature if we provide the design RFC?

@gejibin
Copy link
Author

gejibin commented Jul 15, 2020

@zhangjinpeng1987 if you can provide the detail-level design, we can Participate in development. But we are not very sure about the timing. If you can finish the detailed design next month, we may be able to complete this function before October.

@zz-jason
Copy link
Member

In this way, users can do any of their operations through a high-privilege account without affecting the service provider (public cloud) operation and maintenance of the tidb database.

Can it be accomplished by the current privilege system?

I'm a little confused about the desired privilege, could you give some links about the described privilege management in Aurora and PolarDB?

@gejibin
Copy link
Author

gejibin commented Jul 28, 2020

@zz-jason you can try to use the aurora or polarDB in Amazon Cloud or Alibaba Cloud.

@zz-jason zz-jason added the feature/reviewing This feature request is reviewing by product managers label Aug 6, 2020
@scsldb scsldb added feature/discussing This feature request is discussing among product managers and removed feature/reviewing This feature request is reviewing by product managers labels Aug 18, 2020
@scsldb scsldb added the priority/P1 The issue has P1 priority. label Aug 28, 2020
@zz-jason zz-jason removed their assignment Aug 28, 2020
@zz-jason zz-jason added feature/accepted This feature request is accepted by product managers and removed feature/discussing This feature request is discussing among product managers labels Aug 28, 2020
@scsldb scsldb added this to the Requirement pool milestone Aug 28, 2020
@ghost
Copy link

ghost commented Aug 30, 2020

I believe this is a duplicate of #14148

There are a few ways to implement this, my preference would be via an admin-only port.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature/accepted This feature request is accepted by product managers priority/P1 The issue has P1 priority. type/feature-request Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants