Prerequisites

The Remote Server system has been created (the Verj.io Service Plan has been created)
The Gateway Server System has been created (this might be either a new server or upgrading an existing Verj.io Server and adding the Gateway Server licence feature)
The Gateway Server System has an external facing IP address (this is only necessary if REST calls from the Remote Server to the Gateway Server are needed)

Configuration Instructions

1. Configure authentication on the Gateway Server

All users must be authenticated on the Gateway Server system in order to connect to the Remote Server 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 Gateway Server

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

· In the Gateway Server 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 Remote Server Configuration section, add a Remote Server and enter its Base URL. If this is a Verj.io Service Plan, this will be something like https://domainname/apps or http://ipaddress/apps.

· In the Gateway Server REST IP Whitelist section, optionally add the IP address(es) of any Remote Servers which are allowed to call Gateway REST services on this Gateway Server.

3. Configure the Remote Server

Start the Server Admin App on the Remote Server system: if this is a Verj.io Service Plan, click on Server Settings from the Service Plan details page, then More admin options to invoke the Server Admin App. Then select Remote Gateway Server.
Add a new Client Gateway Server Configuration, give it a name (this can be any name of your choice), then enter the Base URL of the Gateway Server and the API Key (this should be copied from the Gateway Server configuration in the previous section). The Base URL will be something like https://www.mycorp.com/ebase where ebase is the web application name.
In the Client Gateway Server IP Whitelist section, optionally add the external facing IP address of the Gateway Server.
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

· Add a tile to the Gateway Portal application that links to a form on the Remote Server and test this.