Goal
Complete the OAuth 2.0 Device Authorization Flow (RFC 8628) by implementing the redirect flow after user authorization.
Current State
- Device code endpoint (
/auth/v1/oauth/device_authorize) works ✅
- Token endpoint (
/auth/v1/oauth/token) with polling works ✅
- Verification page exists at
/auth/v1/oauth/device ✅
- User can submit user code and authorize ✅
Missing
After the user authorizes the device code, the verification page needs to:
- Show success message - "Authorization complete! You can close this page and return to the CLI."
- Auto-close (optional) - Use JavaScript to close the window after showing success
- Handle errors gracefully - Show clear messages for expired/denied codes
Reference
Acceptance Criteria
Goal
Complete the OAuth 2.0 Device Authorization Flow (RFC 8628) by implementing the redirect flow after user authorization.
Current State
/auth/v1/oauth/device_authorize) works ✅/auth/v1/oauth/token) with polling works ✅/auth/v1/oauth/device✅Missing
After the user authorizes the device code, the verification page needs to:
Reference
feature/oauth-device-authorization-flowAcceptance Criteria