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
Everything appears to work fine for me
I can login, logout - stay logged in etc.
I have an issue with another user's computer.
When see installs the App, it always sees her as having a cached token.
It's always the wrong token - token from another tenant.
I added her user from the other tenant as a guest user in our AD and it works fine, however, she can never logout.
She is running Windows 10 and using AzureAD to login.
I must be doing something wrong somewhere.
My machine is also Windows 10 and also authenticating to yet another AzureAD tenant.
I'm struggling to understand why mine is working and hers not?
I appreciate I haven't given you much to go on.
Happy to supply any additional info.
The Azure AD configuration is set to only users in my Org - which is what we want.
The expected behavior would be that when the token is seen as invalid, she is prompted to login.
Any thoughts?
Kind Regards
Rich
The text was updated successfully, but these errors were encountered:
Try this with an private browser session . If you are using Windows 10 and its a domain joined machine, then the browser could be set to log you in in an accelerated mode (i.e. without bothering to ask for login name.
Everything appears to work fine for me
I can login, logout - stay logged in etc.
I have an issue with another user's computer.
When see installs the App, it always sees her as having a cached token.
It's always the wrong token - token from another tenant.
I added her user from the other tenant as a guest user in our AD and it works fine, however, she can never logout.
She is running Windows 10 and using AzureAD to login.
I must be doing something wrong somewhere.
My machine is also Windows 10 and also authenticating to yet another AzureAD tenant.
I'm struggling to understand why mine is working and hers not?
I appreciate I haven't given you much to go on.
Happy to supply any additional info.
The Azure AD configuration is set to only users in my Org - which is what we want.
The expected behavior would be that when the token is seen as invalid, she is prompted to login.
Any thoughts?
Kind Regards
Rich
The text was updated successfully, but these errors were encountered: