Skip to content
GBG Documents & Biometrics Documentation

Server requirements

This section details the steps for setting up the AssureID Connect runtime environment. These steps should be completed before you run the automated install script to install.

GBG requires using Redis or Amazon ElastiCache for Redis (if you are using AWS) for distributed caching. A cluster of one or more Redis instances is required, depending on the traffic/load sent to the AssureID Connect web service.

GBG supports using a reader endpoint, a writer endpoint, or a single shared endpoint. You must update the ConnectSettings.xml file (an earlier version will not work).

See the new ElasticacheCluster settings (WriterHost and ReaderHost), which replaced the Host setting, for more information.

For example: example.cache.amazonaws.com:6379

In order to use Redis, you need to form a cluster that consists of one or more Redis instances with a single, common Redis endpoint. The following table describes the server network access requirements. The inbound settings describe the ports that must be open to allow AssureID Connect application servers to access Redis.

Direction Description Protocol Port Source
Inbound Redis TCP 6379 AssureID Connect Application servers

Note: There are no outbound server requirements unless specified by the infrastructure provider.

The AssureID Connect Database server has the following recommended minimum database server requirements for Microsoft SQL Server, or for MySQL or AWS Aurora.

Note: Both MySQL and Microsoft SQL Server may impose additional minimum storage requirements on AWS.

Microsoft SQL Server MySQL/AWS Aurora
Microsoft SQL Server 2016 MySQL 5.7 (with InnoDB storage engine)
2-core CPU 2-core CPU
32 GB RAM 32 GB RAM
100 GB disk storage 100 GB disk storage

Important: If you are installing MySQL database on a server to be used by AssureID Connect, then you must configure the MySQL Database engine to have a minimum of 2G of memory for the innodb_buffer_pool_size parameter.

Example

innodb_buffer_pool_size=2G

Typically, the configuration is stored in the C:\ProgramData\MySQL\MySQL Server 5.7**my.ini** file. See https://dev.mysql.com/doc/refman/5.7/en/innodb-buffer-pool-resize.html for more information.

The following table describes the Database server network access requirements. The inbound settings describe the ports that must be open to allow AssureID Connect application servers to access either the Microsoft SQL Server or MySQL Server database.

Direction Description Protocol Port Source
Inbound Microsoft SQL Server TCP 1433 AssureID Connect application servers
Inbound MySQL TCP 3306 AssureID Connect application servers

Note: There are no outbound server requirements unless specified by the infrastructure provider.

The following prerequisite software dependencies must be installed and configured on the database server before beginning the installation process:

Microsoft SQL Server MySQL/AWS Aurora
A static IP address for the database server A static IP address for the database server.
A database instance must be created and available on the server. A database instance must be created and available on the server.
Provide a login with sqladmin or setupadmin access to create and configure the AssureID Connect database. REQUIRED Provide a login with the database admin role in order to create and configure the AssureID Connect database. REQUIRED
Enable mixed-mode authentication. REQUIRED

This section describes the recommended minimum per-application server and network requirements for the AssureID Connect application server.

  • Windows Server 2016 with IIS
  • 4-core CPU
  • 16 GB RAM
  • 30 GB disk storage

The following table describes the network access requirements for the AssureID Connect Application server. The ports must be open to allow clients applications to access the AssureID Connect application and for AssureID Connect application servers to interact with the distributed cache and the database.

GBG recommends using HTTPS for internet-facing connections. If you are using a load balancer, install the certificate on the load balancer, It is safe to use HTTP between the load balancer and the AssureID Connect application servers on a secure, private network. If you are not using a Load Balancer, install the certificate on each application server.

Description Direction Protocol Port range Source
HTTPS Inbound TCP 443 Load balancer or AssureID Connect clients
HTTP Inbound TCP 80 Load balancer or AssureID Connect clients
HTTPS Outbound TCP 443 0.0.0.0/0
Redis or ElastiCache Outbound TCP 6379 AssureID Connect with Redis or ElastiCache
Database Outbound TCP 3306 (MySQL) or 1433 (Microsoft SQL Server) AssureID Connect Database
NTP Outbound UDP 123 0.0.0.0/0

1 MySQL

2 Microsoft SQL Server