Skip to main content
Apprentice
July 2, 2026
Question

PRA Session Termination Behavior Not Working as Expected

  • July 2, 2026
  • 3 replies
  • 64 views

Hi,

We are experiencing an issue with the session termination behavior in PRA.

We have configured the system so that when a session ends, the user's session on the target server should be logged off automatically. However, after ending a session and reconnecting, everything remains exactly as it was left previously, which indicates that the user session is not actually being logged off.

Both the web console and the desktop console are running version 25.3.2.

We found a KB article that appears to describe a similar issue, but it does not seem to apply to the version we are currently running.

Additionally, we are currently applying the Session Policy through Group Policies. To rule out a policy inheritance issue, we also assigned the same Session Policy directly to the Jump Item, but the behavior remained exactly the same.

If anyone has experienced a similar issue or knows why this might be happening, we would really appreciate any guidance or suggestions on what else we should verify.

Thank you in advance for your assistance.

Best regards,

Kevin

3 replies

BeyondTrust Employee
July 2, 2026

Hello ​@kmazzini  - can you confirm what type of session this is? Jump Client, RDP, SSH, etc? Also, in the Rep Console itself, in the lower right hand corner of the Session Window, can you confirm what the ‘’Post Session Action option is during these sessions?

kmazziniAuthor
Apprentice
July 2, 2026

Hello ​@kmazzini  - can you confirm what type of session this is? Jump Client, RDP, SSH, etc? Also, in the Rep Console itself, in the lower right hand corner of the Session Window, can you confirm what the ‘’Post Session Action option is during these sessions?

Hi Phill, thanks for your reply.

It's an RDP session to a Windows machine via Jumpoint. I don't see the text you mentioned in the lower-right corner.

Trailblazer
August 14, 2026

Hello ​@kmazzini , without jump client session you cannot achieve this from PRA. else AD group policy should be able to do that if you do not wish to install jump clients on the server(s).