Patch Level Update

Date and Time Serialization Format Change

As of 2.3.0 and 2.2.2, date and time values in webclient REST responses are serialized as ISO-8601 strings, matching the Spring Boot default:

In version 2.2.1, the webclient supplied its own ObjectMapper, which overrode the Spring Boot defaults and wrote epoch milliseconds instead (1785849600000), and numeric arrays or fractional seconds for java.time types. Consumers built against that output have to parse ISO-8601 strings now.

This also applies when the webclient is embedded as a library into another Spring Boot application: it no longer overrides that application’s date format.

As a temporary migration aid, the previous output can be restored:

cibseven:
  webclient:
    custom:
      spring:
        jackson:
          serialization:
            write-dates-as-timestamps: true

Multi-engine improvement

In CIB seven 2.1.4, multi-engine support feature, introduced in 2.1.3 version, was improved. Now, the extended endpoints are used only for alternative engines, ensuring full backward compatibility for existing webclient configurations. For example, when using the default engine, the web client connects to the standard endpoint to retrieve information about a process definition (as in versions prior to 2.1.3):

/process-definition/key

and for an alternative engine, it connects to the extended one:

/engine/<engine_name>/process-definition/key

Expected Impact

We expect no impact for most of the users.

Dependency Updates

The 2.1.4 release also includes a few dependency updates to address security vulnerabilities. For a complete list of updated dependencies, see Release Notes.

Multi-engine support

In CIB seven 2.1.3, multi-engine support was introduced, and CIB seven webclient was updated to use the extended REST API endpoints that include engine names. For example, before 2.1.3, the webclient connected to:

/process-definition/key

Now, it connects to:

/engine/<engine_name>/process-definition/key

In the next release, we plan to further improve this feature, so that the extended endpoints are used only for alternative engines, ensuring full backward compatibility with existing configurations.

Expected Impact

We expect no impact for most users. If you have custom Spring Boot configurations, please review your authentication filter configuration and ensure that the /engine/* endpoint is included in the urlPatterns array. Alternatively, update your configuration to the recommended general URL pattern /*, which enables the authentication filter for all required endpoints:

  String[] urlPatterns = Arrays.asList("/*")
    .stream()
    .map(pattern -> addUrl(restApiPathPattern, pattern))
    .toArray(String[]::new);