AAL2ProcGenMessageActivation2Rpl
  • 22 Jan 2025
  • 3 Minutes à lire
  • Sombre
    Lumière
  • PDF

AAL2ProcGenMessageActivation2Rpl

  • Sombre
    Lumière
  • PDF

The content is currently unavailable in French. You are viewing the default English version.
Résumé de l’article

Function Prototype

aat_int32 AAL2ProcGenMessageActivation2Rpl(
                                 aat_byte        *InReply,
                                 aat_int32        ReplySize,
                                 TDigipassBlob   *DPMAData,
                                 aat_int32       *pSeqNum,
                                 aat_ascii        TokenType[6],
                                 aat_int16       *Appl_count,
                                 aat_ascii        Serial_Appli [8][23],
                                 aat_ascii        AuthMode [8][3],
                                 TDigipassBlob    DPData,
                                 aat_ascii       *Activation2Message,
                                 aat_ascii       *Activation2MessageLength);

Description

This function processes a reply from the HSM to a Activation Message 2 generation command which has been generated with AAL2GenGenMessageActivation2Cmd.

The Activation Message 2 and Digipass instance generation on the HSM is identical to the functionality available with the Authentication Suite Server SDK Software Digipass Multi-Device Activation Service. For information on the associated functions, refer to the Authentication Suite Server SDK C-C++ Programmer's Guide.

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

A string of up to 2195 bytes that contain the GENERATE MESSAGE ACTIVATION2 command type and the output data from the Generate Message Activation2 function on the HSM:

  • Command type - 2 bytes
  • Digipass Master Activation application BLOB - 192 bytes
  • Sequence Number - 4 bytes
  • Digipass TYPE - 6 characters
  • Application Count - 2 bytes
  • Serial Application - 23 characters (x1 to 8)
  • Authentication Mode - 3 characters (x1 to 8)
  • An authenticator application BLOB - 192 bytes (x1 to 8)
  • Activation Message 2 - 109 characters
  • Activation Message 2 Length - 4 bytes
  • Return code - 4 bytes

Plus 128 bytes for Authentication Suite Server SDK internal use.

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_int32 *pSeqNumO

Contains in output the sequence number of the generated Digipass instance (from 1 to 99).

aat_ascii[6]TokenTypeO

An output string of 5+1 characters, null-terminated. It contains the Digipass type name given to the Digipass instance. Will return a Digipass type of the form TYPxx with xx representing the device type coded on two decimal digits e.g. TYP07.

aat_int16 *Appl_countO

Number of Digipass applications returned. Points to a short integer where the function returns the number of applications found.

aat_ascii[8][23]Serial_AppliO

Set of up to 8 x 22+1 character strings, null-terminated, each composed of the 10-character license serial number concatenated with the 12-character application name. Each array entry represents the logical instance of a Digipass cryptographic application with its unique secrets and parameters. The application name part will end with the sequence number coded on two decimal digits e.g. APPL1    03.

aat_ascii[8][3]AuthModeO

Set of up to 8 x 2+1 character strings, null-terminated. Defines each returned authenticator application authentication mode.

RO: Response-Only

CR: Challenge/Response

SG: Signature

MM: Multi-Mode

UL: Unlock V2

Signature-mode devices may also be used for Challenge/Response authentication if they are programmed to accept a single input data field.

TDigipassBlob[8]DPDataO

Up to 8 authenticator application BLOBs of the Digipass instance. Upon return from the function call, these BLOBs must be written to the application database.

aat_ascii *Activation2MessageO

String of up to 124+1 hexadecimal characters, null-terminated. It contains the Activation Message 2 which is necessary during the activation process to provision the Digipass keys and the payload key to the Digipass device.

aat_int32 *Activation2MessageLengthI/O

In input, this parameter must indicate the size of the allocated buffer for the Activation2Message parameter (recommended 125 bytes). In output, this parameter indicates the length of the Activation2Message 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

Cet article vous a-t-il été utile ?

Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.
ESC

Ozzy, facilitant la découverte de connaissances grâce à l’intelligence conversationnelle