Okta Advanced Server Access and Privileged Access Webpage Fails to Launch the ScaleFT Client
Last Updated:
Overview
When a user clicks the Connect button in Okta Advanced Server Access (ASA) or Okta Privileged Access (OPA), the ScaleFT (SFT) client fails to launch if the system lacks the required registry values. Registering the URL handler creates the necessary registry entries and resolves the issue. The browser requires these registry values to pass connection information to the SFT client.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Okta Advanced Server Access (ASA)
- Okta Privileged Access (OPA)
- ScaleFT-client-tools
Cause
The system registry lacks the required values to instruct the browser on how to launch the ScaleFT client.
Solution
How is the ScaleFT URL handler registered?
Execute the ScaleFT URL handler registration command and verify the resulting registry entries in the Windows Registry Editor based on the installation type.
- Run the following command to update or create the two required registry entries:
-
sft register-url-handler
-
- Open the Windows Registry Editor and navigate to the following paths to verify the entries:
-
Computer\HKEY_CLASSES_ROOT\scaleft -
Computer\HKEY_CLASSES_ROOT\ScaleFTProtocolHandler
-
NOTE: The registry path that calls ScaleFT.exe depends on whether the client installation applies to a single user or all users.
Single-User Installations Require Specific Registry Entries
Review the following images to verify the correct registry configuration for a single-user installation.
All-User Installations Require Specific Registry Entries
Review the following image to verify the correct registry configuration for an all-user installation.
