Bug ID 580512: Sometimes launching RemoteApps from APM webtop fails after logout/login

Last Modified: May 29, 2024

Affected Product(s):
BIG-IP APM(all modules)

Fixed In:
13.0.0

Opened: Mar 14, 2016

Severity: 3-Major

Symptoms

Due to the RemoteApp session termination logic employed by Microsoft and described in https://blogs.msdn.microsoft.com/rds/2007/09/27/terminal-services-remoteapp-session-termination-logic/ , it may happen that, if user logs out and then logs back in to the APM webtop, the subsequent attempts to launch RemoteApps would fail. This happens because of a bug in RDP client 8.1 that attempts to utilize the old authentication token although a new one is provided in the .rdp file.

Impact

Apps are not launched without any further notification.

Conditions

User logs in to APM webtop, launches some RemoteApp, closes its window, logs out, logs in again and attempts to launch the same app or another app hosted at the same backend.

Workaround

None

Fix Information

The fix has been implemented to make RDP client fail immediately on an attempt to use a wrong (expired) auth token. With this fix, it may only happen once to a user that RemoteApp launch would fail and an error will be shown immediately. The subsequent launches will succeed.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips