DPX Import Service

Description

The DPX Import Service groups the functionalities responsible for the import process, which consists in extracting the Digipass data from the DPX file. The import process is divided into four mandatory steps:

1. Initialization. The DPX file is opened using the file name and the software transport key. The software transport key is a 64-digit key that encrypts the sensitive data in the DPX file through an AES mechanism.
2. Digipass data extraction. The Digipass type, serial number, application names, authentication modes, and BLOBs are retrieved for the applications of a Digipass authenticator. The Digipass serial number is a string of ten alphanumeric characters on the back of the hardware authenticator. The Digipass type is the model of the authenticator, as for example Digipass GO 1, Digipass 300, or MOB2T.
3. Digipass data storage. The Digipass data obtained in the course of the previous step is written into the database.
4. Finalization. The DPX file is closed.

(OPTIONAL 1) In addition to this standard import process common to all Digipass authenticators, a step must be added to extract the static vector from the DPX file for certain categories of Digipass authenticators. The static vector is a string containing parameter settings for the Digipass activation. The presence of the static vector in the DPX file and its usage is applicable only to the following categories of Digipass authenticators:

• Software Digipass compliant with standard activation (in the context of single-device licensing; for more information, see Single-device licensing).
• Software or hardware Digipass authenticators compliant with multi-device activation (in the context of multi-device licensing; for more information, see Multi-device licensing).

(OPTIONAL 2) In addition to this standard import process common to all Digipass authenticators, a step must be added to extract the message vector from the DPX file for certain categories of Digipass authenticators. The message vector is a string containing configuration settings for the message generation. The presence of the message vector in the DPX file and its usage is applicable only to the following category of Digipass authenticators:

• Software or hardware Digipass authenticators compliant with multi-device activation (in the context of multi-device licensing; for more information, see Multi-device licensing).
• Software or hardware Digipass authenticators that support operations based on the Secure Channel protocol; for more information, see Single-device licensing and Multi-device licensing).

(OPTIONAL 3) In addition to this standard import process common to all Digipass authenticators, additional data must be retrieved for each Digipass data extraction in case of software or hardware Digipass authenticators compliant with multi-device activation: the sequence number threshold and the activation vector. The sequence number threshold is an integer indicating the number of instances that can be created from a certain Digipass license; the activation vector is a string containing encrypted activation data for a certain Digipass license. The presence of the sequence number threshold and activation vector data in the DPX file and their usages is applicable only to the following category of Digipass authenticators:

• Software or hardware Digipass authenticators compliant with multi-device activation (in the context of multi-device licensing; for more information, see Multi-device licensing).

(OPTIONAL 4) In addition to this standard import process common to all Digipass authenticators, additional data must be retrieved for each Digipass data extraction in case of hardware Digipass authenticators based on the single-device licensing model and using the Secure Channel protocol: the payload key BLOB. The payload key BLOB (if any) contains a Secure Channel payload key that will be involved for operations based on the Secure Channel protocol. The presence of the payload key BLOB in the DPX file and its usage is applicable only to the following category of Digipass authenticators:

• Hardware Digipass authenticators based on the single-device licensing model (provisioned in factory) which support operations based on the Secure Channel protocol; for more information, see Single-device licensing.

Functionalities

To import Digipass data from a DPX file, the DPX Import Service of Authentication Suite Server SDK relies on the Digipass data import functionalities (see Figure: DPX import process workflow).

Workflow

Figure:  DPX import process workflow