Auto-Generate PSKC Files

During initialization of all OATH slots, a PSKC file is generated in the PSKC folder where the tool runs. This PSKC file can be used to import into the back-end system.

As the tool runs, the file is updated every time the OATH slots are initialized or deleted for any device.

Below is the sample of a PSKC file encrypted using the AES 128-bit algorithm where two OATH slots (HOTP and TOTP) are configured for a device.

Note: There can be up to 3 key packages per file (one for each OATH slot). The file name is based on the CUID of the smart card with the .pskc extension (for example, 47900503364800151907.pskc as seen in the sample below).

Sample PSKC.xml: