Migration from 2.0.x to 2.1.x

This guide contains instructions for migration from PowerAuth Cloud version 2.0.x to version 2.1.0.

REST API Updates

GET /v2/registrations/{registrationId}

The response has been extended with:

• a new protocol attribute indicating the protocol used for the registration (possible values are powerauth and fido2)
• a new externalId attribute containing the external ID associated with the registration

GET /v2/registrations

Each registration returned by the endpoint has been extended with:

• a new protocol attribute indicating the protocol used for the registration (possible values are powerauth and fido2)
• a new externalId attribute containing the external ID associated with the registration

POST /v2/fido2/assertions/challenge

The endpoint has been modified:

• a new optional attribute userId is accepted, allowing to specify the user for which the assertion challenge is generated
• the externalId attribute is no longer mandatory
• the response has been extended with the allowCredentials attribute (credentials associated with the assertion), using the following structure:

    {
      "allowCredentials": [
        {
          "credentialId": "string",
          "type": "string",
          "transports": [
            "string"
          ]
        }
      ]
    }
  

POST /v2/fido2/assertions

The appId attribute used to verify the challenge can be approved by given application is no longer mandatory. If not present, the user ID retrieved from response.userHandle is used to determine the application ID.

POST /admin/applications/{id}/push/hms

The appId attribute in the request body is no longer required and will be ignored if present. The path parameter is used exclusively.