Authentication Error Codes
Here is a list of all authentication related error codes. These error codes are potentially visible to end-user. Error codes are not in any particular order.
Error code | Description | How to resolve |
|---|---|---|
TID-AEX-1000 | Black listed login target. Relates to distributed SSO. | Contact support |
TID-AEX-1001 | Multiple matching users. This is generally a non-issue as TrivoreID can provide dialog for user to select user to login as. | Handled automatically |
TID-AEX-1002 | Login rule failed. This happens when authenticating from external service and is dependent on related user directory configuration. | Contact support |
TID-AEX-1003 | Creating new user is not allowed. This happens when authenticating from external service and only existing users are allowed to login. | Contact support |
TID-AEX-1004 | Personal identity code conflict. This happens on strong identification when user is not allowed to change their personal identity code. | Always use same identity when performing strong identification. Contact support if your actual personal identity code has changed. |
TID-AEX-1005 | Invalid attribute mapping value from external service. This can happen when user directory configuration is invalid. | Contact support |
TID-AEX-1006 | User directory configuration is invalid, does not belong to any namespace. Corner case. | Contact support |
TID-AEX-1007 | Database access failure when updating user information. | Contact support |
TID-AEX-1008 | User tries to link their account or perform strong identification with external service that belongs to non-related namespace. Corner case. | Contact support |
TID-AEX-1009 | User tries to link their account with another account but current user is not available. Corner case. | Contact support |
TID-AEX-1010 | Unsupported SAML-based user directory type. Corner case. | Contact support |
TID-AEX-1011 | LDAP user directory not available when trying to perform authentication. Corner case. | Contact support |
TID-AEX-1012 | Invalid namespace username policy. Corner case. | Contact support |
TID-AEX-1013 | Failed to parse user validity attribute from LDAP. Probably caused by invalid attribute mapping. | Contact support |
TID-AEX-1014 | Conflicting user information. This usually happens when trying to create new user but it does not satisfy uniqueness requirements. For example, username must be unique within namespace. Other possible unique indexes may also prevent creating the user. | Contact support |
TID-AEX-1015 | Failed to generate unique username even with backup policy. Corner case. | Contact support |
TID-AEX-1016 | Authentication from external LDAP/ADDS server failed. | Check your username and password |
TID-AEX-1017 | Ambiguous LDAP/ADDS authentication results, multiple matching entries found. | Contact LDAP/ADDS server administrator. |
TID-AEX-1018 | Invalid LDAP/ADDS distinguished name. Unable to fetch user attributes. Corner case. | Contact support |
TID-AEX-1019 | Invalid LDAP/ADDS directory configuration. Check service credentials. | Contact support |
TID-AEX-1020 | LDAP/ADDS connection failure. | Contact support or LDAP/ADDS server administrator. |
TID-AEX-1021 | LDAP/ADDS search failure. | Contact support |
TID-AEX-1022 | Failed to parse userAccountControl attribute from ADDS. | Contact support |
TID-AEX-1023 | Invalid LDAP authentication token provided, internal error. Corner case. | Contact support |
TID-AEX-1024 | Unsupported LDAP-based user directory type. Corner case. | Contact support |
TID-AEX-1025 | User account has expired, validity time has been exceeded. | Contact support and request your account validity to be extended. |
TID-AEX-1026 | User account has been disabled. | Contact support and request your account to be re-enabled. |
TID-AEX-1027 | The user directory your account belongs to has been disabled. | Contact support |
TID-AEX-1028 | User account has been locked. This may happen when, for example, invalid credentials are entered too many times. Other possible causes exist. | Contact support and request your account to be unlocked. |
TID-AEX-1029 | Requested namespace not found. | Contact support |
TID-AEX-1030 | Invalid credentials entered. | Check your username and password. |
TID-AEX-1031 | Requested user information is not available. May happen after user is deleted. Corner case. | Contact support |
TID-AEX-1032 | Login with token failed. Token may be persistent login cookie, distributed SSO token or some other token mechanism. Actual cause varies, usually happens when token has expired or token authentication is not allowed. | Re-enter your credentials and login again. |
TID-AEX-1033 | Invalid API client credentials. | Check your credentials or access token validity. |
TID-AEX-1034 | Invalid credentials for external Simple REST API user directory. | Check your username and password. |
TID-AEX-1035 | Unexpected authentication failure. Actual cause varies but implies internal error. Corner case. | Contact support |
TID-AEX-1036 | Mandatory user directory attribute mapping not available. | Contact support |
TID-AEX-1037 | Strong identification service is not available for user trying to use it. | Contact support |
TID-AEX-1038 | SAML response validation failed or user cancelled SAML based authentication. | Contact support if this problem persists after you have correctly authenticated in external SAML based service. |
TID-AEX-1039 | External authentication ID not available. | Contact support |
TID-AEX-1040 | Directory ID not available. Internal error. | Contact support |
TID-AEX-1041 | Internal user ID not available. Corner case. | Contact support |
TID-AEX-1042 | Invalid user delete conflict policy. Corner case. | Contact support |
TID-AEX-1043 | Username not available. | Contact support |