SecureTunnel Command Line

That’s all. You can run the downloaded executable as it is. Depending on the security settings, the operating system may ask your permission to run it. Grant the permission.

In general case, you can start the tunnel from the BitBar website or on your computer (see Secure Tunnel Desktop App). Using the command-line utility implies that you start the tunnel from your computer. Open the command line window and enter the command like this:

SBSecureTunnel.exe --username "john.smith@example.com" --authkey aaabbbXXXXXNNNNccc --acceptAllCerts

Here, --username is your BitBar account (email address), and --authkey is your authentication key (also called API key). --acceptAllCerts commands the tunnel to accept security certificates. For detailed information on supported command-line parameters, see below.

After the tunnel is up and running, you can create or run your tests as you regularly do. For details, see the following links:

Live (or Manual) Testing

Automated Testing

Regardless of the way you started the tunnel, you can close it on the BitBar website: open the Secure Tunnel dialog box and click Disconnect.

Click the image to enlarge it.

You can also close the tunnel from the command line by using the --kill parameter. See below.

The utility supports special parameters to enable you to configure every aspect of tunnel functioning. The parameters can be organized into the following logical groups:

SBSecureTunnel.exe <required-params> <working-mode-params> <additional-params>

By using the SBSecureTunnel command-line utility, you can start SecureTunnel in various configurations. In every call, you should specify these parameters:

SBSecureTunnel.exe --username your-account --authkey auth-key

In most cases, you will run the utility with the following parameters:

SBSecureTunnel.exe --username your-account --authkey auth-key --acceptAllCerts

This call initiates the tunnel of the Internal Websites type with the the Accept all SSL certificates and Bypass tunnel for public URLs settings enabled (for more information on them, see Tunnel Settings).

Note that the Internal Websites mode is used by default and doesn’t require any command-line argument for activation. The same is with the Bypass … setting.

To run the tunnel in the Tunnel Settings mode, add the --proxyIp and --proxyPort parameters to the command line:

SBSecureTunnel.exe --username your-account --authkey auth-key --proxyIp ip-address --proxyPort proxy-port-number

Currently, BitBar doesn’t support this mode.

By default, the Bypass tunnel for public URLs setting is on and you don’t need to add anything to the command line to activate it.

If you need to disable the setting, add --bypass false to the command line:

SBSecureTunnel.exe --username your-account --authkey auth-key --bypass false

To enable the Accept all SSL certificates setting, add --acceptAllCerts to the command line. If this parameter is absent, the setting is off:

SBSecureTunnel.exe --username your-account --authkey auth-key --acceptAllCerts

--kill file-name

Commands the tunnel executable to monitor the specified file. Once the file appears, the tunnel executable shuts down. The file format and contents don’t matter. It can be an empty file. The SecureTunnel utility checks only the file presence. See also Using Tunnels in Automated Tests.

--ready file-name

Commands the tunnel executable to create the specified file after the tunnel connection has been set up successfully (the created file is empty). Your automation framework can check the presence of this file to determine if the tunnel is ready or not. See also Using Tunnels in Automated Tests.

--verbose

When this parameter is used in the command line, the SecureTunnel utility posts messages about its work to the command-line window. This diagnose issues when the tunnel fails to start. By default, the verbose mode is off.