-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Redirect to GitHub auth flow if token is invalid #10053
Copy link
Copy link
Open
Labels
area:agentAgent workflows, conversations, prompts, cloud mode, and AI-specific UI.Agent workflows, conversations, prompts, cloud mode, and AI-specific UI.area:authAuthentication, login, SSO, session management, and account security.Authentication, login, SSO, session management, and account security.bugSomething isn't working.Something isn't working.repro:mediumThe report suggests a plausible repro path, but some uncertainty remains.The report suggests a plausible repro path, but some uncertainty remains.triagedIssue has received an initial automated triage pass.Issue has received an initial automated triage pass.warp:prioritizedIssues prioritized by the Warp team.Issues prioritized by the Warp team.
Description
Metadata
Metadata
Assignees
Labels
area:agentAgent workflows, conversations, prompts, cloud mode, and AI-specific UI.Agent workflows, conversations, prompts, cloud mode, and AI-specific UI.area:authAuthentication, login, SSO, session management, and account security.Authentication, login, SSO, session management, and account security.bugSomething isn't working.Something isn't working.repro:mediumThe report suggests a plausible repro path, but some uncertainty remains.The report suggests a plausible repro path, but some uncertainty remains.triagedIssue has received an initial automated triage pass.Issue has received an initial automated triage pass.warp:prioritizedIssues prioritized by the Warp team.Issues prioritized by the Warp team.
If a GitHub token is invalid, we should route the user back through the auth flow.
If a user previously revoked Warp's access from their GitHub account, the OAuth token stored on our side may be invalid or expired. However, the GitHub integration record still exists on the account. The system tries to use the stale token instead of prompting for a fresh GitHub OAuth authorization, causing a "Failed to load github repos: missing response data" error.
The fix should clear or invalidate the existing GitHub OAuth integration record and prompt the user to go through the full GitHub authorization flow again.
Linear: REMOTE-1026