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
In short - we should be able to handle refreshing session ID automatically in case the ID expires.
Here is the scenario:
WaG client-side sends an AJAX request to KonText with X-Api-Token (= session ID generated using a private token)
KonText finds out that the session ID is expired and responses with 401 Unauthorized.
WaG client-side calls a special WaG server action refresh_session
The refresh_session action will call KonText's /token/authenticate (it means that the WaG server must have a secret token stored in its config) and obtains a new session ID from KonText
once WaG client-side gets a proper response, WaG will reload respective tiles (or the whole page in case this would be too cumbersome)
The text was updated successfully, but these errors were encountered:
In short - we should be able to handle refreshing session ID automatically in case the ID expires.
Here is the scenario:
401 Unauthorized
.refresh_session
refresh_session
action will call KonText's/token/authenticate
(it means that the WaG server must have a secret token stored in its config) and obtains a new session ID from KonTextThe text was updated successfully, but these errors were encountered: