Replication with ODBC

When multiple OneSpan Authentication Server instances with individual databases are used, they can be configured to replicate data changes between them to keep all databases synchronized.

OneSpan Authentication Server replication works on user data and configuration data only. Audit data is not replicated, all replication instances keep and maintain their own audit data.

If you are running multiple OneSpan Authentication Server instances using ODBC in a high-load scenario, we strongly recommend to disable OneSpan Authentication Server replication and set up replication on the ODBC database server level instead.

Slow responses from the OneSpan Authentication Server instances under load will disrupt the replication process!

Common scenarios

Primary and backup OneSpan Authentication Server instances

The basic and most common replication setup is used when a company has two OneSpan Authentication Server instances—one primary instance to which all authentication requests are customarily sent, and one backup instance to use when the primary server is busy or unavailable (see Figure: Replication between primary and backup OneSpan Authentication Server instances). Replication is usually set up to occur very frequently.

Replication between primary and backup OneSpan Authentication Server instances

Figure: Replication between primary and backup OneSpan Authentication Server instances

Primary, backup, and disaster recovery OneSpan Authentication Server instances

This scenario is often used when a company requires an off-site disaster recovery OneSpan Authentication Server instance and database (see Figure: Replication between primary, backup, and disaster recovery OneSpan Authentication Server instances).

Replication between primary, backup, and disaster recovery OneSpan Authentication Server instances

Figure: Replication between primary, backup, and disaster recovery OneSpan Authentication Server instances

Other scenarios

There are other possible replication scenarios. For example, a company may have three OneSpan Authentication Server instances, all replicating to each other (see Figure: Replication between three OneSpan Authentication Server instances). This can keep data better up to date than a simpler replication chain.

Replication between three OneSpan Authentication Server instances

Figure: Replication between three OneSpan Authentication Server instances

Another possible scenario are two primary OneSpan Authentication Server instances, each with a backup OneSpan Authentication Server instance, and an extra replication link to speed up data communication (see Figure: Complex OneSpan Authentication Server replication scenario).

Complex OneSpan Authentication Server replication scenario

Figure: Complex OneSpan Authentication Server replication scenario

Using SSL with replication

Security for replication can be further enhanced by enabling SSL. You can enable SSL when you define the replication destination server in the Configuration Utility. Use the Destination Servers page to provide the SSL certificate, SSL password, and CA certificate store.

For more information about enabling and configuring SSL for replication connections, refer to the OneSpan Authentication Server Administrator Guide, Section "Enabling SSL for replication connections".