-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Scopes for application tokens #4300
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
This would be pretty nice to have, especially for build authorizations. |
Are there any plans for this? I don't feel comfortable at all with giving every app full access to my Gitea account. |
what can we do to help for this ? |
Send a PR. :) |
All scopes support in one PR? you made me sincerely laugh ^^ , nevertheless, it would really be awesome to have the concept of Oauth Apps onto gitea,making it it a real social platform |
If I understand correctly, if I currently authorize an app it can use that oauth access_token to make a request to EDIT: nope, the |
bump...any updates? Or other pointers as to where the oidc jwt claims can be got via api? That way we can do our own management on users, teams and groups/role mappings. |
It's a sad show stopper for many use cases preventing the usage of Gitea altogether. |
Allow authentication tokens to be limited in scope. Maybe something like GitHub:
https://developer.github.com/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/
The text was updated successfully, but these errors were encountered: