Ask a Question related to ASP.NET Security, Design and Development.
-
Kelly D. Jones #1
Impersonation and delegation
I've read many messages and even more technotes, but I still can't get the
following scenario to work:
I have a Windows 2003 web server and a separate Windows 2000/SQL server,
both in the same Active Directory on our LAN. I need to flow the user
credentials from 2000/XP clients, to the web server, and then onto the SQL
server.
IIS is set to only allow Windows integrated authentication.
My connection string is "workstation id=C3PO;packet size=4096;integrated
security=SSPI;data source=BUNSEN;persist security info=False;initial
catalog=Website" (I'm using VS.Net 2003)
I set the user account to be "Trusted for delegation". I set both server
computer accounts to be Trusted for delegation also.
I set the web.config file to:
<identity impersonate="true" />
<authentication mode="Windows" />
<authorization>
<allow users="*" />
<disallow users="?" />
Authentication works to the web server, but I get the following error when I
try to access the SQL server :
"Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'."
Any tips/help would be greatly appreciated,
---
Kelly D. Jones
[email]kdjones74@hotmail.com[/email]
Kelly D. Jones Guest
-
ASP.NET Impersonation / delegation
you are on the right track. ntlm will not delegate even if your security team allowed delegation, only digest allows delegation. on win2k you... -
ASP.NET Impersonation & Delegation
I have read various articles regarding explaining ASP.Net security model. I have one simple question regarding Delegation that i can't seemed to... -
Impersonation, Delegation & SQL Server
I bailed on this before and just went to Basic Authentication and told the users they would have to live with signing on again.... but now I need to... -
Impersonation or Delegation?
A client makes a request that executes a stored procedure in SQL Server. That stored procedure attempts to read a file on the web server but fails... -
Impersonation/Delegation security considerations
I'm having trouble finding specific documentation regarding the negative impact of using delegation in a Windows 2000 environment. I've read... -
Eric #2
Re: Impersonation and delegation
Try adding "Network Library=DBMSSOCN" for TCP/IP access or "Network
Library=DBNMPNTW" for named pipe access to your connect string. Most of the
stuff says named pipes won't work so use TCP/IP but we found the opposite to
be true. Something else to check into is something called a service
principal name. I'm not to clear on how to set it up or what it does
exactly, our DBA figured out and set that up. It has something to do with
helping the credentials get from one server to another when using the web
application.
Eric
"Kelly D. Jones" <kdjones74@hotmail.com> wrote in message
news:%23bajQOoZDHA.2668@TK2MSFTNGP09.phx.gbl...I> I've read many messages and even more technotes, but I still can't get the
> following scenario to work:
>
> I have a Windows 2003 web server and a separate Windows 2000/SQL server,
> both in the same Active Directory on our LAN. I need to flow the user
> credentials from 2000/XP clients, to the web server, and then onto the SQL
> server.
>
> IIS is set to only allow Windows integrated authentication.
>
> My connection string is "workstation id=C3PO;packet size=4096;integrated
> security=SSPI;data source=BUNSEN;persist security info=False;initial
> catalog=Website" (I'm using VS.Net 2003)
>
> I set the user account to be "Trusted for delegation". I set both server
> computer accounts to be Trusted for delegation also.
>
> I set the web.config file to:
> <identity impersonate="true" />
> <authentication mode="Windows" />
> <authorization>
> <allow users="*" />
> <disallow users="?" />
>
>
> Authentication works to the web server, but I get the following error when> try to access the SQL server :
> "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'."
>
> Any tips/help would be greatly appreciated,
> ---
> Kelly D. Jones
> [email]kdjones74@hotmail.com[/email]
>
>
Eric Guest



Reply With Quote

