Product

Okta Privileged Access (OPA)

Issue details

Unable to open RDP/SSH sessions from Okta Privileged Access

Possible Cause(s)

Okta Privileged Access(OPA) is not able to identify the OPA Client on the user machine. OPA Client must be registered before opening RDP/SSH sessions from OPA

Solution/Fix

Need to follow below steps to solve the issue

• Open Command Prompt on the machine where Okta Privileged Access (OPA) Client is installed.
• Go to C:\Users\uid\Appdata\Local\ScaleFT\bin
• Run command sft register-url-handler and ensure the commands completes without any errors
• Login to Okta Privileged Access – 
• Under My Privileged Access -> Servers
• Click the server to which RDP or SSH session is to be opened.
• Under Accounts -> Click Connect
• A confirmation window opens for the user to consent to Okta opening RDP/SSH session via ScaleFT

Workaround

NA

Reference

How the ASA/OPA Webpage Launches SFT

Author

Ketaki Mujumdar