Describe the bug
So, this happens to some users in world wide local network. At first we thought it is a problem in network itself but then accidentally we discovered something strange. If user after clicking login button activates native Windows screenshot tool, browser frizzes before redirection (to allows taking a screenshot) and then redirecting to application returns with logged in status. Otherwise in normal flow user stays logged out. I have no idea what can go wrong here and why only for these users it works this way. It is like something happens too fast for these cases and library is not able to catch logged in status from authentication server. I am curious if there is some timeout settings on library side I can use to prevent this to happen. Does something need to be done on server side? Any advice how to overcome this situation will be appreciated.
Desktop (please complete the following information):
OS: Windows
Browser Chrome and Edge (no other browsers allowed by administartors)
Describe the bug So, this happens to some users in world wide local network. At first we thought it is a problem in network itself but then accidentally we discovered something strange. If user after clicking login button activates native Windows screenshot tool, browser frizzes before redirection (to allows taking a screenshot) and then redirecting to application returns with logged in status. Otherwise in normal flow user stays logged out. I have no idea what can go wrong here and why only for these users it works this way. It is like something happens too fast for these cases and library is not able to catch logged in status from authentication server. I am curious if there is some timeout settings on library side I can use to prevent this to happen. Does something need to be done on server side? Any advice how to overcome this situation will be appreciated.
Desktop (please complete the following information):