The Wayback Machine - https://web.archive.org/web/20230225155243/https://github.com/go-gitea/gitea/issues/19079
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

Narrowly-scoped Authentication Tokens #19079

Closed
chmac opened this issue Mar 14, 2022 · 1 comment
Closed

Narrowly-scoped Authentication Tokens #19079

chmac opened this issue Mar 14, 2022 · 1 comment

Comments

@chmac
Copy link

chmac commented Mar 14, 2022

Feature Description

Similar to #18374 I'd like to see the same for access tokens. When I add a new access token, I'd like to be able to choose which repositories it is allowed to access, and preferably, whether the token should have read-only or read-write access to each repository.

I'd love to see the following options available for newly created access tokens:

  • Token is valid for:
    • All repositories the user can access
    • Select specific repositories
  • Token allows:
    • Pull only access
    • Pull and push access

If it makes the implementation easier, it would also be totally acceptable to have the tokens created on the repository itself instead of per user, similarly to Deploy Keys. So a user can create a personal access token for a specific repository.

There are places where I put tokens, unencrypted, because they need to push to a single repo on my gitea install. In that situation, I have to create new users to be able to limit the token to only be valid for a single repository. It would be great if there was an easier option.

Thanks for gitea, it really makes self hosting git painless and joyful. Y'all rock. 🧡

Screenshots

GitHub has a whole host of options, which I think would be overkill for gitea.

image

@qwerty287
Copy link
Contributor

Duplicate of #4300?

@go-gitea go-gitea locked and limited conversation to collaborators Apr 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

4 participants