Administration Guide

A Sample Scenario with Client Authentication and a Windows NT Client Machine:

Dale, the administrator, logs on to SRV3 and changes the authentication for the database instance to Client:
```
   db2stop myinst
   db2 update dbm cfg using authentication client
   db2start myinst
```
Ivan, at a Windows NT client machine, logs on to the DC1 domain (that is, he is known in the DC1 SAM database).
Ivan then connects to a DB2 database that is cataloged to reside on SRV3:
```
   DB2 CONNECT to remotedb user Ivan using johnpw
```
Ivan's machine validates the username and password. The API used to find this information first searches the local machine (Ivan) and then the domain controller (DC1) before trying any trusted domains. Username Ivan is found on DC1.
Ivan's machine then validates the username and password with DC1.
SRV3 then:
1. Determines where Ivan is known.
2. Finds out whether Ivan is an administrator by asking DC1.
3. Enumerates all Ivan's groups by asking DC1.

Note: Before attempting to connect to the DB2 database, ensure that DB2 for Window NT Security Service has been started. The Security Service is installed by DB2 and is set up to run as a Windows NT service; however, it is not started automatically. To start the DB2 Security Service, enter the NET START DB2NTSECSERVER command.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]