DIGIPASS Authentication for Epic Hyperspace Administrator Guide
2.4.3
Standard Server Setup
DIGIPASS Authentication for Epic Hyperspace Overview
Figure 2: Standard Server Connection Configuration
This setup uses one main authentication server to handle requests from the DIGIPASS Authentication Module, with a backup authentication server for use when the main server is busy or unavailable.
15
DIGIPASS Authentication for Epic Hyperspace Administrator Guide DIGIPASS Authentication for Epic Hyperspace Overview
2.5
Tracing
The
DIGIPASS Authentication Module
allows use of a trace file to record module activity, e.g. for troubleshooting. This will include errors that have been encountered, warnings, and general information about performed authentication requests.
The level of tracing that the DIGIPASS Authentication Module employs depends on its configuration settings.
CAUTION
Enabling full tracing should only be done for troubleshooting purposes. There are no limits set on the size of the tracing file, so if the option is left on too long on a high-load system the file may dramatically slow down or crash Windows, due to excessive I/O or filling up the hard drive.
Because there are no size limitations set on the trace file, it is not recommended that you have tracing permanently enabled. If your system is set up with tracing always enabled, ensure that the file does not cause problems by deleting or archiving it whenever it gets too large.
Basic tracing includes:
•
Error messages
•
Warnings
•
High-level information from module activity
Full tracing includes:
•
Error messages
•
Warnings
•
High-level information from module activity
•
Detailed information from module activity
NOTE
The DIGIPASS Authentication Module will require permissions for the directory in which the tracing file is kept. For more information, see
6.1.2 Trace file location .
16
