Manage tunnels

Tab: TUNNELS; read-only for SRF Testers

Use an SRF tunnel to test applications installed behind a corporate firewall. For more details, see Tunneling.

Configure a tunnel

  1. Click DOWNLOAD NEW TUNNEL to download a new tunneling utility instance for your operating system.

    The download includes the ftaas-tunnel utility application and the config.json configuration file.

  2. Configure your tunneling settings, either in the downloaded config.json file, directly in the command line when you run the utility, or in your machine's environment variables.

    For details, see Tunneling parameters.

    Note: We recommend working with a .json configuration file instead of command line parameters.

  3. Run the downloaded ftaas-tunnel utility to start your tunnel.

    Tip: Create a batch file to run the utility easily with pre-defined command line parameters.

    For example, use the following code to run an ftaas-tunnel utility in the same directory:

    ftaas-tunnel -config=config.json

Back to top

Manage your tunnels

Active tunnels are displayed on the SRFSettings > TUNNELS page. Click to stop a specific tunnel, or STOP ALL to stop all active tunnels.

Caution: Stopping a tunnel also stops all tests running on that tunnel.

Select the tunnel you want to use when running an automation test or exploratory session, or when recording or playing a script.

Back to top

Tunneling parameters

SRF enables you to define tunneling parameters in an external configuration file, directly in the command line, or using environment variables.

Note: Regardless of how you configure your tunnel, values for the server, client ID, and client secret are mandatory, as well as proxy values, if relevant for your environment.

All other parameters are optional.

For more details, see:

config.json configuration file

Create a config.json file to define settings centrally for all tunnels running on your machine.

Save the config.json file anywhere on your local machine, and then define its location in the command line when you run the tunneling utility.

Parameters defined in the command line override any values defined in the config.json file.

The following configuration parameters are available in the config.json file:

Name Definition
client

Your SRF client ID.

secret

Your SRF client secret.

server

The address of the tunneling server you are connected to.

One of the following:

  • AMS: wss://tunnel-ftaas.saas.hpe.com:443/opb
  • EMEA: wss://ftaas-tunnel-eu1.saas.hpe.com:443/opb
httpProxy

Defines the HTTP/HTTPS proxy for outbound connections, if the value differs from your existing machine environment variable.

  • Connect without authentication. Enter the proxy server URL and port as follows: http://<serverURL>:<port>
  • Connect with basic authentication. Add your username and password to the value, as follows: http://<user>:<password>@<serverURL>:<port>

For more details, see Environment variables.

noProxy

A comma-separated list of hosts to connect to directly, instead of using a proxy.

For example:

google.com,yahoo.com

hosts

Defines specific hosts to be exposed by the tunnel.

log

Defines where the log output is saved:

  • stdout. Log to the terminal (view in your command window)
  • none. No log output.
  • <Specific file path>. The specified file path.
logLevel

The message level to log:

  • DEBUG
  • INFO
  • WARNING
  • ERROR
name

The name of your tunnel. Leave this blank to use your machine name as default.

Note: SRF does not support multiple tunnels with the same name.

selfSigned

String. List of self-signed hosts, contained in square brackets, for which SRF ignores certificate verification. Separate multiple entries by commas.

If allowed hosts are defined on your machine, this value must be a subset of those defined hosts.

If you use this parameter, your certificate will be listed as issued by SRF Certificate.

For example:

{

"httpProxy": "http://proxy.mycorp.net:8080" ,

"server": "wss://ftaas-tunnel-eu1.saas.hpe.com:443/opb" ,

"client": "<placeholder>" ,

"secret": "<placeholder>" ,

"name": "Tunnel107",

"selfSigned": ["136.0.3.5.22:3332" "yourHost.com"]

"hosts": []

}

Command line parameters

Add parameters to the command line when you run the ftaas-tunnel tunneling utility.

If you have defined any of these values as environment variables or in a config.json file, they are overridden by the values in the command line.

Note: We recommend working with a .json configuration file instead of command line parameters. For details, see config.json configuration file.

The following configuration parameters are available for the command line:

Name Definition
config

A path to your config.json file.

client

Your SRF client ID.

secret

Your SRF client secret.

server

The address of the tunneling server you are connected to.

One of the following:

  • AMS: wss://tunnel-ftaas.saas.hpe.com:443/opb
  • EMEA: wss://ftaas-tunnel-eu1.saas.hpe.com:443/opb
insecure-skip-certificate-verify

Skips server certificate validation when starting the tunnel.

Note: This parameter is supported only in the command line, and not in a config.json file.

http-proxy

Defines the HTTP/HTTPS proxy for outbound connections, if the value differs from your existing machine environment variable.

For details, see Environment variables.

no-proxy

A comma-separated list of hosts to connect to directly, instead of using a proxy.

For example:

"*google.com","yahoo.com:*"

hosts

Defines specific hosts to be exposed by the tunnel.

log

Defines where the log output is saved:

  • stdout. Log to the terminal (view in your command window)
  • none. No log output.
  • <Specific file path>. The specified file path.

log-level

The message level to log:

  • DEBUG
  • INFO
  • WARNING
  • ERROR

name

The name of your tunnel. Leave this blank to use your machine name as default.

Note: SRF does not support multiple tunnels with the same name.

self-signed

String. List of self-signed hosts for which SRF ignores certificate verification.

If allowed hosts are defined on your machine, this must be a subset of those defined hosts.

Define multiple hosts separately, using wildcards as needed.

For exampleftaas-tunnel.exe -self-signed *.internal.mydomain.com -self-signed internal2.mydomain.com

Note: If you use this parameter, your certificate will be listed as issued by SRF Certificate.

Environment variables

If possible, use the existing http_proxy environment variable defined on your machine for outbound HTTP/HTTPS proxy connections.

If you need to use a different value for your SRF tunnels, configure this value in a config.json file or in the command line.

Back to top

See also: