Closed vst closed 2 years ago
@alioguzhan This is important.
Note that there are two aspects to this:
For the latter, this hook can be proactive as well: Check before hitting the API. But this is not sufficient as the real state of authentication information is only known by the authentication server.
Maybe we should implement all.
As per our discussion:
?next=hebelehubele&reason=session-expired
In this case, DECAF Waitress can show a notice on the login page:
Your session has expired. Please login again...
Currently, if the session is no longer valid, the app goes rogue and the user does not understand what's going wrong.
We need a machinery that is setup on
<DecafApp>
, tracks the validity of the session and takes action if it is not valid anymore. Possible actions:<DecafApp>
?