The following error codes are returned by Native UX Adapter Node SDK.
These lists are subject to change.
Error Code |
Message Thrown |
Scenarios |
Recommended Action |
LP-REG-1000 |
Invalid registration request |
Passed the wrong registration uuid while registering a user or a device. |
Pass the correct registration uuid from the previous step. |
LP-REQ-1050 |
Invalid Registration Session format |
Passed the wrong registration session while registering a user or a device. |
Pass the correct registration session from the previous step. |
LP-USR-1029 |
Invalid OTP value format |
Passed wrong or null otp while registering a user or a device. |
Pass the valid OTP received either in your mobile or email. |
LP-REQ-1010 |
Invalid mobile number format |
Passed wrong mobile number format while registering a user or a device. |
Pass a valid mobile number with a valid international code. |
LP-EMAIL-1002 |
Email is not valid |
Passed wrong or valid email while registering a user. |
Pass a valid email id. |
LP-REG-1000 |
Invalid registration request |
If validateChallenge() SDK method is called after successful activation of the user or the device. |
Please check the flow of the registration process validateChallenge() SDK method should be called while registering mobile or email not after activating the user or the device. |
LP-REQ-1051 |
Invalid Username format. The Username should be a valid email or mobile number |
Log in with the wrong username after activation of the user or the device. |
Pass a valid email or mobile number with which the user or the device was registered. |
LP-REQ-1020 |
Invalid Hashed Pin format |
Log in with an invalid hashpin after activation of the user or the device. |
Pass a valid hashed pin with which the user or the device was registered. |
LP-REQ-1021 |
Invalid Device UUID format |
Log in with an invalid device uuid after activation of the user or the device.
|
Pass the valid device uuid which was received as a part of the response after the user or the device was registered. |
LP-REQ-1022 |
Invalid AuthKey format |
Log in with an invalid authKey uuid after activation of the user or the device. |
Pass the valid authKey which was received as a part of the response after the user or the device was registered. |
LP-LOGN-0002 |
Invalid login credentials |
Log in with an expired authKey uuid after activation of the user or the device. |
Pass the valid and latest authKey, as authKey changes every time a login or reset pin step occurs. |
LP-REQ-1010 |
Invalid mobile number format |
Passed wrong mobile number while requesting for forgot pin. |
Pass a valid mobile number with a valid international code of the activated device. |
AN-GOTP-1004 |
Incorrect OTP |
Passed the wrong OTP while requesting forgot pin Validate Challenge. |
Pass the valid OTP received either in your mobile or email. |
LP-REQ-1052 |
Invalid Request UUID format |
Passed the wrong request uuid while requesting forgot pin Validate Challenge. |
Pass the correct request uuid from the previous step. |
LP-REQ-1053 |
Invalid Request Session format |
Passed the wrong request session while requesting forgot pin Validate Challenge. |
Pass the correct request session from the previous step. |
LP-USR-1022 |
Invalid forgot PIN request |
Passed the non-registered mobile number session while requesting forgot pin. |
Pass the registered mobile number with a valid international code. |
LP-REQ-1021 |
Invalid Device UUID format |
Passed wrong device uuid after multistep verification while requesting forgot pin. |
Pass the valid device uuid which was received as a part of the response after the user or the device was registered. |
LP-REQ-1052 |
Invalid Request UUID format |
Passed wrong request uuid after multistep verification while requesting forgot pin. |
Pass the valid request uuid which was received as a part of the response in the previous multistep verification step. |
LP-REQ-1052 |
Invalid Request Session format |
Passed wrong request session after multistep verification while requesting forgot pin. |
Pass the valid request session which was received as a part of the response in the previous multistep verification step. |
LP-REQ-1052 |
Invalid Hashed Pin format |
Passed wrong hashed pin after multistep verification while requesting forgot pin. |
Pass a valid hashed pin. |
LP-LOGN-0002 |
Invalid login credentials |
Passed an unregistered email id while login in. |
Pass a valid and registered email id. |
LP-REQS-1004 |
Incorrect request UUID or missing verification steps |
If resetPin() SDK method is called before doing multistep verification in the forgot pin process. |
Please check the flow of the forgot pin process resetPin() SDK method should be called after multistep verification of mobile and email. |
AN-UOTP-1003 |
The OTP is expired. Please request a new one |
If OTP passed in any step is expired. |
Please request a new OTP. |
SDK-OIDC-1115
|
Invalid realm |
If the value against iam.realm in SDK configuration file 'config.properties' is empty or does not exist |
Please check if the value against iam.realm in SDK configuration file 'config.properties' is valid as per your Haventec IAM realm. |
SDK-OIDC-1116 |
redirectUri :http://xyz/ is not reachable |
If the value against redirect.url in SDK configuration file 'config.properties' is not reachable |
Please check if the value against redirect.url in SDK configuration file 'config.properties' is reachable. |
SDK-OIDC-1001 |
Invalid format at the parameter IAM client. |
If the value against iam.client in SDK configuration file 'config.properties' is either null or empty or does not exist |
Please check if the value against iam.client in SDK configuration file 'config.properties' is valid as per your Haventec IAM realm. |
SDK-OIDC-1003 |
Invalid format at the parameter IAM base url. |
If the value against iam.base.url in SDK configuration file 'config.properties' is either null or empty or does not exist |
Please check if the value against iam.base.url in SDK configuration file 'config.properties' is a valid Haventec IAM URL. |
SDK-OIDC-1102 |
Invalid redirectUri |
If the value against redirect.url in SDK configuration file 'config.properties' is either null or empty or does not exist |
Please check if the value against redirect.url in SDK configuration file 'config.properties' is valid. |
LP-REQ-1005 |
Invalid Client ID format |
If the value against haventec.app.client.id in SDK configuration file 'config.properties' is either null or empty or does not exist |
Please check if the value against haventec.app.client.id in SDK configuration file 'config.properties' is valid as per your Haventec IAM realm. |
LP-APP-1002
|
This feature is not enabled for this application yet. Please contact administrators for more information |
If the value against haventec.app.client.id in SDK configuration file 'config.properties' is wrong or invalid |
Please check if the value against haventec.app.client.id in SDK configuration file 'config.properties' is valid as per your Haventec IAM realm. |
SDK-OIDC-1117 |
Haventec IAM : https://xyz:8180/auth is not reachable |
If the value against iam.base.url in SDK configuration file 'config.properties' is not valid or wrong |
Please check if the value against iam.base.url in SDK configuration file 'config.properties' is a valid Haventec IAM URL. You can also refer to the Usage section in the SDK README page to get the actual value for iam.base.url for demo or production. |
SDK-OIDC-1118
|
Haventec Connect is not reachable |
If the Haventec Connect link is down |
Please check with Haventec Team regarding the status of the Haventec Connect link |
SDK-OIDC-1119 |
Haventec Authenticate is not reachable |
If the Haventec Authenticate link is down |
Please check with Haventec Team regarding the status of the Haventec Authenticate link |
SDK-OIDC-1107
|
Iam Access Token is null |
Did not pass any value against IAM access token while calling logout() method of SDK |
Please pass the valid iamIdToken received while calling loginPinDevice() method of SDK |
LP-USR-1015
|
Invalid reset request |
Did not pass a valid device UUID while resetting the pin after multistep verification. |
Please pass a valid Device UUID, which is already registered. |
Haventec IAM Error Codes
Error Code |
Message Thrown |
Recommended Action |
SDK-OIDC-1113
|
An error occurred while communicating with the IAM, please check IAM logs or contact administrator, more information : [Client not found.] |
Please check if the value against iam.client in SDK configuration file 'config.properties' is valid in your Haventec IAM realm. |
An error occurred while communicating with the IAM, please check IAM logs or contact the administrator, more information : [Realm does not exist] |
Please check if the value against iam.realm in SDK configuration file 'config.properties' is valid in your Haventec IAM realm. |
|
An error occurred while communicating with the IAM, please check IAM logs or contact the administrator, more information : [Not Found] |
Please check if the value against iam.base.url in SDK configuration file 'config.properties' is a valid Haventec IAM url. |
|
|
An error occurred while communicating with the IAM, please check IAM logs or contact the administrator, more information : [Bad Gateway] |
Please check if the Identity Provider has the correct Authorization URL and Token URL in your Haventec IAM realm. You can also refer to Haventec IAM documentation to understand how to configure the Identity Provider. |
SDK-OIDC-1109
|
Service.getRequiredQuery [session_state] not found in : [] |
The user you are trying to register already exists in the Haventec IAM realm or there is a linkage issue between the user in Haventec IAM and Haventec Connect. Please delete the user from The Haventec IAM realm and in Haventec Console and try to register again. |
Service.getRequiredQuery [state] not found in : [client_id=baxe_client& redirect_uri=http%3A%2F%2Fmockbin.org%2Frequest& response_mode=fragment& response_type=code&scope=openid] |
To solve this please provide the default identity provider in the Haventec IAM realm. |
Comments
0 comments
Please sign in to leave a comment.