Migration from 0.24.0 to 1.0.0

This guide contains instructions for migration from PowerAuth Server version 0.24.0 to version 1.0.0.

Bouncy Castle Library Update to Version 1.67

Bouncy Castle library has been updated to version 1.67. The newest version of Bouncy Castle library can be downloaded from: https://www.bouncycastle.org/download/bcprov-jdk15on-167.jar

Installation on Java 8:

• Update Bouncy Castle library the lib/ext folder of the Java runtime

Installation on Java 11:

• Tomcat: update Bouncy Castle library in CATALINA_HOME/lib
• JBoss / Wildfly: update Bouncy Castle library global module
• Other web containers: follow instructions for installing a global library for the web container

For more details about installation of the library see Installing Bouncy Castle.

Database Changes

Following DB changes occurred between version 0.24.0 and 1.0.0:

• Table pa_activation - added column flags.
• Table pa_application - added column roles.
• Table pa_application_callback - added column attributes.
• Table pa_recovery_config - added column postcard_priv_key_encryption.

Migration script for Oracle:

ALTER TABLE "PA_ACTIVATION" ADD "FLAGS" VARCHAR2(255 CHAR);
ALTER TABLE "PA_APPLICATION" ADD "ROLES" VARCHAR2(255 CHAR);
ALTER TABLE "PA_APPLICATION_CALLBACK" ADD "ATTRIBUTES" VARCHAR2(1024 CHAR);
ALTER TABLE "PA_RECOVERY_CONFIG" ADD "POSTCARD_PRIV_KEY_ENCRYPTION" NUMBER(10,0) DEFAULT 0 NOT NULL;

Migration script for MySQL:

ALTER TABLE `pa_activation` ADD `flags` varchar(255);
ALTER TABLE `pa_application` ADD `roles` varchar(255);
ALTER TABLE `pa_application_callback` ADD `attributes` text NOT NULL;
ALTER TABLE `pa_recovery_config` ADD `postcard_priv_key_encryption` int(11) NOT NULL DEFAULT 0;

Migration script for PostgreSQL:

ALTER TABLE "pa_activation" ADD "flags" VARCHAR(255);
ALTER TABLE "pa_application" ADD "roles" VARCHAR(255);
ALTER TABLE "pa_application_callback" ADD "attributes" VARCHAR(1024);
ALTER TABLE "pa_recovery_config" ADD "postcard_priv_key_encryption" INTEGER DEFAULT 0 NOT NULL;

New REST Client and SOAP Client Updates

We introduced a new REST client in release 1.0.0 and recommend migrating to the REST client in case you use the SOAP client, the provided functionality is identical.

The SOAP clients for Spring and Java EE are still available, however these clients are marked as deprecated, and they will be removed in a future release.

Marshaller context path setting have been updated due to the migration of client model classes and due to company name change to Wultra.

Original context path setting:

marshaller.setContextPath("io.getlime.powerauth.soap.v3");

New context path setting:

marshaller.setContextPath("com.wultra.security.powerauth.client.v3");

The version 2 context path package has changed the same way, so you will need to update the version 2 path in case you still use the version 2 interface, too.

In your client projects, use the new com.wultra.security.powerauth.client packages for the client model classes.

For more information about the new REST client, see the REST client documentation

Migration of PowerAuth Clients to REST Interface

PowerAuth clients in PowerAuth stack use the REST interface in version 1.0.0. Previous versions of PowerAuth components used the SOAP interface. This change needs to be reflected in configuration property powerauth.service.url in all components which use the PowerAuth client.

Property value before migration: powerauth.service.url=http://[server]:[port]/powerauth-java-server/soap

Property value after migration: powerauth.service.url=http://[server]:[port]/powerauth-java-server/rest

Following components use the PowerAuth client:

• PowerAuth Admin
• PowerAuth Web Flow
• PowerAuth Push Server
• PowerAuth Enrollment Serer

Make sure to update the powerauth.service.url property in each of these components.