Version 5.9 (August 2024)

You can now set a notification priority when sending a notification. High priority notifications can be received without delay and wake up the screen, even if the target device is in Do Not Disturb or a sleep mode.

The sendNotification [v2] service now accepts an optional isHighPriority parameter to set the notification priority. If omitted, isHighPriority is set to true by default.

DIGIPASS Gateway supports direct upgrades from version 5.7 or 5.8 to version 5.9 on the supported operating systems.

Software libraries

The software library lists are not exhaustive, but include the most notable and critical updates only. For a complete overview, refer to the third-party dependency files included with the installed product.

Web servers

Sending push notifications via Google Cloud Messaging (GCM) or legacy Firebase Cloud Messaging (FCM) APIs was deprecated by Google on June 20, 2023, and will be removed from the Google services in June 2024!

Do not use DIGIPASS Gateway with server key string authorization to Google messaging services for new deployments and migrate to use the current Firebase service account key file authorization at your earliest convenience! For more information, refer to the DIGIPASS Gateway Getting Started Guide, Section "Configure push notification web services".

The possibility to configure DIGIPASS Gateway to use a server key string to authorize to GCM/FCM (via the admintool push-notification android-legacy command) will be completely removed in a future release of DIGIPASS Gateway.

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.

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.

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.