kylieolson

I have tested the possible work-around above, but unfortunately this did not work for me. It opened a blank windows PowerShell screen, while continuing the connection as usual. I am using Devolutions Gateway as well, so maybe that is why it still continues the connection?

My work around is having users check out the JIT credential from the PAM vault before opening the RDP connection, which gives it enough time to create the access, but it creates an extra step that is usually forgotten about.

Requesting/Sharing my idea for Check out policies to include check out options for accounts with JiT elevation. Instead of having a PAM account notify approvers for both a standard account, and the JiT, have the option to auto-approve if standard, or notify approvers if JiT is selected for the account.

Another idea is to allow choosing between different PAM accounts for connecting to RDP connections within RDM, instead of just one PAM account.

Thank you!