Re: SQL2k3 connectivity problems
From: Itai Raz (do_not_reply_because_at_this.email.is.fake)
Date: 11/08/04
- Next message: Dallara: "Does anyone know anything about this BUG?"
- Previous message: sal: "How can I have a user select a local MS SQL database using vb.net? TIA SAL"
- In reply to: Jeff Dillon: "Re: SQL2k3 connectivity problems"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 9 Nov 2004 00:25:18 +0200
What else would you use?
I do not want to have a connection string that contains my user and
password. I want one user that my app is running under. All my services are
running under that user. IIS is configured to use this user for anonymous.
All I want is that ASP.Net will use it as well. I have impersonation as true
in web.config. Why wouldn't ASP.Net just follow the rules, and impersonate
as the IIS user?
-- --itai "Jeff Dillon" <jeff@removeemergencyreporting.com> wrote in message news:OmWmWXbxEHA.1452@TK2MSFTNGP09.phx.gbl... > Why are you using integrated security in an ASP.NET app? > > Jeff > > "Rich" <Rich@discussions.microsoft.com> wrote in message > news:66E5E68A-8BC3-4D03-8248-17B2ABD49968@microsoft.com... > > This stuff gets confusing - and it doesn't always seem like it works "as > > advertised" - so you have to experiment. At any rate, I believe that, > when > > you set the <IDENTITY> tag in web.config, it only takes effect when 1) the > > IMPERSONATE attribute is set to TRUE and 2) IIS is configured NOT to allow > > Anonomous access. > > > > If that's not an option and you really need to use integrated security, I > > quite sure you cad code the application to impersonate. > > > > Good Luck > > > > "Itai Raz" wrote: > > > > > Hi Guys, > > > > > > We are making use of SQL2K DB installed on W2003 server for the first > time. > > > We bumped into a whole lot of security related issues, that we managed > to > > > solve, and we have one (hopefully) last outstanding problem keeping us > in > > > the dark. We have some ASP.Net code that is trying to access the DB from > the > > > application servers using a COM+ data access layer. It seems like no > matter > > > what we do, the user which ASP.Net is impersonating in order to access > the > > > DB is the "computer account" on the domain (domain\machineName$). We > tried > > > tweaking machine.config and web.config (impersonation is active and the > IIS > > > settings are set to operate under a privileged user). Doesn't look like > > > anything is changing. The connection string we're using is of course > with > > > integrated security sspi. Everything works perfectly for pure COM > objects > > > called from ASP, but ASP.Net insists on running under the "wrong" user. > > > > > > Anyone seen this one before, and happens to know what needs to be done > to > > > resolve this? > > > > > > Thanks, > > > > > > --itai > > > > > > > > > > > > > >
- Next message: Dallara: "Does anyone know anything about this BUG?"
- Previous message: sal: "How can I have a user select a local MS SQL database using vb.net? TIA SAL"
- In reply to: Jeff Dillon: "Re: SQL2k3 connectivity problems"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
