DAF 4.X Home Page

DAF Documentation Home

Quick Start (First Installation for New User)

1. Download and Unzip the latest DAF Package
2. Run SETUP.EXE. Follow instructions and accept default settings. If the setup program did not report any errors, all DAF components should now be installed and running.
3. Prepare a User Database
4. Create a System DSN ODBC Source (ODBC User Database only)
5. Configure DAF to use your DAF User Database
6. Start the DAF User Database
7. Test your DAF Configuration
8. Setup the Web User Manager
9. How to use Logs options


3. Prepare a User Database

DAF can handle TEXT file or ODBC source as a User Database. For a Quick Start two sample User Databases are available in directory "<DAF directory>\quickstart\userdb":

Both files contain the same four users: 

Login Password DAF Groups
John left grp1;grp2;grp3
Jack blue grp1
Joe square grp2;grp3
Jerry fries  

 File USERDB.TXT:

8242 bytes

File USERDB.MDB (MS Access 97):

Data in table UserDB:

13777 bytes

Structure of Table UserDB:

15885 bytes

If you would rather create your own DAF User Database, please refer to Creating a User Database with an ODBC Source or Text file


4. Create a System DSN ODBC Source (ODBC User Database only)

To use the sample MS Access User Database it is necessary to create a new ODBC data source name attached to the sample MS Access File.

ODBC setup dialog box with an MS Access file:

ODBC MS Access Setup


5. Configure DAF to use your DAF User Database

Launch the DAF Configuration Tool:

DAF Configuration Tool
 

The next step consists of creating a DAF User Database which is an internal object built around the "real" User Database:

57124 bytes

Attach the DAF User Database to an IP address

It is now necessary to specify for which Web Host the DAF User Database should handle authentication. In other words, for which incoming HTTP requests DAF should handle authentication. This specification is done by attaching a combination of an IP address a Port  Number and Host Header Name to a DAF User Database. For this sample the DAF User Database will be attached to an IP address.

In the screen example, IP address 192.168.1.100 has been attached to DAF User Database "userdb1." This means that DAF will handle authentication for all incoming HTTP requests starting with 'http://192.168.1.100/..." (or corresponding web domain name.)

A DAF User Database can also be attached to any combination of a IP address, a Port  number, and Host Header Name. For more information refer to section Web Hosts Configuration

--------- important.GIF (334 bytes) Important! ------------------------------------

IIS Authentication Scheme Configuration requirement

DAF does not support "Windows NT Challenge/Response" Authentication scheme. A Web Site attached to a DAF User Database MUST have the following IIS authentication settings. If this is not the case DAF will not handle web authentication correctly:

For instructions, refer to section IIS Authentication Scheme Configuration.

Error: Connection with the DAF Engine refused

ip_refused.gif (20589 bytes)

The DAF Configuration Tool will communicate with the DAF Engine using a TCP/IP connection (for more information, click here). This error message will be reported when the connection is refused. It can happen in three cases:

-----------------------------------------------------------------

To use the TEXT file as a User Database:

To use the ODBC source as a User Database follow steps 1 through 5 below:

Step 1. Attach the ODBC Source (ODBC Source only!)

Step 2. Define the Update mode (ODBC Source only!)

wpe1A.jpg (46182 bytes)

Step 3. Define the column names (ODBC Source only!)

This step consists of defining which table and which columns should be used by DAF to retrieve all account information.

wpe12.jpg (47430 bytes)

Step 4. Check all ODBC Settings (ODBC Source only!)

Step 5. Attach an IP address to the Table  (ODBC Source only!)

With an ODBC source, it is possible to attach different tables to different IP addresses. Therefore, it is necessary to define which IP address should be attached to table "userdb."

Addresses listed in window "Attached IP & Web Hosts" are addresses defined in Tab "Database & Web Hosts."


6. Start the DAF User Database

At this point the basic DAF configuration is complete.


7. Test your DAF Configuration

Two sample directories are installed with the DAF Package:

--------- important.GIF (334 bytes) Important! ------------------------------------

DAF will never override NT permissions. If DAF grants access to a resource protected by NT permission (for the current NT user) access will be denied to the web client.

Therefore, you need to make sure that the default IIS NT User (IUSR_XXXXX) has read access to directories "<DAF Directory>/quickstart/www/public" and"<DAF Directory>/quickstart/www/private." An easy solution is to set NT permission EVERYONE|READ for these resources.

-------------------------------------------------------------------

In the members only directory are located five files with the following permissions:

With the test user database, access rights to resources are: 

Login,
Password
Member of
DAF Group
Access to file
default.htm
Access to file
allauth.htm
Access to file
grpall.htm
Access to file
grp1.htm
Access to file
grp2.htm
John,left grp1;grp2;grp3 Granted Granted Granted Granted Granted
Jack,blue grp1 Granted Granted Granted Granted Denied
Joe,square grp2;grp3 Granted Granted Granted Denied Granted
Jerry,fries   Granted Granted Denied Denied Denied
Anonymous   Granted Denied Denied Denied Denied

 To test your DAF configuration:

53390 bytes

In sample directory "<DAF Directory>/quickstart/www/private" access permissions are defined with a text file named DAFAUTH.INI. This file is used to define, using a simple syntax, all permission attached to all files located in the same directory.

File DAFAUTH.INI used to define permission for "<DAF Directory>/quickstart/www/private":

15946 bytes

For more information on how to protect files and directories, refer to section Managing Resource Access Permissions.


8. Setup the Web User Manager

The Web User Manager is a Web application designed to manage a DAF User Database. The DAF setup program installs by default this application. However, to use it, it is necessary to map a URL to its home page:

49833 bytes


9. How to use Logs options

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:

At this point, information on all incoming HTTP requests should be displayed live in the window.

69438 bytes

For example, to verify to which DAF User database is attached an incoming HTTP request:

HTTP Request for <192.168.1.100>,<80>,<192.168.1.100> from <192.168.1.55>,
<Mozilla/4.0 (compatible; MSIE 4.01; Windows NT)> - Attached to <userdb1>

A request for an IP address not attached to a DAF User Database would be reported as:

HTTP Request for <192.168.1.101>,<80>,<192.168.1.101> from <192.168.1.101>,
<Mozilla/4.0 (compatible; MSIE 4.01; Windows NT)> - NOT Attached

To get information on an incoming request attached to DAF User Database "userdb1":

192.168.1.100,80,:(FA100)(DAFAUTH.INI PERMISSION) Access Denied for user <>,<> 
to </quickstart/private/grp2.htm>
192.168.1.100,80,:(AA100)(DAF LOGON SUCC.) User Found : joe#grp2;grp3@ (-> ) in DAF db
192.168.1.100,80,:(AA100)(DAF LOGON SUCC.) User Found : joe#grp2;grp3@ (-> ) in DAF db
192.168.1.100,80,:(FA100)(DAFAUTH.INI PERMISSION) Access Denied for user <joe>,<> 
to </quickstart/private/grp1.htm>

Last update: Saturday, April 03, 1999 08:20