optim(auth): improve access token refresh times #12

Closed
opened 2025-09-26 12:29:27 +00:00 by chartgerink · 1 comment
Owner

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.

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.
Author
Owner

Closing this as it is an api issue - see researchequals/api#102

Closing this as it is an api issue - see https://git.libscie.org/researchequals/api/issues/102
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
researchequals/frontend#12
No description provided.