Windows Permissions

[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

[Daniel Walzenbach]

If so you might consider reading the following:

http://msdn.microsoft.com/msdnmag/issues/02/04/ASPSec/
http://msdn.microsoft.com/msdnmag/is...2/default.aspx

HTHs
Daniel Walzenbach

"Eric Sabine" <mo*****@hyottmail.com> schrieb im Newsbeitrag news:3f***********************@news.twtelecom.net. ..

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

[Eric Sabine]

Thank you Daniel. I read both but they are slightly different than I want because they deal with first authenticating the user. I will repost a changed question under a new thread.

Eric

"Daniel Walzenbach" <da**********************@freudenberg.de> wrote in message news:%2****************@TK2MSFTNGP11.phx.gbl...
If so you might consider reading the following:

http://msdn.microsoft.com/msdnmag/issues/02/04/ASPSec/
http://msdn.microsoft.com/msdnmag/is...2/default.aspx

HTHs
Daniel Walzenbach

"Eric Sabine" <mo*****@hyottmail.com> schrieb im Newsbeitrag news:3f***********************@news.twtelecom.net. ..

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

[Daniel Walzenbach]

Eric, sorry if I have misunderstood your question but afaik the impersonated account will be used. I'll have a look for your new post.

Daniel
"Eric Sabine" <mo*****@hyottmail.com> schrieb im Newsbeitrag news:3f***********************@news.twtelecom.net. ..
Thank you Daniel. I read both but they are slightly different than I want because they deal with first authenticating the user. I will repost a changed question under a new thread.

Eric

"Daniel Walzenbach" <da**********************@freudenberg.de> wrote in message news:%2****************@TK2MSFTNGP11.phx.gbl...
If so you might consider reading the following:

http://msdn.microsoft.com/msdnmag/issues/02/04/ASPSec/
http://msdn.microsoft.com/msdnmag/is...2/default.aspx

HTHs
Daniel Walzenbach

"Eric Sabine" <mo*****@hyottmail.com> schrieb im Newsbeitrag news:3f***********************@news.twtelecom.net. ..

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