Prerequisites

A remote Verj.io On-Premises environment has been installed or a Verj.io Service Plan has been created.
The Verj.io Gateway has been installed.
The Verj.io Gateway has an external facing IP address (this is only required if creating Gateway Tunnels or Gateway REST services).

Configuration Instructions

1. Configure authentication on the Gateway

All users must be authenticated on the Gateway in order to connect to a Verj.io Application running on a remote Verj.io On-Premises environment or Verj.io Service Plan using SSO. This example shows the use of Windows Authentication, but any authentication technique is acceptable. Use of IIS with the AJP connector is a prerequisite for Windows Authentication and IIS option Windows Authentication must be configured. (See User Authentication for other authentication techniques.)

· From the Server Admin App home page, select User Authentication and then click the Use Windows Authentication checkbox.

· Initially, also click the Allow Non-Windows Users option. This can be disabled once you have verified that Windows authentication is working successfully.

· Optionally, Active Directory groups and attributes can be extracted and used as Verj.io user roles and credentials. If this is required:

o Select Security Properties in the Server Admin App and configure LDAP Connection Properties to point to your AD server. Test the connection.

o On the User Authentication page, select Automatically populate roles from AD and/or Automatically populate credentials from AD as required. The second option requires a table of the attributes you would like to extract from AD. A starter set of attributes is provided.

2. Configure the Verj.io Gateway

On the, click Gateway Configuration from the Server Admin App home page to show the Gateway Configuration page.

· In the Gateway Properties section, if no API Key is shown, click Generate new API Key to generate a new key then click the update button to save the key.

· Add the optional properties Issuer Name and Issuer URI as required.

· In the Single Sign On section, you can optionally

· Add the IP addresses of the clients who are allowed to use SSO on the Gateway. Note that leaving this blank allows all clients to use SSO.

· Add a remote Verj.io On-Premises environment or Verj.io Service Plan and enter its Base URL. If this is a Verj.io Service Plan, this will be something like https://domainname.

· In the Incoming Requests section, you can optionally:

· Add the IP addresses of the Verj.io On-Premises environments and Verj.io Service Plans that are allowed to call this Verj.io Gateway. Note that leaving this blank allows all clients to use SSO.

· Configure any Gateway Tunnels to private resources that trusted Verj.io On-Premises environments and Verj.io Service Plans need access to.

3. Configure the remote Verj.io On-Premises environment or Verj.io Service Plan

Start the Server Admin App on the remote Verj.io On-Premises environment or Verj.io Service Plan. If this is a Verj.io Service Plan, click on Server Settings from the Service Plan’s details page in the Verj.io Cloud Portal, then More admin options to invoke the Server Admin App. Then select Gateway Connections.
Add a new Gateway Configuration, give it a name (this can be any name of your choice), then enter the Base URL of the Gateway and the API Key (this should be copied from the Gateway configuration in the previous section). If this is a Verj.io Service Plan the Base URL will be something like https://domainname. You can also add the external facing IP address of the Verj.io Gateway in the Single Sign On requests from the Gateway section to restrict the sources of SSO requests from that Gateway.
The Gateway Connection page lists all configured Verj.io Gateways along with any Gateway Tunnels that can be connected to.
Configure authentication of Gateway users: select User Authentication from the Server Admin App home page and then select Use Gateway Authentication.

4. Configure the Gateway Portal

· If you want to use the Gateway Portal application on the Gateway to facilitate SSO, then tiles can now be created that link to forms on the remote Verj.io On-Premises environment or Verj.io Service Plan.