suse-coder

I see in the sso docs of matrix that one should set: ``` session_lifetime: maximum length of a session, even if it's refreshed. In other words, the client must log...

will try to set ``` experimental: access_token_ttl: 86400 ``` to a higher value (currently 24h)

I think it is hard coded currently for mas in the helm chart. So I guess that helm chart needs to get updated: https://github.com/element-hq/ess-helm/issues/615

@florianduros We had it today again from one client that a forced logout was done only on his win pc element client (not on his android). When I understand it...

@florianduros I see that in my logs above this network error: "rageshake.ts:69 FetchHttpApi: --> GET https://matrix-client.matrix.org/_matrix/client/unstable/org.matrix.msc2965/auth_metadata matrix-client.matrix.org/_matrix/client/unstable/org.matrix.msc2965/auth_metadata:1 Failed to load resource: net::ERR_NETWORK_CHANGED " Obviously if during the token refresh period...

On the other side if one changes the network then tcp retransmission no longer works: TCP only guarantees retransmission as long as the underlying connection remains valid and both endpoints...

You have to look in the console in the browser/client and had it open during that (as a logout is deleting all the old logs for security reasons)

We were able to figure the core reason more out. It is that our F5 VPN is leaky, so when the win pc starts all connections are blocked until the...

But why not make the refresh token be valid for a specific time instead be directly invalidated after one use? Having instable VPN connection is something Element has to handle...