AAL2ProcGenActivationDataRndKeyRpl
  • 22 Jan 2025
  • 2 Minutes à lire
  • Sombre
    Lumière
  • PDF

AAL2ProcGenActivationDataRndKeyRpl

  • 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 AAL2ProcGenActivationDataRndKeyRpl (
                                    aat_byte        *InReply,
                                    aat_int32        ReplySize,
                                    TDigipassBlob   *DPData [8],
                                    aat_ascii       *aSerialNumberSuffixOut,
                                    aat_ascii       *aXFADOut,
                                    aat_ascii       *aXERCOut);

Description

This function processes a reply from the HSM after to a command generated with the AAL2GenGenActivationDataRndKeyCmd function.

The software Digipass activation data with random key generation on the HSM is the same functionality as available with the Authentication Suite Server SDK Software Digipass Activation Service. For information on the associated function (AAL2GenActivationDataRndKey), refer to the Authentication Suite Server SDKC-C++ Programmer's Guide.


  • The generated [encrypted] activation code (or [X]FAD) will be related to the new software Digipass key, and the authenticator application BLOBs will be updated with the new software Digipass key.
  • Buffers must be mandatorily allocated for aSerialNumberSuffixOut, aXFADOut, and aXERCOut.
  • 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 (AAL2ProcGenActivationDataRndKeyRpl)
TypeNameUseDescription
aat_byte *InReplyI

Up to 5845 bytes that contain the GENERATE ACTIVATION DATA RND KEY command type and the output data from the generate activation data random key function on the HSM:

  • Command type - 2 bytes
  • An authenticator application BLOB - 192 bytes (x 1 to 8)
  • Application count - 4 bytes
  • Return code - 4 bytes
  • Serial number suffix - up to 14 characters
  • Activation code or [X]FAD - up to 4142 characters
  • Event reactivation counter - up to 91 characters

Plus 52 bytes Authentication Suite Server SDK internal use.

aat_int32ReplySizeIThe length of the InReply message.
TDigipassBlob * [8]DPDataO

Array of authenticator application BLOB pointers. Upon return from the function call, this BLOB must be rewritten to the application database to reflect changes.

aat_ascii *aSerialNumberSuffixOutO

String of up to 14+1 null-terminated digits representing the last 7 digits of the Digipass serial number.

14+1 null-terminated digits in case of software Digipass authenticators based on the Digipass SDK prior to version 4.0 (SN- suffix formatted with inserted 0).

7+1 null-terminated digits in case of software Digipass authenticators based on the Digipass SDK 4.0 or higher.

The aSerialNumberSuffixOut buffer must have at least 15 bytes allocated.

aat_ascii *aXFADOutO

String of up to 4142+1 characters, null-terminated. This parameter holds either the [encrypted] activation code (in case of offline mode) or the [encrypted] full activation data ([X]FAD) (in case of online mode).

The aXFAD buffer must have at least 4143 bytes allocated.

aat_ascii *aXERCOutO

String of up to 91+1 characters, null-terminated.

This parameter holds either the event reactivation counter (ERC) (if both the SharedData and Alea parameters are set to NULL in the cmd function) or the encrypted event reactivation counter (XERC) (if the SharedData and/or Alea parameters are not set to NULL in the cmd function).

The aXERCOut buffer must have at least 92 bytes allocated.

Return codes

  Table: Return codes (AAL2ProcGenActivationDataRndKeyRpl)
CodeMeaningCodeMeaning
0Success573Serial number suffix not decimal
147Invalid ActivationCode pointer574Invalid serial number prefix in SV
164Invalid serial number suffix pointer575Invalid event reactivation counter pointer
272Invalid wrapped key576Digipass data does not match with SV
412Invalid checksum (software)577HSM random generation failed
413Invalid Base64 format579Alea or shared data not allowed
414Invalid checksum (HSM)701Invalid input buffer pointer
510Invalid Digipass data pointer807Serial number not equal
543Activation code generation not supported808Invalid application count value
545Invalid static vector length910Invalid HSM command in reply
546Invalid Activation Code format912HSM invalid BLOB status
547Alea is too long913Invalid HSM key property
548Shared data too long951Invalid HSM key type for HSM decryption
549Alea + shared data too long1009Invalid TLV total length
567Invalid activation flags value1018Invalid TLV item pointer
568Invalid DP+ application in Digipass data1019Missing mandatory TLV item
569Invalid application name in Digipass data1025Data buffer too small
570Invalid static vector version1103Unlock Version 2 not supported
571Invalid application index in static vector1118Unsupported BLOB
572Missing application key type in static vector-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