Implementing Windows Authentication with .NET Impersonation is fairly simple to set up.
Step 1: Add a line to the application’s Web.config file specifying the desired domain user account and password as the anonymous user for the Web application. Within the <system.web> section, add:
<identity impersonate="true" />
Step 2: Configure the anonymous user within Microsoft IIS for the web site (or virtual directory) on the Directory Security tab by clicking the Edit Anonymous access and authentication control button.
Step 3: Manually create a virtual directory in Microsoft IIS for your application. Iron Speed Designer may not be able to create the virtual directory for you automatically.
Step 4: You may need to manually compile your application using the CompileApplication.bat utility.
Step 5: When running the application after changing the application to use a domain account using .NET impersonation, the application can’t access the data, even though the application domain account is a DBO of the application database. This is because Iron Speed Designer creates the stored procedures as owned by the Iron Speed Designer application user account rather than owned by DBO. This prevents the application, which uses a different application account, from accessing the stored procedures.
As a temporary workaround, make the Iron Speed Designer application user account an “sa” (system administrator) rather than a DBO. Iron Speed Designer then properly makes the ownership of the stored procedures DBO, and the application user account is able to access the data.