Migration from 2.0.x to 2.1.x
This guide contains instructions for migration from PowerAuth Enrollment Server version 2.0.x to version 2.1.0.
Database Changes
For convenience, you can use liquibase for your database migration.
For manual changes use SQL scripts:
Add Column subject_id to audit_log table
Added a new indexed column subject_id holding an identifier linking the audit record to an entity it is related to (e.g. user ID for user-related audit records).
The auditing tables may be already updated in your database schema if the database schema is not separated for different PowerAuth applications. In case the column audit_log.subject_id and its index audit_log_subject_id_idx are already present, you can safely skip this migration step.
Last updated on Apr 01, 2026 (08:02)
Edit on Github
Send Feedback