user impersonation

  • Thread starter Thread starter Itai Raz
  • Start date Start date
I

Itai Raz

This used to work for us under Windows 2000 server, but doesn't seem to work
with Windows 2003.

We are accessing an SQL Server using integrated security from ASP.Net. For
some reason it seems like the user that ASP.Net is using to connect to the
DB is domain\machineName$. I don't understand why that is, since I have an
account set up for the IIS app to run under, and i have impersonation set to
true in the web.config file for the app. My understanding is that if
impersonation is true in web.config, then the user under which my app is
supposed to run is the IIS user.

What am I doing wrong?
 
2003 uses application pools. set the application pool account to your
desired account, not iis.

-- bruce (sqlwork.com)


| This used to work for us under Windows 2000 server, but doesn't seem to
work
| with Windows 2003.
|
| We are accessing an SQL Server using integrated security from ASP.Net.
For
| some reason it seems like the user that ASP.Net is using to connect to the
| DB is domain\machineName$. I don't understand why that is, since I have an
| account set up for the IIS app to run under, and i have impersonation set
to
| true in the web.config file for the app. My understanding is that if
| impersonation is true in web.config, then the user under which my app is
| supposed to run is the IIS user.
|
| What am I doing wrong?
|
| --
| --itai
|
|
 
Back
Top