This bug is still unsolved?
The ReturnUrl issue is resolved in ScreenConnect, version 6.1. The fix will be included in the forthcoming stable release of 6.1.
I tried this with the current release: 6.1.12292.6236
and it turns out, it is not fixed.
Still I am beeing sent after the timout and reauthentication to the useless "support" section instead to my last selected group/machine under Access.
I retested this on 6.1.12292 installed on a Windows 2008 R2 server with the Host.aspx MaxLongestTicketReissueIntervalSeconds web.config setting set to 120 and TicketReissueIntervalSeconds set to 600.
Using Chrome, I logged into the Access section of the Host page and selected a session group from the list. After approximately 2 minutes, I was automatically logged out of the Host page. When I reauthenticated, I was automatically returned to the last selected Access session group.
At this point, would you mind submitting details about the environment in which you observe this behavior, including the host's browser, server operating system, and current web.config values for Host.aspx MaxLongestTicketReissueIntervalSeconds and TicketReissueIntervalSeconds?
Host: Browser IE11 on Windows7 X64 or Safari 5.x on Macosx 10.6.8 or IE11 on Windows8 Pro
Server OS Windows Server 2008R2x64
Note: I have a second authentication enabled, After relogin an Email with a one time number is sent to my mobile.
Thank you for providing this information.
The behavior you describe is a result of the manner in which IE11 handles the RedirectUrl -- IE strips this information after the host enters their username and password on the Login page, clicks "Login", and is prompted to enter their one time password.
Since this is browser-specific, the workaround is to use Chrome, Firefox, or a more up-to-date version of Safari. I tested ReturnUrl functionality using the latest versions of Chrome and Firefox, and Safari version 9.0.1 -- each of these browsers correctly return the host to the last selected session group after logging back in.
before this bug appeared it worked in Safari 5.x and IE11. Now, it does still not work. For me that does not mean it is fixed. It is only fixed partially.
Customer support service by UserEcho