For On-Premises deployments that are using a proxy to connect to the internet, the forward proxy configuration feature enables Control Room features that require internet connectivity to function seamlessly.

In such deployments, Control Room features (such as license server and audit log server) cannot easily connect to Cloud-hosted services for updates outside of their internal network. So configure forward proxy for such features so that the features can function seamlessly.

The following Control Room offered services and servers are supported to use the forward proxy hosts:

  • Automatic packages updates
  • License server
  • OAuth managed connections (see use case below)
  • OAuth services

Image displaying the workflow of forward proxy

Procedure

  1. Log in to the Control Room as an administrator.
  2. Navigate to Settings > Network settings > Forward Proxy Configuration.
  3. Click Edit and then select Enabled.
    This feature is disabled by default.
  4. From the Type of connection/scheme menu, select a connection.
    Example: http
  5. In the Host field, enter the host IP address of the proxy host.
    Example: 10.10.0.1 (IP address of the proxy)
  6. In the Port field, enter the port number of the proxy host.
    Example: 8081
  7. Select an appropriate authentication type:
    • None: No authentication is used to connect to the proxy host.
    • Basic Authentication: Uses basic authentication to connect to the proxy host. Enter the Username and Password to connect to the proxy host.
  8. Ignore addresses: Specify the IP addresses or host names (separated by comma) that need not use the proxy server to connect to the internet.
    Example: localhost, 127.0.0.1
    We recommend that you configure the Ignore addresses to prevent calls to localhost from going through the proxy.
Use Case:

Enabling Forward Proxy for OAuth managed connections

Overview:

Finance Company ABANK uses Google Suite apps a lot in its Lines of Business (LOBs). With Forward Proxy support in the Automation 360 On-Premises OAuth setup, you can connect with Google APIs to improve automation scalability.

This example shows a successful case where Forward Proxy (with basic authentication) is set up to allow OAuth connections to work smoothly for Gmail using a CCProxy server.

Prerequisites:

  • A working Control Room setup with:
    • Manage OAuth permission
    • Manage Settings permission
  • Installed and configured CCProxy server with:
    • Basic authentication
    • Permitted access only for designated users
  • Control Room URL must be accessible via HTTPS
Forward Proxy Success — Basic Authentication Procedure:
  1. Log in to the Control Room: Use a user account with Manage OAuth and Manage Settings permissions.
  2. Configure Forward Proxy: Navigate to Manage → Settings → Network Settings → Forward Proxy Configuration.
    1. Turn on Forward Proxy.
    2. Enter the following details:
      • CCProxy IP: 145.xxx.xxx.xxx
      • Port: 808
      • Auth Mode: Basic Authentication
      • Username: user1
      • Password: ••••••
    3. Click Save.
  3. Create Gmail OAuth connection: Navigate to Manage → Settings → OAuth Configuration.
    1. Create a new OAuth connection using Gmail OAuth credentials.
    2. Enter the required Google API scopes.
    3. Save and move on to Test Connection.
  4. Validate through CCProxy logs: Navigate to Manage → Settings → OAuth Configuration.
    1. Enable monitoring/logs on the CCProxy machine.
    2. Click Test Connection in the Control Room.
    3. Select the Google account to authenticate.
Expected Results and Confirmation:
  • OAuth token retrieval succeeds.
  • In CCProxy logs, observe entries for:
    • www.googleapis.com
    • Authentication traffic showing successful passage through the proxy.
  • Google API requests (auth token requests) are successfully routed via Forward Proxy.
  • Control Room receives and validates the OAuth token using the proxy-configured route.

Google API OAuth requests are forwarded through an authenticated proxy, and the OAuth integration for Google Suite is now enabled and secure through the defined proxy path.

Customer Benefits:
  • Seamless Google Suite integration.
  • Enhanced automation scalability.
  • Secure and controlled external API access via authenticated proxy.
  • Reduced ticket volume due to proactive feature validation.

The following video shows how to configure forward proxy: