github / github/roadmap

OAuth apps can opt in to token expiration and refresh [Public Preview]

Open
#1,305 1 comment 0 reactions 0 assignees View on GitHub
Copilot Enterprise Copilot for Business Copilot for Individuals Enterprise Free GHES 3.23 Shipped Team
Dominant language
No language data
Stars
8.9k
Forks
1.8k
PR merge metrics
No merged PRs in 30d

Description

### Value Prop
OAuth apps can now perform token rotation using short-lived access tokens and refresh tokens, giving developers a straightforward way to meet security standards and eliminating a source of long-lived tokens. This feature is opt-in for existing OAuth apps and on by default for newly created ones, so app developers can test and roll it out safely.

### Expected Outcome
Rotating OAuth tokens regularly limits the window of exposure if a token is ever compromised — any previously exfiltrated token becomes invalid upon rotation. They also expire after 8 hours, the same as GitHub App user tokens. Developers building OAuth apps will be able to satisfy security policies that require credential rotation.

Contributor guide

Open the contributing guide

Research direction

This is a GitHub public-roadmap feature proposal and names no repository files, tests, or implementation entry point. Start by reviewing the OAuth app token-rotation requirements in the issue; done means existing apps can opt in, new apps default to it, access tokens expire after 8 hours, and refresh-token rotation invalidates prior tokens.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
authentication
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.