suse-coder

@florianduros Today one user of us had a sudden logout again (after he was already successfully logged in there was a sudden logout: due to "security reasons"). We use the...

Maybe a race condition?: Race between 1. Asynchronous IndexedDB writes (`clearStorage` → `persistCredentials` / `persistAccessTokenInStorage`). 2. Immediate URL cleanup (`history.replaceState` or full redirect). 3. Possible automatic SSO redirects that reload...

Please fix this as soon a possible as this is really making people badmouth element, even if its awesome.

Or is potentially just const params = parseQs(window.location); and window.history at some time overriding it wrong, so that code and state is again in it and it thinks it needs...

@florianduros @richvdh Here are new logs from today (it was where the win client element was already logged in and just logged out of nowhere) where one was forced logout:...

We only get that forced logout in Win Element Client (randomly). Mac Element Client had never that problem ever.

Random Logout could be related to this part: ``` // Wrapper around public method authedRequest to allow for tracking retry attempt counts private async doAuthedRequest( attempt: number, method: Method, path:...

``` const expiresIn = this.latestTokenRefreshExpiry.getTime() - Date.now(); if (expiresIn

I could verify that our keycloak has 60ms to 8s delays. New access token needs to be configurable (from ess helm chart) to have higher values. Maybe add a hint...

I could get more logs: @florianduros As on our mac clients we never had a issue. Could it be that the Win 11 "Credential Manager" which is when i am...