-
-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Open
Labels
type/enhancementAn improvement of existing functionalityAn improvement of existing functionalitytype/proposalThe new feature has not been accepted yet but needs to be discussed first.The new feature has not been accepted yet but needs to be discussed first.
Description
Feature Description
The token created via gitea admin create user --access-token
is effectively useless without providing some minimal scope options. The generated scopeless access token, as expected, always results in a 403 with "token does not have required scope" messages via REST API. There's no way to change the scope afterward either.
Without the ability to provide scopes the --access-token features is completely useless.
Screenshots
This shows the current token scopes (none) as the feature stands without having the option to specify scopes. Another option is from my comment below where all powers are granted to the access token generated for admins from the CLI.
delvh, krzkaczor, oyvindkolbu and joshes
Metadata
Metadata
Assignees
Labels
type/enhancementAn improvement of existing functionalityAn improvement of existing functionalitytype/proposalThe new feature has not been accepted yet but needs to be discussed first.The new feature has not been accepted yet but needs to be discussed first.