Function prototype
aat_int32 AAL2ConvTokenData (TKernelParms* CallParms,
aat_ascii* Old_Serial_No,
aat_ascii* Old_RecType,
aat_ascii* Old_Record,
aat_ascii* Serial_No,
aat_ascii* DIGIPASSType,
aat_ascii* AuthMode,
TDigipassBlob* DPData);
Description
This function may be used to convert existing legacy Digipass databases into the new TDigipassBlob BLOB so that existing Digipass devices can be used with the new validation functions.
Parameters
Table: Parameters (AAL2ConvTokenData) | Type | Name | Use | Description |
|---|
| TKernelParms * | CallParms | I | Structure of runtime parameters to use during this function call. |
| aat_ascii * | Old_Serial _No | I | Digipass serial number as expressed in the legacy format. |
| aat_ascii * | Old_RecType | I | Indicates which kind of legacy data format was used to store Old_Record. |
| aat_ascii * | Old_Record | I | Digipass data record in legacy format. If the function succeeds, this data will be migrated to the TDigipassBlob format in DPData. |
| aat_ascii * | Serial_No | O | String of 22 characters composed of the 10-digit Digipass device serial number concatenated with its 12-digit application name. Represents a logical instance of a Digipasscryptographic application with its unique secrets and parameters. It may be used as a search key to access your Digipass database. If the first character of this string is <> 0 (Binary Zero), you may pass the optional PGMSW key (recommended buffer size is 23 bytes). |
| aat_ascii * | DigipassType | O | String of 5 characters, indicates the physical Digipass device type. It may be used for information purposes or to determine which flashing pattern protocol to use to send data through the device's optical interface, if any. Possible values: - AKII
- AUTCD
- Digipass 100
- Digipass 300
- Digipass 500
- Digipass 600
- Digipass 700
- etc.
(Recommended buffer size is 6 bytes.) |
| aat_ascii * | AuthMode | O | String of two characters. Defines this authenticator application authentication mode. Possible values: - RO: Response-Only
- CR: Challenge/Response
- SG: Signature
- MM: Multi-Mode
- UL: Unlock V2 dedicated application
Signature-mode devices may also be used for Challenge/Response authentication if they support a single input data field (recommended buffer size is 3 bytes). |
| TDigipassBlob * | DPData | O | authenticator application BLOB. Upon return from the function call, this BLOB must be rewritten to the application database to reflect changes. |
Return codes
Table: Return codes (AAL2ConvTokenData) | Code | Meaning | Code | Meaning |
|---|
| 0 | Success | -508 | Token type not supported |
| 510 | Invalid Digipass data pointer | -509 | Response type not allowed |
| 511 | Invalid serial number pointer | -510 | Invalid record |
| 512 | Invalid AuthMode pointer | -511 | Wrong record CRC check |
| 513 | Invalid data record | -1501 | Memory allocation failed |
| 515 | Invalid Digipass type pointer | | |