AuthMinder supports partial password authentication, if you enable this feature, then the user will be challenged to enter the characters in different positions of the password. For example, if the password is casablanca!, then the user can be asked to enter the characters in positions 1, 3, and 8, which would be csn.
The following topics for performing partial password authentication are covered in this section:
For partial password authentication, you must prepare the following request messages:
The GetPasswordChallengeRequestMessage is used to fetch the password challenge for the user from AuthMinder Server. The following table lists the elements of this message.
|
Element |
Mandatory |
Description |
|---|---|---|
|
clientTxnId |
No |
Specifies the unique transaction identifier that the calling application can include. This identifier helps in tracking the related transactions. |
|
userName |
Yes |
The unique identifier of the user. |
|
orgName |
No |
The organization name to which the user belongs to. |
|
additionalInput/pairs |
No |
AuthMinder’s additionalInput element enables you to set additional inputs if you want to augment AuthMinder’s authentication capability by specifying additional information. In such cases, you need to set the extra information in name-value pairs.
Some of the pre-defined additional input parameters include:
|
The VerifyPasswordRequestMessage is used to verify the password provided by the users. The following table lists the elements of this message.
|
Element |
Mandatory |
Description |
|---|---|---|
|
clientTxnId |
No |
Specifies the unique transaction identifier that the calling application can include. This identifier helps in tracking the related transactions. |
|
userName |
Yes |
The unique identifier of the user. |
|
orgName |
No |
The organization name to which the user belongs to. |
|
password |
Yes |
The password provided by the user. |
|
tokenType |
No |
The type of authentication token that is expected from AuthMinder Server after successful authentication. See "Verifying the Authentication Tokens" for more information. |
|
challengeID |
No |
The unique identifier of the challenge returned by AuthMinder Server. Note: The challengeID is required for complete partial password verification. |
|
additionalInput/pairs |
No |
AuthMinder’s additionalInput element enables you to set additional inputs if you want to augment AuthMinder’s authentication capability by specifying additional information. In such cases, you need to set the extra information in name-value pairs.
Some of the pre-defined additional input parameters include:
|
To perform partial password authentication:
This operation returns VerifyPasswordResponseMessage, which provides the transaction details, credential details, and token information.
Following are the response messages that are returned as part of QnA authentication:
For successful transactions, the response message, GetPasswordChallengeResponseMessage returns the elements explained in the following table. These elements are included in the SOAP body. If there are any errors, then the Fault response is included in the SOAP body. See appendix, "Error Codes" for more information on the SOAP error messages.
|
Element |
Description |
|---|---|
|
positions |
The password positions for which the user has to provide the password characters. |
|
challengeID |
The unique identifier of the challenge returned by AuthMinder Server. |
|
transactionDetails |
Contains the following transaction details:
|
For successful transactions, the response message, VerifyPasswordResponseMessage returns the elements explained in Verify Signed Challenge Response Message in Step 2: ArcotID PKI Authentication. These elements are included in the SOAP body. If there are any errors, then the Fault response is included in the SOAP body. See appendix, "Error Codes" for more information on the SOAP error messages.
|
Copyright © 2013 CA.
All rights reserved.
|
|