SSH Tunnel from Pure server to Customer networkSSH Tunnel from Pure server to Customer network

This guide explains how we support using a SSH tunnel/port forward to give a Pure server hosted by Elsevier access to specific services on the customers network.

Step 1: Send information to Elsevier

• Contact Pure Support Team to let them know that you wish to use a SSH tunnel to connect to a service on your network. Include the following information:

Username - The username that Elsevier should use to connect to the SSH server.
SSH Server - The DNS name / IP address of the SSH server that Elsevier should connect to.
Remote server - The server that should be accessed through the SSH tunnel. This can be a DNS name or an IP address.
Remote port - The port that should be used to access the remote server.
Local port - The port that will be accessed by Pure (most often same as Remote port)

• Elsevier will then setup a job on the Pure server that will make sure the connection is working, and if not it will re-connect.
• Elsevier will then generate SSH keys to use for authentication, and send the public key to you.

Step 2: Configure SSH server

• Add the user that Elsevier should use to connect to your SSH server, and add the public key to allow us to connect with the private key.
• Make sure to whitelist Pure outgoing IP's from this list: IPs in use for Pure and Pure Portal
   

Step 3: Configure Pure jobs

• The last step is to configure the jobs in Pure that needs this SSH tunnel to use host.docker.internal and the assigned port for the connections.