Review the following list of general troubleshooting steps prior to contacting Digipass S3 support:
Review the Server and API Server logs and look for exceptions, errors, and failures.
Check that the correct metadata for your ASM is present on the Server.
Check that the AAID for your ASM is present in the Server policy.
Check that you have connectivity to your Server and are able to browse to the facets.uaf file from your web browser.
Clear any data that is cached by your app and any UAF client.
Ensure that the session is communicating using HTTPS. The UAF protocol mandates TLS protected communication.
Verify that your Server has a valid certificate and that your device trusts the Server certificate.
Verify that your app is correctly installed and opens successfully.
Verify your network connectivity.
Verify that the Server FIDO policy accepts the authentication methods installed on the device.
If there are issues with user authentication, check the Authentication Server's diagnostic logs in <TOMCAT_HOME>/logs/nnl.log.
When testing using Tutorial App, verify that the server URL is configured correctly. Follow the instructions to configure the Tutorial App for Android or iOS or Web.
Tutorial App Does Not Work, User is Unable to Login
Problem | Tutorial App does not work; the user is unable to login. |
|---|---|
Description | To use Tutorial App, Tutorial Web App should be deployed. Tutorial Web App is the login servlet, so make sure that it is deployed without any errors. On the mobile devices, Tutorial App may display the error message: Login Failed |
Steps | Verify that you are using "noknok" as the password for the Tutorial App. Check the following:
|
Client Error: NO_MATCH
Problem | Your client app displays the following error message from the Authentication Server: Client Error: NO_MATCH |
|---|---|
Description | This error is the result of an unsuccessful registration or authentication attempt. The NO_MATCH response indicates one of:
|
Steps | To avoid displaying this message to the user, your code should perform a check FIDO policy operation prior to performing a FIDO operation. Use the checkRegPossible(), checkAuthPossible(), and checkTransPossible() methods to perform a check policy for registration, authentication, and transaction confirmation, respectively. If check policy fails, it indicates that subsequent FIDO operations will also fail. Your code can modify the UI to prevent the user from triggering the NO_MATCH message. See Registering and Sign-in sections in the Developer Guide for iOS, Android, and Web. Also see the source code for the Tutorial App for examples of how to use the checkRegPossible(), checkAuthPossible(), and checkTransPossible() methods. |