You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I guess it's not a bad idea to do this. We can produce an error message that will be much clearer about what is going on and what to do (e.g. we can provide instructions in the error message w/ a link / how to renew).
When to do this though?
a. Proactively
We can check on every request, not just errors, and if it's going to expire soon, produce a warning with a lot of the same details. Perhaps we can set a config variable for how long before expiration we should warn. Maybe 2 weeks? Disadvantage is that this slows down the request cycle.
b. Reactively
Check only during exception handling. Advantage is that it won't slow down request cycle by doing a proactive check.
Overview
Check token validity early and often.
Sub-tasks
Additional details
Here's how:
That last number is time-to-live in seconds.
I'm not sure where to run these checks. When the time is getting close, we need to ask Mariam Deacy to generate a new one for us.
The text was updated successfully, but these errors were encountered: