Documentation Index

Fetch the complete documentation index at: https://docs.onespan.com/llms.txt

Use this file to discover all available pages before exploring further.

AAL2ProcGenMessageActivation1Rpl

Prev Next

Availability: Authentication Suite Server SDK 4.0.2 and later

Service: Digipass Multi-Device Activation

Function Prototype

aat_int32 AAL2ProcGenMessageActivation1Rpl(
                                 aat_byte        *InReply,
                                 aat_int32        ReplySize,
                                 TDigipassBlob   *DPMAData,
                                 aat_ascii       *Activation1Message,
                                 aat_ascii       *Activation1MessageLength);

Description

This function processes a reply from the HSM to an Activation Message 1 generation command which has been generated with AAL2GenGenMessageActivation1Cmd.

The Activation Message 1 generation on the HSM is identical to the functionality available with the Software Digipass Multi-Device Activation service.

This function serializes an important amount of data. The InReply buffer must be allocated with a sufficient size. For more information about the allocation of the Cmd and InReply buffers, refer to Cmd and InReply buffers allocation.

Parameters

  Table: Parameters (AAL2ProcGenMessageActivation2Rpl)
TypeNameUseDescription
aat_byte *InReplyI

Contains the GENERATE ACTIVATION MESSAGE 1 command type and output data to the function on the HSM.

aat_int32ReplySizeI

The length of the InReply message.

TDigipassBlobDPMADataO

Digipass master activation application BLOB of the Digipass serial number license that will be used for the activation. Upon return from the function call, this BLOB must be rewritten to the application database to reflect changes.

aat_ascii *Activation1MessageO

String of up to 4234+1 hexadecimal characters, null-terminated. It contains the Activation Message 1 necessary during the activation process of the Digipass instances of a particular license, plus the public key HMAC.

aat_int32 *Activation1MessageLengthI/O

In input, this parameter must indicate the size of the allocated buffer for the Activation1Message parameter (recommended 4235 bytes).

In output, this parameter indicates the length of the Activatin1Message string (without the null-terminated character).

Return codes

  Table: Return codes (AAL2ProcGenMessageActivation2Rpl)
CodeMeaningCodeMeaning
0Success1271Invalid activation message length pointer
272Invalid wrapped key1272Invalid message body type
412Invalid checksum (software)1274Invalid message protocol version
413Invalid Base64 format1275Invalid message protection type
414Invalid checksum (HSM)1285Master key derivation failed
537Invalid static vector pointer1288Invalid serial number prefix
545Invalid static vector length1289Invalid serial number suffix
570Invalid static vector version1290Invalid sequence number pointer
571Invalid application index in static vector1291Invalid application count pointer
574Invalid serial number prefix in SV1292Sequence number threshold reached
701Invalid input buffer pointer1293Invalid sequence number
807Serial number not equal1294Digipass key derivation failed
910Invalid HSM command in reply1295Invalid Digipass instance SM application in static vector
912HSM invalid BLOB status1296Key wrapping failed
913Invalid HSM key property1297Invalid static vector
917Key type inconsistent1298Invalid Digipass instance application in static vector
951Invalid HSM key type for HSM decryption1302AES CTR encryption failed
1000Function does not support EMV-CAP1310Invalid payload key type
1009Invalid TLV total length1311Null Digipass data
1018Invalid TLV item pointer1312Null serial number
1019Missing mandatory TLV item1313Null authentication mode
1025Buffer too small1314Null token type
1118Unsupported BLOB1317Secure Channel supported. Payload key BLOB is mandatory
1264Invalid master application1318Secure Channel not supported. Payload key BLOB has to be NULL or empty string
1265Invalid master application data pointer1332Activation 2 not supported
1267Invalid message vector length1335Invalid payload key type in payload key data
1268Invalid message vector version1336Inconsistent payload key type between payload key data and message vector
1270Invalid activation message pointer-1501Memory allocation failed