Introduction
The following is a list of basic, initial troubleshooting actions to try when attempting to resolve issues encountered during Server installation or operation. Review these steps prior to contacting Digipass S3 support:
Troubleshooting Action | Notes |
|---|---|
Review Server logs | Server log location depends on Tomcat installation, e.g. <TOMCAT_HOME>/logs/nnl.log |
Review the Server's FIDO policies | |
Review the API Server FIDO policy configuration | Make sure that the correct policy name is configured in the API Server for registration and authentication. |
Ensure that the Server FIDO policy is configured with the correct AAIDs (UAF) or correct values for the FIDO2 authenticator attributes. | |
Review the Server properties configuration | The tenant-specific and system properties are in the DB. |
Review Tomcat logs | Example default location for Tomcat logs: <TOMCAT_HOME>/logs/catalina.out |
Review Tomcat services | Depends on your individual Tomcat installation |
Review database logs | Depends on your individual database installation; PostgreSQL and Oracle store logs using different methods. Refer to your DBMS provider’s user documentation. |
Review database services | Depends on your individual database installation. |
Check firewall configuration | Ensure that the firewall has the required open ports. This depends on your individual firewall installation, e.g. /etc/sysconfig/iptables |
Verify Server network routing | Depends on your individual deployment environment. Use nmap, netstat, wget, telnet or other tools to check for access |
Review services and logs for proxy server | Depends on your individual installation. Review the documentation for the proxy server software you are using. |
Review configuration and settings for proxy server | Depends on your individual installation. Review the documentation for the proxy server software you are using. |