The following table lists the response codes, reason codes, the cause for failure, and solution wherever applicable.
Response Code |
Reason Code |
Description |
Possible Cause for Failure |
||
---|---|---|---|---|---|
0
|
0 |
Operation completed successfully. |
N/A |
||
6100 |
Authentication succeeded, but the credential is in grace period. |
Action to Take: |
|||
6101 |
Authentication succeeded, but the credential is in warning period. |
Action to Take: |
|||
1000
|
0 |
Internal error. |
Possible Cause: |
||
2000 |
Database is not operational. |
Possible Cause: Solution: Possible Cause: Solution: |
|||
2001 |
Configuration is missing. |
Possible Cause: Solution: Possible Cause: Solution: |
|||
2002 |
Transaction ID generation failed. |
Possible Cause: Solution: |
|||
6004 |
Internal error. |
Possible Cause: |
|||
1001 |
0 |
Access is denied. |
Possible Cause: Solution: You must send the correct credential or authorization token while making the Web Service call. See chapter, "Managing Web Services Security" for more information. |
||
1050
|
0 |
Invalid parameter. |
Possible Cause: Solution: |
||
2050 |
Value of one of the parameters used in the operation is empty. |
Possible Cause: Solution: |
|||
2051 |
Length of one of the parameters used in the operation has exceeded the maximum allowed value. Tip: Length here refers to length of the parameter, for example password length. |
Possible Cause: Solution: |
|||
2052 |
Length of one of the parameters used in the operation is less than minimum allowed value. |
Possible Cause: Solution: |
|||
2053 |
Value of one of the parameters used in the operation exceeded the maximum allowed value. Tip: VALUE here refers to value of the parameter, for example ArcotID PKI Plain Key length. |
Possible Cause: Solution: |
|||
2054 |
Value of one of the parameters used in the operation is less than the minimum allowed value. |
Possible Cause: Solution: |
|||
2055 |
Value of one of the parameters used in the operation is invalid. |
Possible Cause: For example, the allowed values for user status are 0 and 1. If you set the value of this as 5, then you will get this error. Solution: |
|||
|
2056 |
Value of one of the parameters used in the operation contains invalid characters. |
Possible Cause: Solution: |
||
1050
|
2057 |
One of the parameters used in the operation does not meet the formatting requirements. |
Possible Cause: Solution: |
||
2058 |
The password has less number of alphabets than the minimum allowed value. |
Possible Cause: Solution: |
|||
2059 |
The password has less number of numeric characters than the minimum allowed value. |
Possible Cause: Solution: |
|||
2060 |
The password has less number of ASCII special characters than the minimum allowed value. |
Possible Cause: Solution: |
|||
2061 |
Parameter is not supported for this operation. |
Possible Cause: The parameter that is passed by the plug-in is not supported by the operation. For example, if you pass SAML token configuration name in the createCredential operation. Solution: Change the plug-in code appropriately. |
|||
1050
|
2063 |
Password is invalid. |
Possible Cause: The PKCS#12 files are uploaded with a wrong password. Solution: Ensure that you use the correct password for the PKCS#12 files. |
||
2064 |
Update operation is not supported for the parameter. |
Possible Cause: You are trying to update a read-only parameter. Solution: None. |
|||
2065 |
Parameter does not match. |
Possible Cause: The organization name specified in the XML file to upload the OATH tokens does not match with organization name specified in the operation. Solution: Provide the correct organization name. |
|||
6000 |
Duplicate questions are not supported. |
Possible Cause: Solution: |
|||
6001 |
Duplicate answers are not supported. |
Possible Cause: Solution: |
|||
6002 |
The question cannot be same as any of the answers. |
Possible Cause: Solution: |
|||
1050
|
6007 |
Credential history check failed. |
Possible Cause: The credential that you are trying to update failed the password history Solution: Ensure that the password that you have specified meets the history check criterion. |
||
6010 |
Question not found. |
Possible Cause: Question that you are trying to update, delete, and for which you want to update answer does not exist. Solution: Ensure that you use the correct question. |
|||
6105 |
Duplicate elements found. |
Possible Cause: The PKCS12 file being uploaded in to the ArcotID PKI contains duplicate elements. Solution: Upload a PKCS#12 file that does not contain duplicate entries. |
|||
6106 |
Invalid element reference. |
Possible Cause: The element that you are trying to delete does not exist in the ArcotID PKI. Solution: Ensure that you use the correct element identifier. |
|||
6200 |
Event is already assigned. |
Possible Cause: The event is already associated with an organization. Solution: Choose a different event to assign. |
|||
6201 |
Duplicate events are not supported. |
Possible Cause: The event list passed contains duplicate entries. Solution: Do not assign duplicate events. |
|||
1051 |
0 |
Invalid request. |
Possible Cause: Solution: 1. Ensure correct SDK is pointing to the server. 2.Ensure the port cconfigured on the client-side refers to the appropriate server protocol. |
||
|
|||||
|
|||||
|
|||||
|
|||||
|
|||||
|
|||||
|
|||||
1060 |
0 |
The request is noted. |
Possible Cause: Caller verification of the QnA credential is successful. In this case server does not apply the authentication policy. Solution: NA |
||
1100 |
0 |
Organization is not found. |
Possible Cause: Solution: 1. Check if the organization with the given name is created. 2. After creating the organization, the server might need cache refresh. Refresh the server cache. 3. Check if the name of the organization passed is correct. |
||
|
|||||
1101 |
0 |
Credential configuration not found for the organization. |
Possible Cause: Solution: 1. Check if the configuration is created for this organization. 2. Check if the configuration is assigned to this organization. 3. Creating and assigning configuration might need cache refresh. Refresh the server cache. |
||
|
|||||
1102 |
0 |
User not found. |
Possible Cause: Solution: |
||
|
|||||
1103 |
0 |
Organization is not active. |
Possible Cause: Solution: |
||
1104 |
0 |
Configuration already exists. |
Possible Cause: The configuration that you are trying to create already exists. Solution: If you want to create a configuration, the use a different configuration name. If you want to update an existing configuration, then use the correct operation. |
||
1150 |
0 |
User status is not active. |
Possible Cause: Solution: |
||
|
|||||
1151 |
0 |
User already exists. |
Possible Cause: Solution: |
||
|
|||||
1152 |
0 |
Credential is invalid. |
Possible Cause: Solution: |
||
|
|||||
5500 |
0 |
Processor is invalid. Note that processor refers to authentication mechanism. |
Possible Cause: Solution: |
||
|
|||||
5501 |
0 |
Data not found. |
Possible Cause: There was no data found for the Solution: Use a different search criteria. |
||
5600 |
0 |
The RADIUS client IP is not valid. |
Possible Cause: Client IP used in the RADIUS configuration is not valid. Solution: Ensure that you use an appropriate octet IP format. |
||
5601
|
0 |
The credential configuration is not valid. |
Possible Cause: The configuration passed in the input is not valid. Solution: Based on the operation being performed there could be multiple reasons for this error. Check the parameter details in the response or check the server logs for further details. |
||
2003 |
Configuration organization does not match with the request organization. |
Possible Cause: The organization name specified in the OATH token does not match with the organization name that you have specified in the operation. Solution: Ensure that you provide the correct organization name. |
|||
5601
|
6005 |
OATH token not found. |
Possible Cause: OATH token being assigned is not uploaded to the organization or it might not be uploaded for the organization the current user belongs to. Solution: Check the token identifier and ensure that you upload the OATH token at the global level or for the current organization. |
||
6006 |
OATH token is already assigned to a user. |
Possible Cause: The OATH token has already been assigned. Solution: Assign a different OATH token for the user. |
|||
6009 |
OATH token is abandoned. |
Possible Cause: The OATH token has been used and abandoned. Solution: Assign a different OATH token for the user or reuse the same token by force- assigning the token. |
|||
6104 |
Credential key is not active. |
Possible Cause: The key with which the credential is protected is no longer ACTIVE. Solution: Reissue and use the new credential. |
|||
5602 |
0 |
The protocol is not valid. |
Possible Cause: The protocol that you are trying to update or fetch is not valid. Solution: Use a valid protocol identifier. |
||
5603 |
0 |
The credential configuration for the organization is not valid. |
Possible Cause: The credential configuration name is not valid. Solution: You must provide a valid configuration name. |
||
5605 |
0 |
SSL trust store group name is invalid. |
Possible Cause: Solution: |
||
5606 |
0 |
SSL trust store group is invalid. |
Possible Cause: SSL trust store with this name already exists. Solution: Create a trust store with a different name. |
||
5607 |
0 |
Invalid WebFort Server instance name. |
Possible Cause: Server instance name being set is not valid. Solution: Provide a valid instance name. |
||
5608 |
0 |
A RADIUS client with the specified IP address is already configured. |
Possible Cause: The IP address specified in the operation has already been configured. Solution: If the existing configuration is not correct, then delete that configuration and create a new configuration. |
||
5700 |
0 |
Number of authentication attempts exceeded. |
Possible Cause: Solution: |
||
|
|||||
5701 |
0 |
Authentication token has expired. |
Possible Cause: Solution: |
||
|
|||||
5702 |
0 |
Challenge has expired. |
Possible Cause: Solution: |
||
|
|||||
5704
|
0 |
Credential has expired. |
Possible Cause: Solution: |
||
0 |
The credential configured for ASSP has expired. |
Possible Cause: The credential, which is provided by the user is expired. Solution: |
|||
6102 |
The credential validity period has not yet started. |
Possible Cause: The credential has been created for future use. Solution: Use the credential that is within the validity period. |
|||
5705
|
0 |
Credential is not active. |
Possible Cause: Solution: |
||
0 |
Credential is not active" "ASSP" "The user ( $$(USER)$$ ) account is inactive." |
Possible Cause: Solution: |
|||
5706 |
0 |
Credential is reissued. |
Possible Cause: |
||
5707
|
0 |
The authentication credentials provided are incorrect. |
Possible Cause: Solution: |
||
0 |
The ASSP authentication credentials provided are incorrect. |
Possible Cause: Solution: |
|||
6103 |
The authentication credentials provided are incorrect. Re-synchronize the credential. |
Possible Cause: The OTP that is provided is not in the configured authentication window, but can be synchronized. Solution: Synchronize the OTP credential. |
|||
5800
|
0 |
Credential not found for the user. |
Possible Cause: Solution: Possible Cause: Solution: |
||
0 |
ASSP credential not found for the user. |
Possible Cause: Solution: Possible Cause: Solution: |
|||
6004 |
The credential not found for the user. It is already been deleted. |
Possible Cause: The credential has already deleted. Solution: You can perform a fetch operation on the credential to understand the credential state. Reissue the credential, if required. |
|||
5801
|
0 |
Credential already present for the user. |
Possible Cause: |
||
6008 |
Credential already present for the PAN. |
Possible Cause: |
|||
6500 |
0 |
The event is not supported. |
Possible Cause: The event that being assigned to the plug-in is not supported by AuthMinder. Solution: Ensure that you use the supported events. |
||
6501 |
0 |
The operation is not supported. |
Possible Cause: The credential input provided is not valid. For example, you might have provided QnA input for the downloadCredential operation. Solution: Ensure that the input data that you provide is correct. |
Copyright © 2013 CA.
All rights reserved.
|
|