| Event log messages | What to do |
|---|
OTP verification failed. 2 attempts remaining. Otp verification failed. 1 attempt remaining | Try entering the the One Time Code again |
Authentication failed. User not found in LDAP/HTTP. Tried ldap://192.168.171.160 with path
basedn[ou=user,dc=test,dc=local(*)],filter[samAccountName=user].
Please ensure that the user has entered the username correctly and that the mobile number
and/or appID for the user is declared in the correct LDAP/HTTP-attribute | Verify that the user has supplied the correct username Verfify that LDAP/HTTP contains the correct username/appID in the correct attribute for the user Verify that the query is performed in the correct LDAP path
|
The phone number +4711111111 in your LDAP does not match the handset that has generated the OTP. Check that the phone number and/or appID is correct and that the phone number is formatted correctly (with country code). Also, check that the user has activated the application using the correct phone number | Verify that the telephone number and/or appID in LDAP has the correct format (including county code) and that this correlates with the users app. Also verify that it is the same number the user is using when activating the app. |
Authentication failed. User found in HTTP http://youruserstore.com/lookup but appId was missing | Enter Supply the users appID in the HTTP catalog. |
Authentication failed. User found in HTTP http://youruserstore.com/lookup but phone number was missing | Enter Supply the users telephone number in the HTTP catalog. |
Could not authenticate to ldap://192.168.171.160 due to an authentication problem,
please verify that service username and password is correct.
Contact your network administrator for troubleshooting and assistance. | Update the LDAP configuration with the correct username and password. |
Could not contact ldap://190.190.190.190 due to a communication/network problem.
Contact your network administrator for troubleshooting and assistance. | Verify that the communication between the Service Connector and the LDAP catalog is allowed. |
Authentication failed. User found in LDAP ldap://192.168.171.160 using path
basedn[ou=test,dc=bpcode01,dc=local(*)],filter[samAccountName=user] but phone number was missing | Enter Supply the users telephone number in the LDAP catalog. |
Authentication failed. User found in LDAP ldap://192.168.171.160 using path
basedn[ou=test,dc=bpcode01,,dc=local(*)],filter[samAccountName=user] but appId was missing | Enter Supply the users appID in the LDAP catalog. |
OTP is no longer valid. Date/time created: Fri Nov 07 05:06:40 CET 2014.
Looks like the user tried to use an offline OTP. Offline generated OTPs are not allowed for NAS ADFS Proxy (10.11.1.82) | Verify that the user is trying to log on with an offline One Time Password (8 numbers) and if this is the case inform that offline codes are not permitted. |
Offline OTP was generated using wrong PIN. 2 attempt(s) remaining Offline OTP was generated using wrong PIN. 1 attempt(s) remaining | Generate a new One Time Code and try again. |
Offline OTP validation failed. Typical reasons are that the phone is out of sync,
the user took too long to enter the OTP or wrong phone was used | Ask the user to generate a new One Time Code and try to log in again. Ask the user, if possible, to activate data traffic, and generate an One Time Code and logging on with it. This will also synchronize the time difference between the mobile phone and the server and thus enabling offline codes. Help the user with a manual synchronization of the time difference.
|
Offline OTP has already been used | Ask the user to generate a new One Time Code and then logging in again. |
User is not active | The user has been deaktivated in Buypass Code Manager. Look up the user account and activate it if access is to be granted again. |
OTP app is not the right type. AppType is 120001 and accepted appTypes are [120002,120003] | The user tries to use an app from another partner than what is to be used, Ask the user to uninstall the app and install the app from the correct partner. |
OTP AppType not valid for this operation, appType = 120001 not accepted by merchant. Accepted appTypes is (120002,120003) | The user tries to use an app from another partner than what is to be used, Ask the user to uninstall the app and install the app from the correct partner. |
The app that was used to generate the OTP is not the most recently activated.
Check that the user is using the most recently activated app. | The user is using an app that is not the last activated one for the corresponding telephone number. Ask the user to use the correct telephone/app Ask the user to uninstall, install, and then activate the app again
|
The app that was used to generate the OTP is not the most recently activated.
Check that the phone number and/or appID in LDAP is correct and that the user is using the most recently activated app. | AppID in LDAP/HTTP does not correspond to the appID that generated the One Time Code. Update the LDAP/HTTP catalog with a new appID from the users app. |
The user has input incorrect values. Last OTP was generated: .*
Please ask the user to generate a new code and try authenticating again | Ask the user to generate a new One Time Code and to log in again. |
OTP tried too many times: 3 | Ask the user to generate a new One Time Code and to log in again. |
OTP is no longer valid. Date/time created: Fri Nov 07 06:09:26 CET 2014 | Ask the user to generate a new One Time Code and to log in again. |
OTP is blocked for merchant 44445556, status = 20 | The user has entered the wrong pin 3 times in a row and will need an unblock code the unblock the app. |