connecting to sql server with windows authentication
From: Mark (mfield_at_idonotlikespam.cce.umn.edu)
Date: 01/20/04
- Next message: ASP.Net User: "Authentication"
- Previous message: ASP.Net User: "restrict 1 active session per user"
- Next in thread: Alek Davis: "Re: connecting to sql server with windows authentication"
- Reply: Alek Davis: "Re: connecting to sql server with windows authentication"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 20 Jan 2004 15:13:34 -0600
I'm confounded how difficult it is to setup a connection from an ASP.NET
application to SQL Server on a different machine in the same windows domain
using windows authentication. My research has found the following options:
1. Use delegation to leverage the current user's account.
2. Replace the ASPNET local account that is running .NET applications on the
web server with a domain account.
3. Use impersonation specifiying a specific domain user and password in the
web.config.
In options 2 and 3 above, the new account must be granted all the rights
that the ASPNET account comes with by default. Moreover, if you have a
development machine, a live machine, and local installs of IIS for all your
developers, the rights must be recreated on every blasted box. That sounds
like a maintenance nightmare. Option 1 raises all sorts of security
concerns. Understandably, our DBA wants to keep SQL Server authentication
turned off since we have a windows network.
Am I missing something here? What is the "obvious" choice?
Thanks in advance.
Mark
- Next message: ASP.Net User: "Authentication"
- Previous message: ASP.Net User: "restrict 1 active session per user"
- Next in thread: Alek Davis: "Re: connecting to sql server with windows authentication"
- Reply: Alek Davis: "Re: connecting to sql server with windows authentication"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
