Migration from 2.1.x to 2.2.x

This guide contains instructions for migration from PowerAuth Cloud version 2.1.x to version 2.2.0.

Database Changes

Liquibase is used for automated migration of database schema during startup of PowerAuth Cloud backend components.

Configuration Updates

Temporary Activation Block

A new feature allows activations to be blocked only temporarily after reaching the maximum number of failed attempts, instead of being blocked permanently. The feature applies to activations using cryptography protocol version 4. Activations using older protocol versions are always blocked permanently, regardless of this configuration.

When enabled, an activation that reaches the maximum number of failed attempts is blocked for a limited time and then automatically returned to the ACTIVE state.

The feature is disabled by default. You can configure it using the following environment variables:

POWERAUTH_SERVER_CRYPTO_TEMPORARY_ACTIVATION_BLOCK_ENABLED=false
POWERAUTH_SERVER_CRYPTO_TEMPORARY_ACTIVATION_BLOCK_PERIOD_IN_MILLISECONDS=300000
POWERAUTH_SERVER_CRYPTO_TEMPORARY_ACTIVATION_BLOCK_MULTIPLIER=2

See Post-Install Configuration for more details.

Admin Console Container Port Change

The Admin Console SPA container now serves static files on port 8080 inside the container (previously port 80).

If your deployment configuration maps the internal container port, update it accordingly.

Dependency Updates

Docker Base Image Upgrade

The Docker base image has been upgraded from ibm-semeru-runtimes:open-21.0.9_10-jre-noble (OpenJDK 21) to ibm-semeru-runtimes:open-jdk-25.0.3.0-jre-noble (OpenJDK 25). No action is required.

Spring Boot 4 and Jackson 3

PowerAuth Cloud has been migrated to Spring Boot 4 and Jackson 3.