| Hendelseslog melding | Framgangsmåte |
|---|
OTP verification failed. 2 attempts remainingOtp verification failed. 1 attempt remaining | Prøv å skrive inn engangskoden en gang til |
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 | Undersøk om brukeren har skrevet riktig brukernavn Undersøk om LDAP/HTTP inneholder riktig telefonnummer/appID i riktig attributt for brukeren Undersøk om oppslag gjøres i korrekt LDAP sti
|
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 | Undersøk om telefonnummeret og/eller appID i LDAP er riktig formatert (med landkode) samt om dette stemmer overens med brukerens app. Sjekk også om det er samme nummer som brukeren benytter i fbm aktivering av appen. |
Authentication failed. User found in HTTP http://youruserstore.com/lookup but appId was missing | Legg inn brukerens appID i HTTP katalogen |
Authentication failed. User found in HTTP http://youruserstore.com/lookup but phone number was missing | Legg inn brukerens telefonnummer i HTTP katalogen |
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. | Oppdatere LDAP konfigurasjonen med riktig brukernavn og passord |
Could not contact ldap://190.190.190.190 due to a communication/network problem.
Contact your network administrator for troubleshooting and assistance. | Undersøk om kommunikasjonen mellom Service Connector og LDAP katalogen er tillatt |
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 | Legg inn brukerens telefonnummer i LDAP katalogen |
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 | Legg inn brukerens appID i LDAP katalogen |
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) | Undersøk om brukeren forsøker å logge inn med offline engangskode (8 siffrer) og informer i så fall om att offline koder ikke er tillat |
Offline OTP was generated using wrong PIN. 2 attempt(s) remaining Offline OTP was generated using wrong PIN. 1 attempt(s) remaining | Generer ny engangskode og forsøk igjen |
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 | Be brukeren generere ny engangskode og forsøke logge inn igjen Be brukeren om, hvis mulig, aktivere datatrafikk og generere en online engangskode og logge på med den. Dette vil også synkronisere tidsforskjellen mellom mobiltelefonen og serveren samt medføre at offline genererte engangskoder vil fungere. Hjelpe brukeren med en
|
