|
whw1sfb opened 2 years ago
|
||||
|
@whwlsfb I moved issue here. Manual project is for user guide. |
||||
|
|
👌 |
||||
|
a fine grained permission model for tokens would also be handy. for example create a token that can get repositories but not create new repositories. |
||||
|
OneDev changed state to 'Closed' 11 months ago
|
||||
|
|
State changed as code fixing the issue is committed (1a139bb7) |
||||
|
|
To get fine-grained access token permission, just create an user with desired permission, and create access token. Managing access token permission separately from its owner means to duplicate the role assignment functionality again, which is overly complicated, considering OneDev is targeting self-hosted usage scenarios. |
||||
|
|
OneDev changed state to 'Released' 11 months ago
|
||||
|
|
State changed as build #3693 is successful |
||||
|
Referenced from other issue 10 months ago
|
| Type |
New Feature
|
| Priority |
Normal
|
| Assignee |
In some case, i want create a temp access-token, and easy to distinguish and delete in the future.