Re: Connecting to DB and other resources outside the domain
From: Paul Clement (UseAdddressAtEndofMessage_at_swspectrum.com)
Date: 07/14/05
- Next message: RedEye: "Re: ASP.NET v2.0 login control issue with SQL Server 2000"
- Previous message: J-T: "Re: Windows integrated"
- In reply to: Dominick Baier [DevelopMentor]: "Re: Connecting to DB and other resources outside the domain"
- Next in thread: J-T: "Re: Connecting to DB and other resources outside the domain"
- Reply: J-T: "Re: Connecting to DB and other resources outside the domain"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 14 Jul 2005 11:39:45 -0500
On Thu, 14 Jul 2005 08:19:26 -0700, Dominick Baier [DevelopMentor]
<dbaier@pleasepleasenospamdevelop.com> wrote:
Hi Dominick,
¤ oh - sorry - forgot that he was impersonating...
¤
¤ the problem is not integrated auth - the problem is using NTLM and non-domain
¤ accounts.
¤
¤ NTLM cannont delegate - it is just not designed to do that.
¤
¤ you have two choices:
¤
¤ a) using sql authentication, which means you have to pass uname/password
¤ in the connection string
¤ b) use a custom worker process identity (if running under IIS6)
Yeah, either of those should work.
The question was multi-posted in another newsgroup and I referred him to the following doc:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/SecNetch05.asp
Paul
~~~~
Microsoft MVP (Visual Basic)
- Next message: RedEye: "Re: ASP.NET v2.0 login control issue with SQL Server 2000"
- Previous message: J-T: "Re: Windows integrated"
- In reply to: Dominick Baier [DevelopMentor]: "Re: Connecting to DB and other resources outside the domain"
- Next in thread: J-T: "Re: Connecting to DB and other resources outside the domain"
- Reply: J-T: "Re: Connecting to DB and other resources outside the domain"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]