Using Secure Connections with On-prem

HTTP requests made in a custom adapter will be sent from Workato by default. This means that all traffic will come through our IP addresses. However, you can also configure it to route all requests through an on-prem agent.

• Sample connector - Mandrill
• Enable connection through on-prem agent
• Connections SDK reference

Sample connector - Mandrill

{
  title: "Mandrill",

  # This is needed for OPA
  secure_tunnel: true,

  connection: {
    fields: [
      {
        name: 'api_key',
        label: 'API key',
        control_type: 'password',
        optional: false
      }
    ]

    authorization: {
      type: 'custom_auth',

      apply: lambda do |connection|
        headers("Authorization": "Bearer #{connection["token"]}")
      end
    },

    base_uri: lambda do |connection|
      "https://api.acmestudios.com"
    end
  },

  test: lambda do |connection|
    get('/me')
  end,
}

Enable connection through on-prem agent

By default, a custom adapter does not provide an option to connect through an on-prem agent. As a result, when setting up a connection, there will not be a way to configure it.

Connection without option to use OPA

To enable the option for connecting through an OPA, all you have to do is add the secure_tunnel property in your custom adapter code. This should be set to true and be defined as a top level property.

With this property added, an input field will be visible when setting up a connection to choose an existing on-prem agent in your account.

Connection with option to use OPA

Learn how to setup an on-prem agent here.

Connections SDK reference

To be more familiar with the available keys within the connection key and their parameters, check out our SDK reference.