Activation Transfer

PowerAuth server allows the transfer of existing activations.

Activation Transfer Configuration

To enable activation transfer, an entry with the key activation_transfer must exist in the table pa_application_config. This configuration is exposed to the Enrollment Server, and it will manifest itself in the response Activation Spawn endpoint, issuing an activation code.

Mind that this table supports encryption, see Encrypting Records in Database for details.

Required Configuration

  • allowedTargetApplicationIds - Mandatory. List of application IDs to which the activation is allowed to be transferred.
  • type - Mandatory. Type of activation transfer, SPAWN and MOVE are supported.
  • initialFlags - Optional. List of flags to be set on the child activation.

The configuration is exclusive. The allowed target application ID must not be specified for more than one type of activation transfer.

If the MOVE type is specified, the parent activation will be removed, after the child activation status is changed to ACTIVE.

Example

The value of config_values column may look like this:

[
  {
    "allowedTargetApplicationIds": [
      "application-1",
      "application-2"
    ],
    "type": "SPAWN",
    "initialFlags": ["my-custom-flag"]
  },
  {
    "allowedTargetApplicationIds": [
      "application-3"
    ],
    "type": "MOVE"
  }
]
Last updated on Oct 14, 2025 (08:53) Edit on Github Send Feedback
Search

develop

PowerAuth Server