ESF 7.6 Upgrade Changes

This section will list the changes and upgrades made in ESF 7.6.0 and that need to be considered when updating from a previous release. It is possible to perform an upgrade from ESF 7.0.2, ESF 7.1.x, ESF 7.2.x, ESF 7.3.x, ESF 7.4.x and 7.5.x to ESF 7.6.0 and the upgrader will preserve existing configurations.

Jersey upgrade

ESF 7.6.1 includes a Jersey version upgrade from 2.22.2 to 2.47.0, this is necessary to address CVE-2025-12383.
The version bump introduces breaking changes that impact mainly the org.glassfish.jersey.* implementation specific APIs, see Jersey Migration Guide form more details.
We recommend to review the migration guide and test the customer application components that use REST APIs before upgrading.

Identity and configuration REST API restrictions

Starting from ESF 7.6.3, the REST APIs that manage identities, permissions and the UserAdmin persistence apply the same rules enforced by the ESF Web Console. These changes affect identities that hold the rest.identity or rest.configuration permission but not kura.admin:

  • Identity V1 and Identity V2 REST APIs: such an identity can only create, update or delete identities whose permissions are a subset of its own permissions, and can only assign permissions that it holds. Creating and deleting permissions requires kura.admin. Requests that do not satisfy these rules are rejected with the 403 Forbidden status.
  • Configuration V2 REST APIs: the configuration of the UserAdmin persistence component (org.eclipse.kura.internal.useradmin.store.RoleRepositoryStoreImpl) is not returned to such an identity, and its pid is omitted from the pid lists. Updating that configuration and rolling back a snapshot require kura.admin; otherwise the request is rejected with the 403 Forbidden status.

Identities holding the kura.admin permission and requests received through the cloud request handlers (IDN-V1, IDN-V2 and CONF-V2) are not affected.

We recommend reviewing the permissions assigned to the identities used by customer applications and remote management tools that call these REST APIs, and testing them before upgrading. If an application cannot be adapted immediately, the previous behaviour can be temporarily restored with the -kura.rest.identity.legacyIdentityManagement and -kura.rest.configuration.legacyUserStoreAccess startup arguments, as described in Restoring the previous behaviour.

🚧

The ESF start scripts are regenerated during the upgrade, so these arguments must be added after upgrading to ESF 7.6.3, and again after every subsequent upgrade. In production mode, the launch script fingerprint must also be reloaded after editing the script.

Wire Service REST API factory pid validation

Starting from ESF 7.6.3, when a Wire V1 REST API request updates a component that already exists on the system, the service.factoryPid property specified in the request must match the factory pid of the existing component. Otherwise, the request is rejected with the 400 status and no changes are applied. Applications that send Wire Graph configurations should be checked to make sure that they report the correct factory pid for existing components.

ReliaGATE/DynaGATE 10-14 Serial Port Configurator

In ESF 7.5.x and before, the Serial Port Configurator component for 10-14 allowed to configure only the COM1 port, forcing COM0 in RS232 mode.

ESF 7.6.0+ provides a new Serial Port Configurator that allows to configure both COM0 and COM1 serial ports, in this version the com1.mode property defined previously is replaced by a new com.modes property that covers all mode combiation supported by the line driver.

ESF Upgrader will set the value of the new com.modes property basing of the value of the old com1.mode property preserving the serial port configuration that was in place before the upgrade. The old com1.mode property will be ignored by ESF 7.6 if specified as part of a configuration update. For more details see the ReliaGATE/DynaGATE 10-14 page.