Migration from 2.2.x to 2.3.x
This guide contains instructions for migration from PowerAuth Cloud version 2.2.x to version 2.3.0.
Device Public Keys in Registration APIs
PowerAuth Cloud 2.3.0 introduces an opt-in feature to retrieve device public keys from registrations via the registration detail and list endpoints.
API Changes
Two registration endpoints now accept an optional includeDevicePublicKeys query parameter (default: false):
GET /v2/registrations/{registrationId}GET /v2/registrations
When includeDevicePublicKeys=true, non-CREATED registrations in the response include a devicePublicKeys map containing public keys by key type (KeyType name to normalized Base64 encoding). By default, the map is omitted, so existing responses remain unchanged.
Database Changes
Liquibase is used for automated migration of database schema during startup of PowerAuth Cloud backend components.
Configuration Updates
Loopback Interface Binding
The internal Tomcat connectors are now bound to the loopback interface (127.0.0.1) by default. Previously, they were bound to all network interfaces (0.0.0.0).
If you rely on the previous behavior, set the following environment variable:
TOMCAT_BIND_ALL_INTERFACES=true
[!WARNING] The internal ports bypass the nginx reverse proxy and are not secured by it. Applications served on them (e.g., PowerAuth Server or Push Server) may not require authentication. Restrict network access to trusted clients only.
The default is false, i.e. only loopback binding is enabled.