Netcetera 3DS Server - Release Notes - Version 2.11.0.0

Overview

Published: 12.09.2024

Version 2.11.0.0 is a major release of the Netcetera 3DS Server.

For documentation about this release please refer to the documentation site.

This version is NOT backwards compatible with previous 2.10.0.0 version of the Netcetera 3DS Server.

In line with the sunset of 3DS 1.0 protocol version applied globally by all major Schemes (Card Networks), Netcetera 3DS Server stopped the support of this protocol version and 3DS 1.0 API is removed from the product.

Properties starting with "threedss.encryption." are renamed to start with "threedss.configuration.encryption.".

Introduced a method for storing encrypted application properties. Check the details inapplication properties encryption.
We've enhanced monitoring capabilities by adding new metrics for HTTP client DS connection pools, prefixed with app.httpclient.pool.connections. These metrics allow you to track the total number of maximum allowed persistent connections, available connections, leased connections, pending connection requests, and the maximum number of connections per route for each pool.

Improved HTTP client to automatically close expired and idle connections based on the new ds-client.connection.max-idle-time configuration property, and added ds-client.connection-request.timeout.milliseconds for configuring the timeout when acquiring a connection from the pool. See details about the properties in the 3DS Server Configuration Properties.
Schedulers removing 3DS Method data, Results Data and Operation Data are removed in case Redis is used as session storage. In the previous major release TTL was introduced to each record and the records are now removed by Redis upon their expiration.
RESULTS flow tag was renamed to PUSH_RESULTS for Http Client metrics.
In the 3DSS Admin UI, enhanced CSR creation with a warning prompt that notifies users of potential key-pair overwriting when an alias match is detected in the keystore.

Fixed an issue with bulk importing merchants that occurred when multiple organizations had merchants with the same Merchant Configuration ID.
Fixed a bug where enabled schemes were missing from the configuration when a new organization was added in the 3DSS Admin UI and the 3DS Server reloaded the configuration.
Fixed the Mapped Diagnostic Context mappings for 3DSS Admin UI default Logback configuration for audit logs.
Fixed an issue where the HTTP client was closed too early when cached RestTemplates were evicted under high transactions load.
Fixed data sources configuration in the Admin UI application. The spring.datasource.* properties are now correctly used for the primary data source handling regular application DML operations, while the threedss.db.flyway.* properties are designated for executing Flyway migrations (DDL operations) against the database.
Fixed a NullPointerException in the Versioning flow that occurred when a cached card range had a directory server URL without a corresponding configured Scheme.