Log Settings
Since DAF can be a little tricky to configure, DAF offers powerful log features which should be helpful to solve potential problems. Logs can be viewed in real-time with the DAF Configuration Tool (button [Live Log]) or saved in text log files. With live and file mode, logs can be reported in a unique main log, or in separate logs (one per database).
Live log is always active. If needed, it can be deactivated by a registry setting.
Log Settings are available in the DAF Configuration Tool with button [Main Log file] for the main log, and under tab "Logs" for DAF User Database log settings.
Main Log file:
This setting should be used to enable the use of a main log file.
Write in main log file/Write in private log file:
If Write in main log file is checked all logs are reported in the same live log
window and in the same text file.
If Write in private log file is checked logs are reported in a separate log window
(and separate text file) for each database, plus one as the main log.
File names specified here will be extended with "MMDD.LOG" (MM=month, DD=day) and a new file will be created each day.
Log to log file:
Log written to a test file log is active only if Log to log file is checked.
Log on DAF user logged (login only):
If checked, DAF will report a message each time a user has been found in a DAF database,
and will specify what NT user has been mapped.
Important Note:
This option reports a message when a WEB user was found in a DAF database. This is true
regardless of the mapped NT user. In other words, if the mapped NT user has an invalid NT
account (or does not have the read NT permission for the requested file or directory) this
message will not show it and the WEB user will receive an "Access Denied"
result. Information on the NT user is reported when the log option Log on "Access
Denied" is checked.
Log on DAF user logged (login & password):
Same as the previous option, except that the password will also be logged.
Log on DAF user NOT logged (login only):
If checked, DAF will report a message each time a user is not found in a DAF database.
Important Note: However, if this user is a valid NT user, and if the option "Forward
unfound DAF user to NT" is activated, the WEB user will access the requested file or
directory.
Log on DAF user NOT logged (login & password):
Same as the previous option, except that the password will also be logged.
Log on IIS "Access Denied":
If checked, DAF will report information for each "Access Denied" result
generated by an invalid NT user, or a valid NT user with too limited NT permissions.
Log ODBC/SQL Requests:
Applicable only for an ODBC User Database. When enabled, all SQL
requests sent to the database system will be logged. This option can be very useful to
solve problems related to the used ODBC source.
Log all received HTTP requests:
When this option is enabled, all received HTTP requests will be
logged in the main log. This option can be very useful to find which database is is used
to process authentication for a specific HTTP request.
Tips
Troubleshooting Logs settings
To setup and test a new DAF User Database configuration, it is recommended you use the following settings:
and use the Live log to search potential error messages.
Live Log
When the live log window is open, all log messages will be reported in real-time.
Sample live Log window
Finding which DAF User Database is used
With several DAF User Databases installed an easy way to find which DAF User Database is used for a specific request is to enable the DAF configuration option "Log all received HTTP requests" and open the "Live Log" window with the "Main Log" selected. At this point all received HTTP requests will generate a line in the Live Log such as:
HTTP Request for <www.dafweb.com>,<80>,<192.168.1.50> from <192.168.1.150>, <Mozilla/4.0 (compatible; MSIE 4.01; Windows NT)> - Attached to <AccessDB>
showing in particular which DAF User Database is used (here: "AccessDB").
Last update: Friday, April 02, 1999 07:58