Two Windows Mattermost client users consistently have to login to the Mattermost service on a daily basis with “session has expired” errors
Steps to reproduce
This is tricky as only two users out of 10 are experiencing this behavior. Windows Mattermost client 4.3.2 on Mattermost Server 5.17.1.
The users launch their Mattermost clients and are able to re-establish their sessions without needing to re-authenticate.
The bulk of the users, a mix of Windows 10 and MacOS, have no issue bringing up their Mattermost clients and the session re-establishing after being offline all night without needing to re-authenticate. However, two Windows 10 users have to re-authenticate each morning when launching the Mattermost client. The Mattermost Server is configured for session lengths of 180 days in all three configuration spots (AD/LDAP, Mobile, SSO). I think it might be a client issue more than a Server configuration issue as one of the two users who needs to re-authenticate also connect to multiple Mattermost servers and need to re-auth to ALL of them.
I have uninstalled and re-installed the Mattermost client, but I suspect perhaps there may be remaining stale configuration files/registry settings that are possibly lingering after the uninstall has been completed, which is why the behavior appears to be persisting between installs.
I’m just looking for some additional suggestions on things to try or other things that I could look for to ensure the client is fully uninstalled (assuming my hypothesis is valid). Thanks!