Testing and authenticating connectors

Connectors with on-prem support

Copy

Following connectors are available across all three regions (US, EU and AP) for use in an on-prem setup:

Notes about multi-region availability

Copy

Kafka v1.0 is not on the above list but it is available to be used in the US.

Creating connector authentications

Copy

Now you have your agent set up and connected to Tray you can set up authentications that will be routed to the on premise location where the agent is located (rather than the internet).

This can be done in all places where you can currently create authentications in Tray.

So if you are creating an MS Dynamics GP auth you can select the on-prem group to route this authentication through:

Once you’ve selected the on premise group you can proceed to create an authentication as normal.

Once an on-prem authentication for a connector has been created, it can be used in any workflows which use that connector.

DNS support

Copy

The agent supports proxying DNS requests.

This allows connectors to use private DNS servers accessible by the agent.

This feature can be disabled using the --disable-dns flag (when DNS is disabled any addresses must be publicly resolvable from the internet, or an IP address will have to be used instead).

Port configuration

Copy

Test setup

Copy

While you can of course attempt to connect to your on-prem services straight away, a simple way to test your agent is to:

1. Configure a simple test API service (using node express, nginx etc.) on your network which accepts token-based auth and run on e.g. port 3000

2. Create a custom token-based service in your tray workspace

3. Create a manually-triggered test workflow which uses the HTTP client to make a simple GET request to your API service (using your network's private IP address):

You can create an on-prem authentication using the custom service:

Then run the workflow and check the logs for a successful execution