Our quality instance has 3 clients. When a user is in one QS instance client called 100 and logs out and then opens another URL in the same QS instance but different client called 200 the system logs them in like they are in the second URL client but they are still actually in the first client. If we clear the browser cache it corrects this issue. We are using Azure SSO to authenticate. We temporarily created a script for the user to run that clears their browser cache and then opens the URL but this is not a long term solution. Has anyone run across this and how have you resolved it?
The issue looks to be caused by browser cache and Azure SSO session persistence across clients; so to resolve it long-term, may configure SSO with client-specific logon parameters or use different subdomains per client to isolate sessions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.