Skip to content

Scopes for application tokens #4300

@aunger

Description

@aunger
Contributor

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/

screenshot_2018-06-22-06-41-29

Activity

added
type/featureCompletely new functionality. Can only be merged if feature freeze is not active.
on Jun 23, 2018
stale

stale commented on Jan 22, 2019

@stale

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.

added
issue/confirmedIssue has been reviewed and confirmed to be present or accepted to be implemented
and removed on Feb 6, 2019
randomchance

randomchance commented on Jan 9, 2020

@randomchance

This would be pretty nice to have, especially for build authorizations.

mpfaff

mpfaff commented on May 3, 2020

@mpfaff

Are there any plans for this? I don't feel comfortable at all with giving every app full access to my Gitea account.

mcansky

mcansky commented on May 7, 2020

@mcansky

what can we do to help for this ?

lunny

lunny commented on May 7, 2020

@lunny
Member

Send a PR. :)

Jean-Baptiste-Lasselle

Jean-Baptiste-Lasselle commented on Nov 18, 2020

@Jean-Baptiste-Lasselle

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

Coding-Kiwi

Coding-Kiwi commented on Jan 4, 2021

@Coding-Kiwi

If I understand correctly, if I currently authorize an app it can use that oauth access_token to make a request to /users/{username}/tokens to generate an unlimited, non-expiring access token which then renders the whole oauth expiry/refresh logic useless.

EDIT: nope, the /users/{username}/tokens requires basic auth. Scopes would be awesome nontheless

Morriz

Morriz commented on Apr 26, 2022

@Morriz

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.

cayolblake

cayolblake commented on Oct 8, 2022

@cayolblake
  • bump

It's a sad show stopper for many use cases preventing the usage of Gitea altogether.

locked and limited conversation to collaborators on May 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    issue/confirmedIssue has been reviewed and confirmed to be present or accepted to be implementedtype/featureCompletely new functionality. Can only be merged if feature freeze is not active.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      Participants

      @lunny@mcansky@Morriz@randomchance@aunger

      Issue actions

        Scopes for application tokens · Issue #4300 · go-gitea/gitea