Skip to main content

Identity Provider - A-Trust QES (EU-Identity)

The activation process consists of the following steps:

  1. Identify the customer and create an identity record

    The Identity Provider (or the initiating system) performs the identification of the customer. Once the customer's identity has been verified, the relevant identification data is transmitted to the identity interface in the form of an identity record.

  2. Receive the activation URL

    The identity interface returns an activation URL. The customer can then be redirected to this URL.

  3. Complete the EU-Identity activation

    The customer completes the EU-Identity activation process.

  4. Optional redirection

    After the activation process has been completed, the customer may optionally be redirected to a previously provided page of the Identity Provider.

Requried documentation and interfaces​

Before integrating the activation flow, ensure that your application is able to create an identity record and submit it to the identity interface. The identity record contains the information required to identify the customer and initiate the activation process.

A detailed description of the required request format, the identity record structure, authentication requirements, and the available API endpoints can be found in the Identity interface and Identity record documentation. It is recommended to review this documentation before implementing the activation workflow.

Optional: Redirect After Activation​

Identity interface and Identity record​

Refer to the Identity interface and Identity record documentation for details on creating an identity record and submitting it to the identity interface.

The activation flow can optionally redirect the user back to the Identity Provider after the process has completed. To enable this behavior, provide the Response\Success and Response\Error parameters when initiating the activation.

If neither parameter is provided, the activation flow ends on the default completion page and no redirect to the Identity Provider is performed.

Optional: Timestamp​

The Timestamp API can be used to create a timestamp as part of the signing process. This step is optional and may be used if required by your application's workflow.

Refer to the Timestamp documentation for implementation details.

Optional: Qualified Seal​

The a.sign seal qualified API can be used to apply a qualified electronic seal to the resulting document as part of the signing process.

Refer to the a.sign seal qualified documentation for implementation details.