URL Handler

The URL handler for the Access Interface follows a specific format that allows you to circumvent using memorable names or identifiers for your URLs. These machine-generated URLs are found in daily interfaces such as dashboards, ticking and monitoring systems, and logs.

Setup

Use the following template to setup your URL Handler:

scaleft://[<sft-username>@]<instance>/t/<team>/a/<target>/<access-method>?via=[<username>@]<bastion>

Note: All information within [brackets] is optional.

Parameters

Examples

The following lines are examples of a URL Handler:

  • scaleft://app.scaleft.com/t/okta-demo-only/a/ubuntu-target/ssh
  • scaleft://app.scaleft.com/t/okta-demo-only/a/ubuntu-target/ssh?via=ubuntu-bastion

Check for correct URL handling

The Advanced Server Access clientEssentially, a client is anything that talks to the Okta service. Within the traditional client-server model, Okta is the server. The client might be an agent, an Okta mobile app, or a browser plugin. logs clicks and the handling of the URL.

If you are on a Windows machine, the client logs are located in c:\users\<username>\appdata\local\scaleft\logs.

If you are using a Mac: the files are located in ~/Library/Logs/ScaleFT/sft/.

Top