![]() It runs on every subsequent login as well. There is no difference in Behaviour.ĮPA is configured as well but shows no issues. The users are only able to login via Gateway and use either Receiver for Web with app launch via local installed CWA/Receiver or HTML5-Receiver. If a session somehow persists a 5min, everything stays fine.Īctive ICA Connections stay open, no issue there. ![]() The drop to login does not happen on all sessions after 5min, but from my testing at least in 50% of the times. I could reproduce that, but there were no complaints about that yet. I can see that quite a bunch of users to try to authenticate multiple times, so there also might be an additional login loop issue (). I looked for an error on our SF-Servers for quite a time until i decided to reboot one of them.Īfter I disabled one of the SF Servers and tried to start a new app, the message about a required re-authentication appeared instead of a hard drop to login, so there is a difference.Īaad.debug shows nothing special, just new Login-Delegations to SF. They got dropped to login immediately without any Timeout Warning. This happens when trying to start new apps after about 5 Mins. We see Users getting dropped to Login after Upgrade to 13.0 85.19 on a pair of MDX 5550.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |