Traditional Security Configuration

We won’t spend time here looking at the traditional security configuration techniques in detail, because they are just the ones you use when creating applications that don’t incorporate MTS. Instead, they depend on each component file and resource being allocated the appropriate permissions under Windows NT for the accounts that the application will run under. For a Web-based application, this will usually be the IUSR account, unless you need to limit access to individual users or groups of users. The techniques for mapping users to groups were described in the previous chapter.

A couple of points to watch out for are that you need to assign Read and/or Execute permissions for all the individual components and resources required for your application. This includes many of the files in the

Winnt

and System32
directories, as well as the specialist components in the Program
Files\Common
Files\System
directories, where the ADO and OLEDB components are stored. There may also be other components that are specific to your applications.