Passthrough authenication w/ SQL trusted connection
From: Steve Kallal (stevekallal_at_newsgroups.nospam)
Date: 03/23/04
- Next message: bruce barker: "Re: Windows Auth -- double hop issue??"
- Previous message: Joe Kaplan \(MVP - ADSI\): "Re: Windows Auth -- double hop issue??"
- Next in thread: [MSFT]: "RE: Passthrough authenication w/ SQL trusted connection"
- Reply: [MSFT]: "RE: Passthrough authenication w/ SQL trusted connection"
- Reply: Ken Schaefer: "Re: Passthrough authenication w/ SQL trusted connection"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 22 Mar 2004 15:31:08 -0800
I have been searching for an answer to this in vain. Currently we have a hard coded SQL account for all of our ASP .NET applications. We want to use an SQL Server trusted connection instead. In the documentation I find that I can map all users to a single domain user such as the following:
<identity impersonate="true" userName="domain\username" password="password"/>
However this is not what I want. For example, if domain\janedoe is using the web app, then I would want domain\janedoe to be passed to SQL Server using a trusted connection. It is not acceptable to have all users mapped to a single domain account.
I am currently using Windows Authentication in the Web App. Anonymous access is turned OFF for the app in IIS.
Thanks in Advance!
- Next message: bruce barker: "Re: Windows Auth -- double hop issue??"
- Previous message: Joe Kaplan \(MVP - ADSI\): "Re: Windows Auth -- double hop issue??"
- Next in thread: [MSFT]: "RE: Passthrough authenication w/ SQL trusted connection"
- Reply: [MSFT]: "RE: Passthrough authenication w/ SQL trusted connection"
- Reply: Ken Schaefer: "Re: Passthrough authenication w/ SQL trusted connection"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|