SQL Server Access using Windows NT and ASP.NET
From: Aaron Ghadiyali (aghadiyali_at_atlantaregional.com)
Date: 08/26/03
- Next message: Keith Patrick: "Re: Application Security"
- Previous message: Aaron Ghadiyali: "Parsing Domain Groups with .NET"
- Next in thread: I.Charitopoulos: "DESCryptoServiceProvider weak and semi-weak keys"
- Reply: I.Charitopoulos: "DESCryptoServiceProvider weak and semi-weak keys"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 26 Aug 2003 11:00:06 -0700
Hello,
We are trying to use a seperate SQL Server Database
Server and a Web Server to use Windows NT Authenication
against the SQL Server. From what I have read on the
Microsoft sites, you can only use an impersonated user if
the SQL Server and Web Server is on the same box,
otherwise it passes the ASPNET_USER or NETWORK SERVICE
(win2003) to the database for credentials. Surely there is
a way to do this?
We want to be able to have an ASP.NET web app on one
machine and when completing functions within that app that
use the database, have it pass through the logged in Users
credentials to the database, instead of the Web Server
account. This seems to work ok with FAT Clients, but
ASP.NET apps pass the ASPNET user, and not the logged in
domain user. I can only setup impersonation to use a
domain account I SPECIFY in web config, not one that is
dynamically logged into the app. Any help is appreciated!
- Next message: Keith Patrick: "Re: Application Security"
- Previous message: Aaron Ghadiyali: "Parsing Domain Groups with .NET"
- Next in thread: I.Charitopoulos: "DESCryptoServiceProvider weak and semi-weak keys"
- Reply: I.Charitopoulos: "DESCryptoServiceProvider weak and semi-weak keys"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|