Skip to main content

Check out Interactive Visual Stories to gain hands-on experience with the SSE product features. Click here.

Skyhigh Security

Deploy Secure app connector V2 on VMWare vCenter using OVA for TCP Applications

icons.png  Watch the visual story about Deploying V2 OVA on VMWare VCenter

NOTE: Make sure to allow the following domains and HTTP(S) ports when you are using a firewall, For more details, see  Secure App Connector V2 Prerequisites and Firewall settings For Private Applications


  • Skyhigh Security recommends Secure App Connector have at least 4CPU8GB RAM, and 50GB HDD.

Steps to Deploy 

  1. Download the latest OVF package. For information about how to download, see Download Secure App Connector V2.
  2. Connect to a VCenter Server with the vSphere Web Client and log in.

MicrosoftTeams-image (48).png

  1. On the home page, select VMs and Templates.

Step 2_1.png

  1. Select Deploy OVF template to start deploying OVF.

Step 3.png

  1. In the Select an OVF template window, make sure you select the Local file option and browse to the location of the OVF template from the local system and click Next.

Step 4.png

  1. Name a virtual machine and select a storage location for the same and click NEXT.

Step 5.png

  1. Select a compute resource and click NEXT.

Step 6.png

  1. Review the package details which contain advanced configuration options, and then click Next.

NOTE: The warning shown can be ignored as it's the default warning that VCenter triggers while implementing custom configuration.

Step 8.png

  1. Read and accept all the terms of the license agreement and click NEXT

Step 9.png

  1. Select Thin Provision as the virtual disk format for the configuration, and click NEXT.

Step 10.png

  1. Configure the IP allocation network setting and click NEXT.
  • Select DHCP if DHCP service is available in your environment.
  • Select Static - Manual If DHCP service is not available in your environment.
  • The host should be able to connect to private applications that will be configured for this connector.
  • Do not select IP Pool in IP allocation.

Step 11.png

  1. Refer to the following steps to get the config file. For more details, see Configure Secure App Connector V2

IMPORTANT: The config file is a mandatory input for installation. 

 Screenshot (316).png

  1. Configure Network Settings, Proxy Settings, and Private Access Settings and click Next.
    • <PROXY>: Address of the proxy server (optional)
    • <Bypass Proxy> :  List of domains that can be added to bypass the proxy (optional). This parameter can be ignored if you don't have any domains that need to bypass the proxy, even when a proxy is used
  • Set the <PROXY> and <BYPASS_PROXY> parameters only when your connector uses a proxy server to reach the Internet.
  • No configuration settings are added to IP, DNS & Gateway if DHCP is selected.
  • All the connectors are setup with the default hostname out of the box. Changing it would affect connector functionality. If DNS auto-registration is enabled in the VMWare host, we recommend you to add another entry for this host with the desired DNS name.

After downloading the config file, paste the connector configuration content from SSE to vCenter UI. 

IMPORTANT:  Ensure config file contents are properly pasted in the Connector Configuration textbox. If any character is missing while adding it, the installation will fail.

NOTE: Ensure you follow this format: <URI Schema>://<Proxy-hostname>:<Proxy-port>. If this format isn't followed, installation will fail for a proxy. Only one proxy is supported for a connector.
Eg: or

Note: 1st 3 DNS entries will be used, and the rest will be ignored. 

image (25).png

  1. Review all the settings and click Finish.
  • The OVA file will be deployed in ~5-10 minutes (depending on the network speed).  
  • Verify if the connector configuration has been properly entered and not truncated.

Step 13_1.pngStep 13_2.png

  1. Deployment progress can be monitored in the Recent Tasks panel.

Step 14.png

  1. Power ON the VM once the OVA deployment is completed. You can access the VM via Remote Console.

Step 15.png

Change the Password after the OVA Deployment 

To change the default user name and the password (Login: admin / Password: Welcome@123) once OVA deployment is completed. 

To change the root user password: 
  1. Login to the host VM.
  2. Type sudo passwd command.
  3. Enter a new password in the New password field.
  4. Re-enter the new password in the Retype new password field. 
  5. When the new password is set, the passwd: all authentication tokens updated successfully message appears.
To change the user admin password:  
  1. Login to the host VM.
  2. Type passwd command.
  3. Enter the existing user password In the current user admin field.
  4. Enter a new password in the New password field.
  5. Re-enter the new password in the Retype new password field. 
  6. When the new password is set, the passwd: all authentication tokens updated successfully message appears.

OVA Deployment Validation 

  • If the DHCP service is selected during OVA deployment, then IPV4 address allocation will be done automatically. In case the IPV4 address is not assigned then restart VM. 

To verify the connector deployment, For more details, see Secure App Connector V2 CLI for TCP Applications.

  • Was this article helpful?