Skip to main content

Enable HTTP Tunneled TCP

The Corsha Gatekeeper is able to add Corsha Authentication to a Tunneled TCP connection over HTTP.

The Gatekeeper expects a Corsha Cred during the TCP Tunnel's initial handshake, then opens up the tunnel as expected. This means that the tunnel is not constantly being authenticated, but is authenticated at initialization.

Docker Deployment Configuration​

Tunneling is enabled by editing the proxy-config.yaml. To enable tunneling, simply set the targeted service's upstream.protocol to TCP as seen below:

http:
  listenPort: 8080
  proxies:
    - name: proxy
      domain: proxy
      upstream:
        host: "api" # the proxied tcp service
        port: 4880
        protocol: TCP

Helm Deployment Configuration​

Tunneling is enabled by editing the values.yaml. To enable tunneling, simply set the targeted service's upstream.protocol to TCP as seen below:

http:
  listenPort: 8080
  proxies:
    - name: proxy
      domain: proxy
      upstream:
        host: "api" # the proxied tcp service
        port: 4880
        protocol: TCP