Custom Launchers

In addition to the built in PuTTY and Remote Desktop launchers, Secret Server supports custom launchers. You can customize these process launchers to work with any application that can be started by command-line. Custom launchers pass values to the command-line from the secret text fields. For process launchers to work, the client machine needs to have the program installed and typically needs the program folder in the PATH environment variable.

For more information on launcher arguments see Custom Launcher Process Arguments.

Like the built in launchers, custom launchers run on the users machine not on the web server. Launcher Processes can be set to run either using the credentials of the logged in user or the credentials of the secret. The "Run Process as Secret Credentials" check box is used to switch between theses two options.

There are four types of custom launchers to choose from:

  • Process: Launches the process on the user's machine and replaces $ parameters with values from the Secret and its associated Secret.

  • Proxied SSH Process: Launches the specified SSH client on the user's machine. This prevents Secret credentials from being passed to the client by connecting to Secret Server's proxy to interact with the remote host. When the SSH Proxy Server is running, launched SSH sessions are proxied through the server.

  • Batch File: Launches the indicated batch file on the user's machine. Allows the script to launch multiple processes using information from the server.

  • Session Connector Launcher: Not used for this task. Allows for downloading and running an RDP file to launch into a Remote Desktop Server with protocol handler installed, so end-user client machines do not need to install anything. Recommended only for advanced users.

See Configuring SSH Proxies for Launchers.