Troubleshooting PRA Inactivity Timeouts

PRA does not have its own dedicated timeout setting. PRA session timeouts are a downstream effect of other timeout configurations.

1. Platform Session Timeout:

   • Controls how long a user can be idle on the Platform UI, including browser tabs with active PRA remote connections

   • Configured in Identity Policies under Browser Session Parameters:

     • User Idle Timeout

     • Session Length

     • Keep Me Logged In

   • If the user has mouse/keyboard activity in any Platform or PRA tab, the idle timer resets

2. RDP Idle Timeout

   • Configured on the users' target host or their datacenter RDS services and not controlled by the Platform.

   • If a user is active on one PRA connection tab, a different PRA connection may still be timed out by its target host

   • PRA cannot override timeouts or other third-party controls enforced on the target server

Unintentional Logout When Using Microsoft Edge

Microsoft Edge has a built-in "sleeping tabs" features that put inactive tabs to sleep to conserve system resources. When users are working in their remote session browser tab, this feature can cause the tab showing the Platform WebUI (the tab from where the PRA remote session was launched) to "sleep". When this happens, the user is logged out from the Platform during their next refresh token validation cycle - in turn causing the user to be logged out of their PRA remote sessions.

Users should configure their Microsoft Edge browser settings with their Platform tenant URL to prevent the Platform tab from sleeping and causing unintended session logout.

See the following documentation to learn how to update Microsoft Edge settings.

Default behavior: Edge puts tabs to sleep after 1 hour of inactivity

Users should set the sleep time to be the maximum duration needed for their PRA remote sessions.