Netcetera 3DS Server - Release Notes - Version 2.9.0.0

Overview

Published: 20.12.2023

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

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

Compatibility

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

Important notification

• Elasticsearch client will be removed in the major release planned for the end of Q2 2024. For customers using Elasticsearch as a storage for transactions data, it is highly recommended to migrate the data and traffic to OpenSearch prior to installing the above mentioned release version. Find more information on OpenSearch advantages, compatibility and migration in the OpenSearch documentation page.
• In line with the sunset of 3DS 1.0 protocol version applied globally by all major Schemes (Card Networks), Netcetera 3DS Server will stop the support of this protocol version and 3DS 1.0 artifacts will be removed from the product in the next major version.
• New Versioning V4 API endpoint was introduced in v2.8.1.0 for better visibility of Schemes in which ranges the card was found and easier integration. The /3ds/v3/versioning endpoint will be removed in the next major version.
• The Eureka Service Discovery is removed in this release thus resulting in the 3DS Admin having no more the responsibility to notify the 3DS Server(s) about configuration changes. Starting from this release, the 3DS Admin only validates and updates the configuration in the underlying storage and it is the 3DS Server(s) themselves that take care of reloading their configuration. This is achieved by having a scheduler that, on a configurable interval of time (the default is each minute), checks if there are changes in the configuration in the underlying storage and reloads them. With that in place, once a user makes configuration changes in the 3DS Admin, the 3DS Server will reload them with the next interval reload. This feature was introduced in release 2.5.3.0, but now it is made a default behaviour. Customers do not have to explicitly enable this feature because from this release it is enabled by default.

As a result of the Eureka Service Discovery being removed, the Statistics tab is also removed. We believe that this tab didn't bring value since it was using actuator endpoints which shouldn't be publicly exposed out of security reasons. Both the 3DS Server and Admin expose quite rich metrics information that could be visualised in more advanced monitoring systems in more efficient and visually attractive way.

With this change, the validate and reload mechanism is much simplified, the 3DS Admin does not rely on an external library for this reason anymore and the 3DS Admin has no more the responsibility to notify the Server for configuration changes, thus its "work" is simplified.

• The 3DS Admin actuator endpoint /reloadConfiguration that was used for validating the configuration, updating it in the underlying storage and notifying the 3DS Server instances to reload the updated configuration is now renamed to /validateAndUpdateConfiguration and is used only for validating the configuration and updating it in the underlying storage. This 3DS Admin no more notifies the 3DS Server instances to reload the configuration on this endpoint.
• The deprecated 3DS Admin built-in users' authentication (i.e. internal mode of users' authentication) is removed and customers need to use external OIDC provider for authenticating their users. More information can be found under3DS Admin OIDC support.
• Please note that we do no longer support IE11. Admin UI is based on Angular, and the supported browser versions are directly linked to the Angular versions. We regularly update our Angular versions to be up to date with the latest dependencies and minimize any potential risk for vulnerabilities.

Upgrade Notes

• The Elasticsearch Java REST Client has been succeeded by the Java Client, with the current version being 8.7.1. The Elasticsearch Java Client is forward compatible; meaning that the client supports communicating with greater or equal minor versions of Elasticsearch Server.
• A new property, springdoc.swagger-ui.enabled, has been introduced to enable or disable the default Swagger UI endpoint, which is /swagger-ui.html.
• Renamed 3DS Server and 3DSS Admin UI configuration properties:

  Old name	New name
  spring.elasticsearch.rest.*	spring.elasticsearch.*
  management.metrics.export.cloudwatch.*	management.cloudwatch.metrics.export.*
  management.metrics.export.prometheus.*	management.prometheus.metrics.export.*
  management.prometheus.metrics.export.pushgateway.enabled	sb-auto.ama.prometheus.enabled
  management.prometheus.metrics.export.pushgateway.push-rate	sb-auto.ama.prometheus.push-rate
  management.prometheus.metrics.export.pushgateway.base-url	sb-auto.ama.prometheus.endpoint1, sb-auto.ama.prometheus.endpoint2
  management.prometheus.metrics.export.pushgateway.job	sb-auto.ama.grouping-key.job
  spring.redis.*	spring.data.redis.*

• The following configuration properties are deprecated:
  • management.prometheus.metrics.export.pushgateway.shutdown-operation
• Property spring.datasource.driver-class-name is removed, the driver is automatically registered via the SPI and manual loading of the driver class is generally unnecessary. See details about the properties in the 3DS Server Configuration Properties.

Version-specific and spatial-specific dialects are deprecated

As of Hibernate 6.0, dialects can detect and adapt to the version of the database in use and its spatial capabilities. As a result, version-specific dialects (e.g. org.hibernate.dialect.PostgreSQL95Dialect) or spatial-specific dialects (e.g. org.hibernate.spatial.dialect.postgis.PostgisPG94Dialect) should no longer be used. Use these dialects instead, and ignore their deprecated subclasses:

- org.hibernate.dialect.PostgreSQLDialect
- org.hibernate.dialect.MySQLDialect
- org.hibernate.dialect.OracleDialect
- org.hibernate.dialect.SQLServerDialect

Changes