Where does Cup keep Apple's refresh token, and when does it revoke it?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- authentication, backend
Research direction
Start by tracing where native and web Apple authorization codes enter the application, then follow the component that exchanges them and stores refresh tokens. Read the account deletion coordinator’s retry and stuck deletion reporting paths to understand how revocation should fit scheduling, erasure, recovery, and unlinking. Done means documenting or implementing the intended revocation behavior for each listed case, including identities that were never provisioned.
Written by the indexing model from the issue text.
Description
Question
Where does Cup capture Apple's authorization code (native and web), which component exchanges it, where the refresh token is kept and how it is protected, and when it is revoked: on account deletion scheduling, at account erasure, on recovery, and for an identity unlinked or never provisioned. How does revocation fit the deletion coordinator's retries and its stuck account deletion reporting?
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from patricktree/cup
-
wayfinder:grilling
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
patricktree/cup#484 ·
-
wayfinder:grilling
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
patricktree/cup#487 ·
-
wayfinder:grilling
Difficulty 5/5 Over a week Newbie friendliness 25/100
patricktree/cup#486 ·
-
wayfinder:grilling
Difficulty 5/5 Over a week Newbie friendliness 25/100
patricktree/cup#485 ·
-
wayfinder:grilling
Difficulty 5/5 Over a week Newbie friendliness 25/100
patricktree/cup#483 ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vercel-labs/ui#865 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
outline/outline#14638 · 1 comment ·
Maintainers usually reply within 1 day
-
bot:ai-assisted component:platform-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
midnightntwrk/platform-js#69 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day