Performance and Deployment Guide

Prev Next

Thank you for reading the OneSpan Authentication Server Performance and Deployment Guide. This guide provides information about common deployment models, performance considerations, and performance statistics.

Components or features described in this document may need to be configured to meet the standards of the General Data Protection Regulation (GDPR). If your organization is collecting or in any capacity processing data on citizens of a European Union country, your organization is subject to the GDPR.

For more information about GDPR, refer to the OneSpan Authentication Server GDPR Compliance Guide.

Who should read this guide?

This guide is designed for system managers and administrators using OneSpan Authentication Server and its side products.

You should be familiar with:

  • Online authentication and authorization tools and protocols, including SOAP, RADIUS, WSDL, SSL, XML, HTML, and TCP/IP.

  • Windows and Linux security software environments including IIS, Active Directory, and ODBC.

  • Administration tasks including user management, policy, scheduling, reports, and performance monitoring.

  • Password management and encryption techniques.

Factors that affect OneSpan Authentication Server performance

Some elements that affect the performance of OneSpan Authentication Server are the following:

  • System specifications. For more information, refer to the OneSpan Authentication Server Installation Guide for Windows and the OneSpan Authentication Server Installation Guide for Linux, section "System requirements".

  • Data store type and its location(s). See Deployment models.

  • Data replication method. For more information, refer to the OneSpan Authentication Server Administrator Guide, section "Replication".

  • Load balancing and failover options. See Load balancing.

  • Auditing method. Auditing to database is encouraged, as this will speed up both the auditing and reporting processes. Auditing to file is available, but will produce significant processing overheads for reporting, as reporting can only be performed from a database.

  • Authentication protocol.

  • Tracing. Tracing highly impacts the performance if enabled.