High-availability deployment model
The high-availability deployment model is an example of a system with higher performance and greater availability.
Figure: High-availability deployment model
Performance
Higher performance is achieved with the use of load balancing in client-side applications, between two primary OneSpan Authentication Server instances. Database load sharing to dedicated database servers is configured in each OneSpan Authentication Server instance. A dedicated audit database is used for auditing and reporting. Administration is performed via the backup OneSpan Authentication Server instance, thus minimizing the load on the primary servers.
Availability
Availability of the system is increased by the configuration of failover and failback between the OneSpan Authentication Server instances, and the use of a backup database server.
Client-side load balancing and failover is built-in to the client application in this type of deployment.
OneSpan Authentication Server
Two primary OneSpan Authentication Server instances and one backup OneSpan Authentication Server instance.
Data is stored on dedicated database servers.
Administration
All administrative operations are performed on the backup server.
Long running operations can be performed with no direct impact on the authentication server performance handling authentication requests (these administrative operations will introduce only a replication impact on the commercial database servers).
The administration scenario could be disabled on both primary servers to exclude administrative load. This is done via the Administration Web Interface.
Replication
Custom database replication is used. OneSpan Authentication Server replication is disabled.
Auditing
Auditing data should be written to databases at each site. The data should be imported to the master auditing database at the administration site on a regular basis.
Reporting
Deployment steps
To set up the high-availability deployment model
- Install a commercial database on each dedicated database server, and modify the schema as needed.
- Set up replication between the databases.
- Install OneSpan Authentication Server on each primary server and the backup server, using the Advanced installation option.
- Configure database load sharing on each OneSpan Authentication Server instance.
- Install a database on the audit server.
- Set up auditing as required.
- Configure reporting as required.
- Schedule making data available for reporting, i.e. schedule to merge the primary servers' audit files with the backup server auditing information using the Maintenance Wizard.