optim(auth): improve access token refresh times #12
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: researchequals/frontend#12
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?
Upon implementation, it looks like refreshing the access token takes a matter of seconds - 3-8 seconds or so. This currently does not have a loading state, which makes it feel off.
We do implement pro-active refresh, but currently that is not in the background - it becomes manifest on the client as well. This issue tracks the need for optimizing the access token refresh procedure. Evidence/testimony on the topic is also welcome here.