RETURN CODE

DESCRIPTION

100 A success return code to indicate a process is success however it is put on a queue or batch processing.
1 A return code to represent the boolean true value.
0 A return code to represent the boolean false value.
0 A success return code.
-1 A system error had occurred.
-2 A bad parameter error had occurred. Generally this would be due to an invalid API parameter/argument supplied.
-3 An invalid user had been identified. Depending on the API call, it generally either means the user had not been assigned a 2FA token, user is not found in external user store etc. Check the server error logs for details.
-4 An invalid serial no. had been identified. Depending on the API call, it generally represents an invalid token serial no. had been provided as in the token serial no. algorithm check failed in formatting etc. or the serial no. is not found in the database records (particularly for Hardware Token flow for instance). Check the server error logs for details.
-5 An invalid state had been detected. Depending on the API call, it can represent some configuration issue, user token state is invalid etc. Check the server error logs for details.
-6 An invalid certificate state had been detected. This generally returns by API that deals with certificate issuance and states. For example if the certificate is expired/not yet valid or if the certificate is not found in database. Check the server error logs for details.
-7 An invalid One-Time Password had been detected. Depending on the API call, it can represent either an invalid One-Time Password OR an invalid Registration Code had been provided. Check the server error logs for details.
-8 An invalid signature data had been detected. Check the server error logs for details.
-9 An error had been encountered with the Certificate Authority Gateway server. Check the server error logs for details.
-10 An error had been encountered with the Short-Messaging-System Gateway server. Check the server error logs for details.
-11 An error had been encountered with the E-Mail Gateway server. Check the server error logs for details.
-12 The mobile no. is currently in used. Check the server error logs for details.
-13 There are no more license available. Contact EZMCOM Inc. for licensing information.
-14 There is duplicated serial no. in the Ezidentity system. Contact EZMCOM support for details.
-15 A slightly more detailed error compared to bad parameter -2 indicating that a mobile no. is mandatory and required.
-16 A slightly more detailed error compared to bad parameter -2 indicating that an e-mail address is mandatory and required.
-17 The API currently does not support a particular business logic. Contact EZMCOM support for details.
-18 The 2FA token is currently locked. Contact EZMCOM support for details.
-19 The 2FA token is not active.
-20 The group/domain/organization is either an invalid identifier (don't exist in the system) or the group had been disabled/marked as soft deleted. Contact EZMCOM support for details.
-21 A generic error code to indicate an external server communication failure. Contact EZMCOM support for details.
-22 Unable to perform authorization. Check on the external server, the username/userid is record could not be found on the external server.
-23 An existing group name had been found. A unique group name is required.
-24 An error in the certificate attribute on the external server. The attribute or the certificate is either not found.
-25 A generic error return code to represent a particular object is not found. Check the server error logs for details.
-26 A duplicate in username had been identified. A unique username is expected.
-27 The Token Activation Code had expired.
-28 The user token quota had reached its maximum. Contact EZMCOM support for details.
-29 The serial no. is already assigned and in use for a particular user.
-30 The Out-Of-Band Gateway had encountered an error. Check the server error logs for details.
-31 A generic error to indicate a failure to modify the user password. Check the server error logs for details.
-32 An authentication had failed. For example an external server authentication. Check the server error logs for details.
-33 The external server host is not available. Check the server error logs for details.
-34 A generic invalid credentials had been supplied. Check the server error logs for details.
-35 A generic bad attribute had encountered. This usually deals with LDAP server. Check the server error logs for details.
-36 The external user store group configuration had encountered a failure. Check the server error logs for details.
-37 User already binded with 2FA token. Check the server error logs for details.
-38 An XML parsing had failed using XStream. Check the server error logs for details.
-39 An error had occurred while creating Directory Server group. Check the server error logs for details.
-40 The group does not belong to a master group (indicating it is a master group itself) - a customer group is expected. Check the server error logs for details.
-41 The master group is not SAAS (Software As A Service) enabled. This is typically for MSIGN.
-42 The customer group is not SAAS (Software As A Service) enabled. This is typically for MSIGN.
-43 No configuration for group base DN. Typical return code for group marked as SAAS but the master group did not configure the group base DN group configuration. This is typically for MSIGN.
-44 No configuration for user base DN. Typical return code for group marked as SAAS but the master group did not configure the user base DN group configuration. This is typically for MSIGN.
-45 The user is already enrolled. This is typically for MSIGN.
-46 Invalid SAAS (Software As A Service) service identifier. This is typically for MSIGN.
-47 Invalid group state. The group is either soft-deleted or disabled.
-48 Invalid service state. The service is either soft-deleted or disabled. This is typically for MSIGN.
-49 The user enrollment state is invalid. This is typically for MSIGN.
-50 The external credential password had expired. This normally deals with Directory Server settings where the user password credential is expired.
-51 The directory server user creation was unsuccessful. Check the server error logs for details.
-52 Generic incomplete process status. Useful to indicate a particular bulk process (loop process) is not successfully completed.
-53 Insufficient license. Contact EZMCOM support for details.
-54 Unsupported SAAS client action request identifier. This is typically for MSIGN.
-55 Common invalid adapter state. Can be used to identify a missing adapter, missing adapter configuration etc. anything related to an adapter. Check the server error logs for details.
-56 Common invalid adapter callback. Also to represent a common adapter call failure had occurred. Check the server error logs for details.
-57 Common code to indicate the adapter does not support test.
-58 Common code to indicate the adapter test had thrown unhandled exception.
-59 Enrollment (for SAAS) which includes sending the service activation code successful but failed at notifying the user via Out-of-Band protocols. This is typically for MSIGN.
-60 SAAS activation notification failure. This is typically for MSIGN.
-61 Invalid service activation code. This is typically for MSIGN.
-62 The SAAS service is already activated for this user. This is typically for MSIGN.
-63 The service activation code had expired. This is typically for MSIGN.
-64 The user status is invalid. User could be disabled/soft-deleted etc. Check the server error logs for details.
-65 No bound (associated) token found for the user. Most likely have not activated SAAS for the first time. This is typically for MSIGN.
-66 The transaction already exists and is in pending state. This is typically for MSIGN.
-67 The transaction already exists and is in pending state. This is typically for MSIGN.
-68 The certificate is not found in the database. This is typically for MSIGN.
-69 The certificate had expired. This is typically for MSIGN.
-70 The certificate is not valid yet. This is typically for MSIGN.
-71 The certificate had been revoked. This is typically for MSIGN.
-72 The mobile device UID is already in used. This is typically for MSIGN.
-73 The SAAS activation callback adapter is not bound. This is typically for MSIGN.
-74 The SAAS transaction callback adapter is not bound. This is typically for MSIGN.
-75 The transaction had expired. This is typically for MSIGN.
-76 The transaction is invalid. This is typically for MSIGN.
-77 The SAAS transaction push notification failed. This is typically for MSIGN.
-78 There is an invalid gateway URL configured. This is typically for MSIGN.
-79 The SAAS connector had timed out. This is typically for MSIGN.
-80 Invalid registration code. Check the server error logs for details.
-81 Document signing had failed. This is typically for MSIGN.
-82 Unknown status created for polling type of return code where there is no result (yet). This is typically for MSIGN.
-83 Returned when an attempt is being made to register a duplicate 'maker action' entry. This is typically for MSIGN.
-84 The expected formatted message for push transaction cannot be parsed without error, e.g. missing tag, closing bracket, etc. Also if it is not HTML. This is typically for MSIGN.
-85 Failure to pull transactions from service provider's end. This is typically for MSIGN.
-86 Invalid configuration - used as a generic return code to identify some invalid configuration had occurred.
-87 Special return code for time based token signature otp, used as a 'claim code'.
-88 Invalid external server configuration - used as a specific return code to indicate some invalid configuration in the external server settings.
-89 Invalid XML Digital Signature XADES. Check the server error logs for details.
-90 An object already exists. Check the server error logs for details.
-91 A failure to decrypt. Check the server error logs for details.
-92 A failure to encrypt. Check the server error logs for details.
-93 Unable to pre-activate (for Online Token Activation - OTA) due to the serial number supplied is already binded. Check the server error logs for details.
-180 On the next failure attempt, the token will be locked. NOTE: If the user gets a valid attempt on the last try, the failure attempt will be reset.

Last generated: 11 February 2014 @ 07:42:12 PM