Back-end logout flow
Nobody has claimed this yet.
- #198 by @collinpreston — closed without merging
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 4
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 114
Description
User Story
The process flow for Keycloak's OpenID Connect logout flow should follow the process flow here: https://docs.google.com/document/d/17tJ-C2EwWoSpJWZKjuhMVgsqGtyPH0IN9KakXvSKU0M/edit#heading=h.qr1x27po61aq
Description/Context
https://www.keycloak.org/docs/latest/server_admin/#backchannel-logout
https://github.com/mitodl/hq/discussions/2817
Acceptance Criteria
- When a user logs out of Keycloak, any MIT Open session associated with the user on the same device should be terminated.
Contributor guide
No contributing guide indexed for this repository
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 with the linked Google process flow, Keycloak backchannel-logout documentation, and discussion #2817; no repository file or test is named in the issue. Trace the existing Keycloak logout handling and identify how sessions are associated with a user and device. Done means logging out of Keycloak terminates the associated MIT Open session on the same device.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100