Re: Windows Authentication in asp.net 2005 to SQL Server?

You can definitely use Basic authentication here (along with SSL) to
authenticate the users. You might also consider using IWA as well if you
want the ability for your users to authenticate automatically.

Note that to authenticate users in your domain, your web server and SQL
server must be members of your Active Directory domain.

Additionally, to use IWA, you will need to implement Kerberos delegation so
that the web app can successfully forward the user's credentials to SQL
server. This can be tricky, but there are some great documents out there
specifying how to implement it.

If you don't have a domain, you might not want to go down this path.
ASP.NET membership might work better for you with one of the SQL-based
stores. You could possibly still use SQL authentication to SQL or maybe
Windows auth. Out of curiosity, do your connection strings to SQL use a
fixed set of credentials or insert the authenticated user's credentials?
The former is called a "trusted subsystem" model and the latter is called a
"delegated" model. This is because with a trusted subsystem, a single
trusted account is used to perform actions against the backend on behalf of
all of the users of the app, while in a delegated model, the user's
credentials are used for accessing both the frontend and backend resources.
Kerberos delegation is just a way of delegating credentials using built-in
features of Windows security.

Joe K.

"John" <IDontLikeSpam@xxxxxxxxxxx> wrote in message
news:es9fyjiPGHA.3528@xxxxxxxxxxxxxxxxxxxxxxx
Sorry if this sounds like a novice question but we've been using SQL
Server logins and passwords from our home made .asp login page with the
whole connection string and app wrapped in https for individual users to
access the databases on our SQL Server. I'm looking into moving towards
asp.net 2005 and heard using Windows authentication is a better practice
in accessing SQL Server. I was wondering if anyone could tell me how
would one go about it in that there would be an initial login page or
login pop up (like the Windows authentication popup) where individual
users would enter in their valid windows login information which would
allow them to proceed to use the .net 2005 web app that connects to our
SQL Server. Just taking a guess...would it be good to use Windows Basic
authentication where it would pop up and the individual user can enter in
their info and use https to encrypt the database and app communication
since it's in clear text?



.

Relevant Pages

  • RE: Beginners Questions
    ... We do use Windows form on the presentation layer which is on ... terminal server and call web services on the business logic side. ... of using "proxy" authentication on SQL Server. ... > I have written an app with a Windows Forms UI that is deployed to clients ...
    (microsoft.public.dotnet.distributed_apps)
  • Re: Windows Authentication and software in a hosted environment.
    ... What type of authentication are you using for the VPN? ... If you are using something like ISA server then the user is passing windows ... In my experience with hosted DB solutions almost always SQL auth is used. ...
    (microsoft.public.sqlserver.security)
  • Re: Accessing SQL Server w/ Forms on Intranet
    ... Windows Integrated Authentication as that is what our network runs on. ... > of authentication are you using on SQL Server - Windows? ...
    (microsoft.public.dotnet.distributed_apps)
  • Re: Connecting to SQL Without Windows Authentication
    ... Are you connecting to the SQL ... Server via named ... >> I have a Windows 2000 server ... If I connect using SQL Authentication, ...
    (microsoft.public.sqlserver.security)
  • Re: SQL / IIS Application Pool Identity
    ... Set the authentication tag in web.config to "windows" (this way it actually ... to sql, which will obviously be different for each user. ... I want to use the application pool identity to make the> connection to the SQL server database. ...
    (microsoft.public.dotnet.framework.aspnet.security)