Configure the Gatekeeper to Handle OPC UA

The Corsha Gatekeeper can be configured to support authentication for the OPC Unified Architecture Standard (OPC UA) over TCP. More reading on the OPC UA architecture can be found at the OPC Foundation.

note

Before beginning, if this is a new Corsha Gatekeeper deployment, see the Corsha Gatekeeper Guides Deploy as a Docker Image and Deploy Using a Helm Chart to configure your deployment environment prior to following the steps found in this guide.

Docker Deployment Configuration

Configuring a Corsha Gatekeeper to handle OPC UA connections is as simple as modifying the proxy-config.yaml. To enable OPC UA, simply add the values in the appropriate section below:

opcuaTcp:
  listenPort: 4841
  tlsTermination:
    enabled: true
  upstream:
    host: <Target OPC UA Service>
    port: 4840
    protocol: OPCUATCP
  tls:
    cert: /etc/pki/tls/private/cert.crt
    key: /etc/pki/tls/private/cert.key

# Optionally, add Internal CA cert to trust
trustedCAs: /etc/pki/ca-trust/source/anchors/ca-bundle.pem

note

For a more detailed explanation of every possible Docker value, see the Docker Config Values Page

Helm Deployment Configuration

Configuring a Corsha Gatekeeper to handle OPC UA connections is as simple as editing the following values of the Corsha Gatekeeper's Helm chart. To enable OPC UA, simply set the values in the appropriate section below:

opcuaTcp:
  listenPort: 4841
  tlsTermination:
    enabled: true
  upstream:
    host: <Target OPC UA Service>
    port: 4840
    protocol: OPCUATCP
  tls:
    cert: |
        -----BEGIN CERTIFICATE-----
        <omitted>
        -----END CERTIFICATE-----
    key: |
        -----BEGIN CERTIFICATE-----
        <omitted>
        -----END CERTIFICATE-----

# Optionally, add Internal CA cert to trust
trustedCAs: |
  -----BEGIN CERTIFICATE-----
  <omitted>
  -----END CERTIFICATE-----

note

For a more detailed explanation of every possible Helm value, see the Helm Chart Values Page

info

Corsha uses x509 certificates for TLS