E
Eric Sabine
Note: even though I start out talking about SQL server, this isn't about SQL
Server
In an app I need to execute a stored procedure in SQL Server. The code is
simple enough, but the connection permissions is the issue. I could use a
SQL account, as in
"server=servername;uid=user;pwd=password;"
but in the stored procedure, active directory is accessed and the sproc
returns some permissions errors. So I figured that I should use NT
authentication as in
"server=servername;integrated security=sspi;database=somedatabase"
This is about the point I get lost. I see in some posts people saying "use
impersonation" etc. as in
<authentication mode="Windows" />
<identity impersonate="true" userName="NT Account Name"
password="accountPassword" />
Will someone explain to me how this is supposed to work. I'm sketchy on
what user account will be used here. Is it the impersonate account? Or a
service account? Or the security account on the web site? Hope this makes
sense. Perhaps all I need is a lesson on the users and accounts.
Eric
Server
In an app I need to execute a stored procedure in SQL Server. The code is
simple enough, but the connection permissions is the issue. I could use a
SQL account, as in
"server=servername;uid=user;pwd=password;"
but in the stored procedure, active directory is accessed and the sproc
returns some permissions errors. So I figured that I should use NT
authentication as in
"server=servername;integrated security=sspi;database=somedatabase"
This is about the point I get lost. I see in some posts people saying "use
impersonation" etc. as in
<authentication mode="Windows" />
<identity impersonate="true" userName="NT Account Name"
password="accountPassword" />
Will someone explain to me how this is supposed to work. I'm sketchy on
what user account will be used here. Is it the impersonate account? Or a
service account? Or the security account on the web site? Hope this makes
sense. Perhaps all I need is a lesson on the users and accounts.
Eric