mirror of
https://github.com/EddieTheCubeHead/Stagnum.git
synced 2026-04-26 22:25:52 +03:00
[GH-ISSUE #93] Design a flow for refreshing auth token #67
Labels
No labels
bug
bug
client
design
documentation
feature
feature
infrastructure
pull-request
ready for development
server
server
spike
technical work
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Stagnum#67
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @EddieTheCubeHead on GitHub (Feb 23, 2024).
Original GitHub issue: https://github.com/EddieTheCubeHead/Stagnum/issues/93
Decide how the communication between UI and core happens concerning auth token refresh; Who is responsible? How is it communicated?
Acceptance criteria: Necessary tickets for implementing auth token refresh are created.
@EddieTheCubeHead commented on GitHub (Apr 6, 2024):
Ticket: #197