-
Notifications
You must be signed in to change notification settings - Fork 79
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 proposal for robot permission expansion #249
Conversation
Signed-off-by: wang yan <[email protected]>
5ee1671
to
3e07e2d
Compare
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
Signed-off-by: wang yan <[email protected]>
Signed-off-by: wang yan <[email protected]>
Signed-off-by: wang yan <[email protected]>
2. any system level robot account can be created by a system level robot account who with the robot creation permission. | ||
|
||
Deletion/Update: A robot account cannot assign permissions to another robot account that exceed its own permissions. | ||
1. any robot account that created by another robot can be updated by the creator robot or the itself, provided that the update permission has been granted to the creator or the robot itself. |
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.
the itself
should be itself
## Robot accounts that are created and managed by another robot accounts | ||
|
||
Robot accounts are principals, it means that you can grant robot account to Harbor resources. However, from the perspective of preventing privilege escalation, generally, a robot account | ||
cannot grant roles that are higher or more powerful than the roles it possesses. When a robot account creates a new robot account, the new robot account doesn't automatically inherit any roles |
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.
replace role with permission, avoid using role because the role is only used in project member,
Signed-off-by: wang yan <[email protected]>
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
Update codes according to the proposal of goharbor/community#249 Signed-off-by: wang yan <[email protected]>
Update codes according to the proposal of goharbor/community#249 Signed-off-by: wang yan <[email protected]>
Update codes according to the proposal of goharbor/community#249 Signed-off-by: wang yan <[email protected]>
* have option to enable robot full access When the system admin enable this option, the robot can be assigned with robot/user/group/quota permissions. Signed-off-by: wang yan <[email protected]> * robot account permission enhancement Update codes according to the proposal of goharbor/community#249 Signed-off-by: wang yan <[email protected]> --------- Signed-off-by: wang yan <[email protected]>
Signed-off-by: wang yan <[email protected]>
Signed-off-by: wang yan <[email protected]>
8cf6aef
to
8a9319a
Compare
No description provided.