Gateway Properties

The Gateway Properties section contains the Gateway API Key that is used to create the trust relationship between this Verj.io Gateway and remote Verj.io On-Premises environments and Verj.io Service Plans. See Gateway Connections for more information on how this Key is configured in those remote environments.

API Key – When the Gateway Server starts for the first time, an API Key is generated. Should the API Key become compromised a new one can be generated by clicking the Generate New API Key button. Remote environments using this key will need to be updated to continue to communicate with the Gateway.
Issuer Name – The issuer name is an optional attribute. If specified it will be added to the token sent to a remote environment.
Issuer URI - The issuer URI is an optional attribute. If specified it will be added to the token sent to a remote environment.

Single Sign On (SSO) Configuration

Verj.io Gateways can facilitate Single Sign On of users into configured Verj.io Applications running in remote Verj.io On-Premises environments and Verj.io Service Plans.

Click the appropriate icon to add a remote Verj.io Application to facilitate Single Sign On to or add an IP address the whitelist.
Click the icon to refresh the respective display.

Single Sign On Whitelist

IP addresses can be specified to restrict the sources that can use the Single Sign On feature – either using the Gateway Portal or using the direct link to Verj.io Applications.

Each IP address line can be specified as either:

A single IP address e.g. 127.0.0.1
An IP address containing an * wild card as the last character e.g. 192.168.*
An IP address range e.g. 192.168.0.1|192.168.0.10

Adding or Editing a Remote Verj.io Application

Name – A name given to represent the remote Verj.io On-Premises environment or Verj.io Service Plan.
Description – An optional description of this Verj.io Application.
Base URL – The URL of this Verj.io Application. Requests sent to this Verj.io Application all start with the URL specified here.

Incoming Request

Verj.io Applications running on trusted Verj.io On-Premises environments and Verj.io Service Plans can connect to Gateway Tunnels to access private resource in the Gateway’s network, or to call Gateway-only REST services.

Click the appropriate icon to configure a Gateway Tunnel or to add a new IP address to a whitelist of trusted remote Verj.io Application sources.
Click the icon to refresh the respective displays.

Incoming Request Whitelist

IP addresses can be specified to further restrict the sources that can connect to configured Gateway Tunnels and Gateway-only REST services.

Each IP address line can be specified as either:

A single IP address e.g. 127.0.0.1
An IP address containing an * wild card as the last character e.g. 192.168.*
An IP address range e.g. 192.168.0.1|192.168.0.10

Gateway Tunnels

Gateway Tunnels can be configured in a Verj.io Gateway, each one connecting to a private resource on the same network as the Gateway. Verj.io Applications running in trusted Verj.io On-Premises environments or Verj.io Service Plans can connect to a Gateway Tunnel and communicate with the configured private resource as if connecting to them directly. Most private resources can be access in this manner, including Database, REST, SOAP, email and LDAP services.

Name – The name of the Gateway Tunnel. The name will appear in trusted Verj.io Applications as an available Gateway Tunnel (see Gateway Connections for details).
Hostname – The hostname or IP address to the private resource.
Port – The Port number of the private resource.
Secure – Whether the resource must be connected to via a SSL/TLS connection (e.g. https or ldaps). Appropriate SSL certificates for that resource may need to be added to the Verj.io Gateway’s trust store, especially if the resource is secured using a self-signed certificate.