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

Improved control over Personal Access Tokens (PATs) #184

Open
github-product-roadmap opened this issue Apr 7, 2021 · 0 comments
Open

Improved control over Personal Access Tokens (PATs) #184

github-product-roadmap opened this issue Apr 7, 2021 · 0 comments

Comments

@github-product-roadmap
Copy link
Collaborator

@github-product-roadmap github-product-roadmap commented Apr 7, 2021

Summary

Personal Access Tokens, or PATs, provide users a quick way to create OAuth access tokens with they can use to make API calls. The tokens allow users to specify scopes to determine what the token can access. This is a typical way of getting API keys in other SaaS products. However, PATs only have broad scopes (e.g. repos or orgs), which grant access to anything the user can access (i.e. specific repos or orgs cannot be specified). This improvement will introduce a new version of PATs which provide users with the ability to scope access to specific repos and orgs, set fine-grained permissions across specific features, and set expiration dates for each token.

Intended Outcome

Allow users to create PATs with improved security and access controls.

How will it work?

Once introduced, GitHub will provide UI and tools for creating new PATS and migrating existing PATs to the new version. This new version of PATs will support the following:

  • Scoping access to specific repos and orgs
  • Fine-grained permissions across specific features
  • Expiration dates for each token
@github github locked and limited conversation to collaborators Apr 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant