Document revocation flow
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1k
- Forks
- 165
- PR merge metrics
- No merged PRs in 30d
Description
Expected Behavior
[REQUIRED] Describe expected behavior
There should be clear instructions on how to revoke a token.
Describe the problem
There's no mention of token revocation in the readme and the electron demo just disposes of the tokens in memory but does not revoke the token
[REQUIRED] Actual Behavior
Sign out in electron demo should revoke tokens
[REQUIRED] Steps to reproduce the behavior
N/A
[REQUIRED] Environment
- AppAuth-JS version: current
- AppAuth-JS Environment (Node, Browser (UserAgent), ...): N/A
- Source code snippts (inline or JSBin)
NOTE: there is mention of revocation in https://github.com/openid/AppAuth-JS/issues/71
Contributor guide
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.
Research direction
Start by reading the README and the Electron demo's sign-out flow, then review the revocation discussion in issue 71. Done means the README explains token revocation and signing out in the Electron demo revokes tokens rather than only disposing of them in memory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, typescript
- Domain
- authentication, desktop, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100