Where does Cup keep Apple's refresh token, and when does it revoke it?

Open
#478 0 comments 0 reactions 0 assignees View on GitHub

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

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

wayfinder:grilling

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from patricktree/cup

All issues in patricktree/cup

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.