This function is an extension of AAL2VerifyPassword. The functionality is identical except for the additional feature of integrating the return host code.
Return host code
By facilitating a two-way authentication process, this feature allows a client to back-authenticate the server that validates the dynamic password. The server validates the user's dynamic password and returns a host code with which the user can be sure that the authentication happened on the correct server. This function is particularly useful for web implementations.
Parameters
Table: Parameters (AAL2VerifyPasswordEx)
Type
Name
Use
Description
TDigipassBlob *
DPData
I/O
authenticator application BLOB. Upon return from the function call, this BLOB must be rewritten to the application database to reflect changes.
TKernelParms *
CallParms
I
Structure of runtime parameters to use during this function call.
aat_ascii *
Password
I
String of up to 17+24 numeric or hexadecimal characters, left-justified, null-terminated or right-padded with spaces. This is the dynamic password generated by the Digipass authenticator.
aat_ascii *
Challenge
I
String of up to 17 numeric or hexadecimal characters, left-justified, null-terminated, or right-padded with spaces. This parameter holds the challenge that was proposed to the user to generate the password to verify. If no challenge was generated, this parameter should be NULL.
aat_ascii *
ReturnHostCode
O
String of up to 17 numeric or hexadecimal characters, left-justified, null-terminated, or right-padded with spaces. This is the code generated by Authentication Suite Server SDK (recommended buffer size is 18 bytes).
aat_int32 *
ReturnHostCodeLength
O
Pointer to a long integer that indicates the length of the generated return host code.
Return codes
Table: Return codes (AAL2VerifyPasswordEx)
Code
Meaning
Code
Meaning
0
Success
802
Change password mandatory
10001
Success with context warning*
803
New password too short
10002
Success with user warning*
804
New password too long
10003
Success with user & context warning*
1039
Invalid response length with DP algorithm
10004
Success with platform warning*
1040
Invalid host code length with DP algorithm
10005
Success with platform & context warning*
1103
Unlock Version 2 not supported
10006
Success with platform & user warning*
1116
Response check digit not allowed
10007
Success with platform & user & context warning*
1117
Challenge check digit not allowed
1
Code not verified
1118
Unsupported BLOB
2
Static password validation failed
-101
Challenge too short
130
Invalid response pointer
-102
Challenge too long
131
Missing required challenge
-103
Challenge check digit wrong
132
Unsupported token type
-105
Challenge minimum length not allowed
140
Challenge corrupted
-106
Challenge maximum length not allowed
201
Code replay attempt
-107
Challenge number wrong
202
Identification error threshold reached
-108
Challenge character invalid
205
Inactive days reached
-201
Response length out of bounds
208
Application disabled
-202
Response too short
412
Invalid checksum
-203
Response too long
413
Invalid Base64 format
-204
Response check digit wrong
510
Invalid Digipass data pointer
-205
Response character not decimal
600
Invalid Gordian root information
-206
Response character not hexadecimal
601
Invalid Gordian today information
-207
Response character set not specified
602
Invalid Gordian tomorrow information
-1501
Memory allocation failed
603
Invalid Gordian stimulus information
* Specific score-based authentication codes; see Section 7.1.2.3 Score-based DIGIPASS.
Cet article vous a-t-il été utile ?
Merci pour vos commentaires! Notre équipe vous répondra
