Migration from 1.9.x to 2.0.x

This guide contains instructions for migration from PowerAuth Enrollment Onboarding Server version 1.9.x to version 2.0.0.

Database Changes

For convenience, you can use liquibase for your database migration.

For manual changes use SQL scripts:

• PostgreSQL script
• Oracle script

Onboarding Process Configuration

A new table es_onboarding_process_configuration has been added. Also added a foreign key process_config_id to the table es_onboarding_process.

You have to insert at least one row into the table es_onboarding_process_configuration, and configure property enrollment-server-onboarding.onboarding-process.default-type (or ENV ONBOARDING_PROCESS_DEFAULT_TYPE) to work as a default process type.

Onboarding Process

Added a new column target_activation_id to the table es_onboarding_process.

REST API Changes

Onboarding Start

The following changes were made to the onboarding start endpoint:

• Added a new optional request field processType to specify which onboarding process type should be used.
• Added a new optional response field activationCode to return activation code and a mandatory field activationType.

External Onboarding Services Changes

Process Type

For external onboarding services, the processType field has been added to the request body.

Configuration

OTP Configuration

The property enrollment-server-onboarding.identity-verification.otp.enabled has been removed in favor of the database changes, see the table es_onboarding_process_configuration.

Documents configuration

Following configuration properties were removed:

enrollment-server-onboarding.document-verification.required.primaryDocuments
enrollment-server-onboarding.document-verification.required.count

New logic works in this way:

Field documents.totalRequiredDocumentsCount - specifies min count of unique document types required for verification.

Field documents.groups - group specifies more rules for set of document types:

• requiredDocumentsCount - specifies min count of unique document types required from this group
• items - set of documents. Each item specifies document type and sideCount

EXAMPLE:

{
  "documents": {
    "totalRequiredDocumentsCount": 2,
    "groups": [
      {
        "requiredDocumentsCount": 1,
        "items": [
          {
            "type": "ID_CARD",
            "sideCount": 2
          },
          {
            "type": "PASSPORT",
            "sideCount": 1
          }
        ]
      },
      {
        "requiredDocumentsCount": 0,
        "items": [
          {
            "type": "DRIVING_LICENCE",
            "sideCount": 1
          }
        ]
      }
    ]
  }
}

For this configuration in total at least 2 unique document types must be submitted for verification. Acceptable combinations:

• ID_CARD (2 sides) + PASSPORT (1 side)
• ID_CARD (2 sides) + DRIVING_LICENCE (1 side)
• PASSPORT (1 side) + DRIVING_LICENCE (1 side)