AAL2ProcProcMessageInformationRpl

  • Published on Jul 9, 2025
  • 1 minute(s) read
Prev Next

Function Prototype

aat_int32 AAL2ProcProcMessageInformationRpl(
                                         aat_byte   *InReply,
                                         aat_int32   ReplySize,
                                         aat_ascii  *InformationBody,
                                         aat_int32  *InformationBodyLength);

Description

This function processes a reply from the HSM to an information message processing command which has been generated with AAL2GenProcMessageInformationCmd.

The information message processing on the HSM is identical to the functionality available with the Authentication Suite Server SDK Authentication Suite Server SDK Software Digipass Secure Channel 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 (AAL2ProcProcMessageInformationRpl)
TypeNameUseDescription
aat_byte *InReplyI

Up to 1046 bytes that contain the INFORMATION MESSAGE PROCESSING command type and the output data from the response message processing function on the HSM:

  • Command type - 2 bytes
  • Information Body - 1024 characters
  • Information Body Length - 4 bytes
  • Return code - 4 bytes

Plus 12 bytes for Authentication Suite Server SDK internal use.

aat_int32ReplySizeIThe length of the InReply message.
aat_ascii *InformationBodyO

String of up to 1024+1 hexadecimal characters, null-terminated. In case of a successful operation, this parameter contains the clear response body extracted from the InformationMessage.

aat_int32 *InformationBodyLengthI/O

In input, this parameter must indicate the size of the allocated buffer for the InformationBody parameter (recommended are 1025 bytes).

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

Return codes

  Table: Return codes (AAL2ProcProcMessageInformationRpl)
CodeMeaningCodeMeaning
0Success1349

Invalid response body pointer

701Invalid input buffer pointer1350Invalid response body length pointer
910

Invalid HSM command in reply

1351

Response body buffer too small

913

Invalid HSM key property

1352Nonces are not equal
917

Key type inconsistent

1353

Payload key BLOB is mandatory

951Invalid HSM key type for HSM decryption1354

Invalid request message type

1000Function does not support EMV-CAP1355

Invalid response message type

1009

Invalid TLV total length

1361

Invalid authentication tag

1018

Invalid TLV item pointer

1362

Invalid response message error length

1019

Missing mandatory TLV item

5001[1]

Unsupported request message protocol version

1025

Buffer too small

5002[1]

Unsupported request message type

1267

Invalid message vector length

5003[1]

Unsupported request message protection type

1268

Invalid message vector version

5004[1]

Invalid request message length

1342

Invalid response message length

5005[1]

Invalid request message; character not hexadecimal

1344

Invalid request message length

5006[1]

Incorrect serial number in the request message

1345

Invalid request message protection type

5007[1]

Invalid authentication tag in the request message

1346

Invalid message response protection type

-1501Memory allocation failed
  1. Specific request error message codes