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.
Use the following template to setup your URL Handler:
Note: All information within [brackets] is optional.
http://appAn abbreviation of application. Essentially, it is a web-based site used to perform any number of specific tasks, and requires authentication from end users by signing in..scaleft.com|app.scaleft.com.
viasection of the URL is optional and is only needed if there is no established preconfigured bastion configuration which is not required for most use cases. If there are multiple bastion configurations in the URL, multiple via parameters are required and must be in the correct order.
<target>, use any valid URL.
The following lines are examples of a URL Handler:
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
If you are using a Mac: the files are located in