> Source: [sk181219](https://support.checkpoint.com/results/sk/sk181219)

# sk181219 - Harmony Connect: Proxy Support for Application Access Connector 

| Property | Value |
|----------|-------|
| Solution ID | sk181219 |
| Date Created | 2023-07-05 |
| Last Modified | 2023-07-07 |
| Technical Level | General |

## Solution

Harmony Connect allows you to tunnel the outgoing traffic of the Application Access Connector towards the controller or gateway, through a proxy component.   

**Note** - The proxy component is supported only for the Application Access Connector.   

Harmony Connect supports these proxy types to tunnel the outgoing traffic:   

* SOCKS5
* HTTP
* HTTPS

Configuring the Proxy for the Application Access Connector
----------------------------------------------------------

1. Define one of these environment variables to set the proxy for tunneling used by the connector:
   * `ALL_PROXY`/`all_proxy` for supplying SOCKS5 proxy configuration
   * `HTTP_PROXY`/`http_proxy` for supplying HTTP proxy configuration
   * `HTTPS_PROXY`/`https_proxy` for supplying HTTPS proxy configuration
2. Use any one of these methods to pass the environment variables:

* **Method 1** : Define the environment variables as part of the Docker command of the connector. For example:  

  |------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
  | **Proxy Type**                                             | **Description**                                                                                            | **Defining Environment Variable in Docker Command**                                                                                                                                                                                                                                                  |
  | **SOCKS5 proxy**                                           | Defining `all_proxy` environment variable for SOCKS5 proxy                                                 | `sudo docker run -d --cap-add=NET_ADMIN --sysctl ` `net.ipv4.ip_forward=1 --device /dev/net/tun --restart=always --log-opt ` `max-size=1g `-e all_proxy=socks5://proxy-ip:proxy-port` -e ` `Secret=XXX CONNECTOR-IMAGE `                                                                             |
  | **SOCKS5 proxy with username and password authentication** | Defining `all_proxy` environment variable for SOCKS5 proxy that authenticates given username and password  | `sudo docker run -d --cap-add=NET_ADMIN --sysctl ` `net.ipv4.ip_forward=1 --device /dev/net/tun --restart=always --log-opt ` `max-size=1g `-e all_proxy=socks5://username:password@proxy-ip:proxy-port` -e ` `Secret=XXX CONNECTOR-IMAGE` **Note** - You can replace `all_proxy` with `ALL_PROXY`.   |
  | **HTTP proxy**                                             | Defining `http_proxy` environment variable for HTTP proxy                                                  | `sudo docker run -d --cap-add=NET_ADMIN --sysctl ` `net.ipv4.ip_forward=1 --device /dev/net/tun --restart=always --log-opt ` `max-size=1g `-e http_proxy=http://proxy-ip:proxy-port` -e ` `Secret=XXX CONNECTOR-IMAGE `                                                                              |
  | **HTTP proxy with username and password authentication**   | Defining `http_proxy` environment variable for HTTP proxy that authenticates given username and password   | `sudo docker run -d --cap-add=NET_ADMIN --sysctl ` `net.ipv4.ip_forward=1 --device /dev/net/tun --restart=always --log-opt ` `max-size=1g `-e http_proxy=http://username:password@proxy-ip:proxy-port` -e ` `Secret=XXX CONNECTOR-IMAGE ` **Note** - You can replace `all_proxy` with `ALL_PROXY`.   |
  | **HTTPS proxy**                                            | Defining `https_proxy` environment variable for HTTPS proxy                                                | `sudo docker run -d --cap-add=NET_ADMIN --sysctl ` `net.ipv4.ip_forward=1 --device /dev/net/tun --restart=always --log-opt ` `max-size=1g `-e https_proxy=https://proxy-ip:proxy-port` -e ` `Secret=XXX CONNECTOR-IMAGE `                                                                            |
  | **HTTPS proxy with username and password authentication**  | Defining `https_proxy` environment variable for HTTPS proxy that authenticates given username and password | `sudo docker run -d --cap-add=NET_ADMIN --sysctl ` `net.ipv4.ip_forward=1 --device /dev/net/tun --restart=always --log-opt ` `max-size=1g `-e https_proxy=https://username:password@proxy-ip:proxy-port` -e ` `Secret=XXX CONNECTOR-IMAGE ` **Note** - You can replace `all_proxy` with `ALL_PROXY`. |

<!-- -->

* 
<!-- -->

* **Method 2** : Define the environment variables in the environment file and add it in the Docker command of the connector. For example:  
  `sudo docker run -d --cap-add=NET_ADMIN --sysctl net.ipv4.ip_forward=1 `  
  `--device /dev/net/tun --restart=always --log-opt max-size=1g -e `  
  --env-file=./my-env-file.en`?-e Secret=XXX CONNECTOR-IMAGE`

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content