-
Feature Request
-
Resolution: Done
-
Critical
-
None
-
None
-
False
-
None
-
False
-
Not Selected
-
x86_64
-
0% To Do, 0% In Progress, 100% Done
-
-
-
-
-
Right now, only Organization owners can create OAuth tokens, and the tokens are created on behalf of the user who has created. The problem is that when the token is created for and used by some organization member, the action is logged to the token creator. In restricted environments, where only dedicated registry administrators are organization owners, this is undesirable due to inaccurate auditing.
There should be an option to assign the OAuth token to a specific user, meaning that the actions performed by this token will be logged to this user, and the user will be accountant of this token.
- is duplicated by
-
RFE-4510 Team Role that allows token access but doesn't allow create. (A limited "admin" type role)
- Rejected
- relates to
-
PROJQUAY-3394 Ability for robot accounts to access the API
- Closed