Trusted connections??

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Paul M (masonp_at_trials.bham.ac.uk)
Date: 02/02/04 

Date: Mon, 2 Feb 2004 10:16:55 -0000

Hi folks,

Just want to make sure I've got this right.

I've got an application I want to authenticate to the domain i.e. an
intranet app. I've set this up (all the web.config items are in place and
everythings tickety boo) and I can get the username and various other bits
of info from a WindowsIdentity object. So far so good.

When I try and connect to my SQL 2K server however using a trusted
connection, the system will either use the account that ASP.NET runs under
in IIS or I have to switch impersonation on and use a user at my discretion.

Either way, it doesn't matter who's using the application, each individual
session will always use the one account to make a trusted SQL server
connection. Correct?? So I'll always have to replicate some security
structure in the database i.e. create and maintain and User table if I want
to use a trusted connection.

Is this something that's going to get fixed (it's not a feature) in Whidbey?
Having read a number of books about this, none of the authors seem to find
this inconsistency odd, which I find odd. It's as if it's perfectly natural
for the framework to be able to pick up the domain user data, but not let
SQL server use it. To me it's the king of mildly annoying and screamingly
obvious bug I normally associate with the Unix crowd.

I'm tempted just to use Forms authentication and not bother with integrated
security until they sort this out. Would that be a better move?

Any comments and advice would be much appreciated...

Cheers...Paul

Relevant Pages

  • How to enable Windows Authentication
    ... web app using information from ... it and authenticate with a known good user name and password from my local ... Web.Config (notice the commented out connection string) ... under the default settings SQL Server does not allow remote connections. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Trusted connections??
    ... running SQL server and want it to use the domain credentials of the client? ... called account delegation or something. ... > connection, the system will either use the account that ASP.NET runs under ... > this inconsistency odd, which I find odd. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: intermittent connection problems
    ... If SQL Server can not authenticate the user against the Domain Controller, ... > We are having an intermittent connection problems with some DTS ... > Client network configuration TCP/IP NamePipes ...
    (microsoft.public.sqlserver.connect)
  • Re: Error "SQL Server does not allow remote connections"
    ... The application could not connect to the sql server db. ... network is blocking the connection. ... SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 ... integratedSecurity, SqlConnection owningObject) +737554 ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Connection from remote computer to network SQL Server
    ... There is no firewall on the W2K machine acting as the SQL server. ... I tried making the SQL machine a "trusted" on the router. ... connection works. ... To find the IP address of your computer inside the network, ...
    (microsoft.public.access.adp.sqlserver)