Okta Advanced Server Access and Okta Privileged Access Fail to Detect WinSCP Installed for Users-Only Installations
Last Updated:
Overview
Okta Advanced Server Access (ASA) and Okta Privileged Access (OPA) fail to detect WinSCP when installed in user-only mode because the client tools only search specific directories. Resolve this issue by reinstalling WinSCP using a custom installation path that the client tools support.
The sft winscp <servername> command fails with the following error:
error: Failed to find WinSCP.exe. Tried: []string{"C:\Program Files\WinSCP\WinSCP.exe", "C:\Program Files (x86)\WinSCP\WinSCP.exe", "C:\Users\<username>\AppData\Local\Apps\WinSCP\WinSCP.exe"}
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Okta Advanced Server Access (ASA)
- Okta Privileged Access (OPA)
- WinSCP
Cause
The sft winscp client tools only detect WinSCP installations in three specific directories. The default user-only installation mode installs WinSCP to C:\Users\<username>\AppData\Local\Programs\WinSCP\WinSCP.exe, which the client tools fail to search.
Solution
How is the failed to find WinSCP error resolved?
Resolve the detection error by reinstalling WinSCP and selecting a custom installation path supported by the client tools by following these steps.
- Reinstall WinSCP and select the custom installation option.
- Specify one of the following supported installation paths during the setup process:
C:\Program Files\C:\Program Files (x86)\C:\Users\<username>\AppData\Local\Apps\
