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

AAL2VerifySignatureEx

  • 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 AAL2VerifySignatureEx (
                                 TDigipassBlob*   DPData,
                                 TKernelParms*    CallParms,
                                 aat_ascii*       Signature,
                                 aat_ascii*       SignedDataFields [8][20],
                                 aat_int32        FieldCount,
                                 aat_int32        DeferredSignatureData
                                 aat_ascii*       ConfirmationCode,
                                 aat_ascii*       ConfirmationCodeLength);

Description

This function is an extension of AAL2VerifySignature. The functionality is identical except for the additional feature of integrating the confirmation code.

Signature confirmation code specifics

By facilitating a two-way authentication process, this feature allows a client to back-authenticate the server that validates the signature. The server validates the user's signature and returns a confirmation code with which the user can be sure that the authentication happened on the correct server.

With Digipass 110, AAL2VerifySignatureEs must be used instead of AAL2VerifySignatureEx.

Parameters

Table: Parameters (AAL2VerifySignatureEx)
TypeNameUseDescription
TDigipassBlob *DPDataI/Oauthenticator application BLOB. Upon return from the function call, this BLOB must be rewritten to the application database to reflect changes.
TKernelParms *CallParms IStructure of runtime parameters to use during this function call.
aat_ascii *SignatureIString of up to 17 numeric characters, left-justified, null-terminated, or right-padded with spaces.
aat_ascii [8][20]SignedDataFieldsI

Array of 8 left-justified, null-terminated, or space-padded strings of max. 20 characters. This parameter holds the 8 possible data fields that are entered into the Digipass authenticator to generate a signature. The Digipass data fields are limited to 16 decimal, hexadecimal, or alphabetic characters.

aat_int32 *FieldCountINumeric value from 1 to 8 indicating the number of data fields to use from the SignedDataFields array.
aat_int32 *Deferred signature dataI
  • Must be 0 if signature is validated in online mode (OnlineSG=1 or 2).
  • If signature is validated in offline mode with OnlineSG=0, this parameter can receive the Digipass date of the signature generation (number of elapsed seconds since January 1, 1970) or 0. (With 0, the current time is used.)

    If this parameter is >0, the filled parameter must be the Digipass time, not the host time.

  • If the signature is validated in offline mode with OnlineSG=3, this parameter must receive counter of the Digipass instance used for the signature generation.
aat_ascii *Confirmation codeOString of up to 17 numeric or hexadecimal characters, left-justified, null-terminated, or right-padded with spaces. This is the confirmation code generated by Authentication Suite Server SDK (recommended buffer size is 18 bytes).
aat_int32 *Confirmation CodeLengthOPointer to a long integer that indicates the length of the generated confirmation code.

Return codes

Table: Return codes (AAL2VerifySignatureEx)
CodeMeaningCodeMeaning
0Success510Invalid Digipass data pointer
10001Success with context warning*1103Unlock Version 2 not supported
10002Success with user warning*1116Response check digit not allowed
10003Success with user & context warning*-103Data field check digit wrong
10004Success with platform warning*-105Challenge minimum length not allowed
10005Success with platform & context warning*-106Challenge maximum length not allowed
10006Success with platform & user warning*-107Challenge number wrong
10007Success with platform & user & context warning*-108Challenge character invalid
1Signature not verified-201Response length out of bounds
132Unsupported token type1117Challenge check digit not allowed
139Invalid signature pointer1118Unsupported BLOB
141Invalid field count-101Data field too short
148Invalid data field pointer-202Response too short
203Sign error threshold reached-203Response too long
204Duplicate signature found-102Data field too long
205Inactive days reached-204Response check digit wrong
206Chronological signature error-205Response character not decimal
207Deferred signature not allowed with OnLineSG not Null-206Response character not hexadecimal
208Application disabled-207Response character set not specified
412Invalid checksum-1501Memory allocation failed
413Invalid Base64 format  

* Specific score-based authentication codes; for more information, refer to Score-based Digipass.


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

What's Next
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