Version 5.10 (April 2025)

Prev Next

New features and enhancements

New endpoints for authentication and signature validation based on Cronto images

OneSpan Authentication Server supports new methods for authentication and signature validation where users are presented a Cronto image, scan that image and complete the process on their mobile device.

DIGIPASS Gateway was extended to provide new service endpoints to be integrated with the new workflows:

  • Scan and login is an authentication method based on Cronto images, providing the following new service endpoints:

    • /rest/v2/authentication/scan/authUser
    • /rest/v2/authentication/scan/cancelAuthUser
    • /rest/v2/authentication/scan/getPreparedSecureChallenge
  • Scan and sign is a signature validation method based on Cronto images, providing the following new service endpoints:

    • /rest/v2/signature/scan/authSignature
    • /rest/v2/signature/scan/cancelAuthSignatureRequest
    • /rest/v2/signature/scan/getPreparedSignatureRequest

AES encryption of sensitive configuration data

DIGIPASS Gateway stores its configuration in a Java properties file. Sensitive configuration data, such as the push notification proxy password, the API keys, the PKCS#12 certificate password, and the Java keystore password, is encrypted.

To improve security, the encryption algorithm has been changed, sensitive configuration data is now encrypted using AES-256 by default. If you upgrade an existing deployment, the sensitive configuration values stored with the old encryption are retained and can still be read. If you change the values after the upgrade, the new values will automatically be encrypted using AES-256.

We recommend that you update the values of all sensitive configuration settings to switch to the new encryption algorithm.

Upgrade path

DIGIPASS Gateway supports direct upgrades from version 5.9 to version 5.10 on the supported operating systems.

Supported platforms, database management systems, and other third-party products

Web servers

DIGIPASS Gateway can now be run on these web application servers (based on the respective JRE):

  • Apache Tomcat 10.1–10.1.34 (included)

    • Oracle Server JRE 17
    • Azul Zulu 17 (included)

CVE-2025-24813 vulnerability

Recently, a critical vulnerability was discovered in the included version of Apache Tomcat (10.1.34), which allows potential remote code execution, information disclosure, and information corruption.

This vulnerability has been analyzed and labelled as not exploitable when you deploy DIGIPASS Gateway using the provided installation packages.

If you deploy the DIGIPASS Gateway web application file directly to your own web server, refer to the vulnerability description for more detailed information and recommended actions, available at https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-24813.

Software libraries

The software library lists are not exhaustive and include the most significant and security-relevant updates only. CVE references are provided for informational purposes only and do not imply that the corresponding vulnerabilities were exploitable in the product. For a complete overview, refer to the third-party dependency files included with the installed product.

This version now includes the following (updated) third-party libraries:

Fixes and other updates

Issue OAS-19961: API key generation takes a long time

Description: In some Linux environments, using the OneSpan Web Configuration Tool to automatically generate API keys for DIGIPASS Gateway can take a long time. This issue depends on the entropy pool used to generate pseudorandom numbers and can affect the following commands:

  • admintool api-key-backend generate
  • admintool api-key-frontend generate

Affects: DIGIPASS Gateway on Linux

Status: This issue has been fixed.

Deprecated components and features

PDF documentation (Deprecated)

You can view the user documentation of most OneSpan products online already at https://docs.onespan.com/, and we plan to shift exclusively to online documentation.

This means that PDF documentation will be completely removed in future major releases of DIGIPASS Gateway (currently planned for 5.11).

Known issues

Issue OAS-7063 (Support case CS0049841): FQDN cannot start with number

Description: DIGIPASS Gateway cannot be installed if the fully qualified domain name (FQDN) of the server starts with a number, e.g. 001234-MYHOST. In that case, the setup will issue an error when it attempts to generate a self-signed certificate for the Apache Tomcat web server.

Status: No fix available. To circumvent this issue ensure that the FQDN meets the naming requirements before you install DIGIPASS Gateway.

Issue OAS-4908 (Support case CS0024103): Certificate must contain IP address when using FQDN

Description: If you use the FQDN to connect to the OneSpan Authentication Server instance, the respective server certificate for SOAP connections must specify the IP address of the OneSpan Authentication Server instance either as common name (CN) or the subject alternative name (SAN).

Otherwise, this can cause a "No subject alternative name matching IP address" error message during the setup, indicating that DIGIPASS Gateway verifies the SAN in the OneSpan Authentication Server certificate but does not find any matching IP address.

Status: No fix available. The OneSpan Authentication Server IP address must be set either as common name (CN) or the subject alternative name (SAN) in the certificate.

For more information, see KB0014260.

SSL certificate selection from network repository

Description: With the current version of the DIGIPASS Gateway installer, it is not possible to select the OneSpan Authentication Server SOAP certificate if it is located on a network drive.

Status: No fix available. To circumvent this issue the certificate must first be copied locally before being selected when installing DIGIPASS Gateway.