Re: SQL and IIS on Separate machines

From: Jason Kleban (jason.kleban_at_bdhhi.com)
Date: 08/07/03

  • Next message: Rastio Hodul: "PasswordDeriveBytes and CryptoAPI" 
    Date: Thu, 7 Aug 2003 11:29:35 -0700

    Doesn't that require me to hardcode or somehow otherwise
    manage yet another password?

    Jason

    >-----Original Message-----
    >With impersonation and anonymous authentication, you will
    be giving the
    >credentials of the IIS process. Change the IIS process to
    use the domain
    >account that you want, keep impersonation on, and you
    should authenticate
    >fine.
    >
    >--
    >Chris Jackson
    >Software Engineer
    >Microsoft MVP - Windows XP
    >Windows XP Associate Expert
    >--
    >"Jason Kleban" <jason.kleban@bdhhi.com> wrote in message
    >news:008b01c35c3b$1cca1f20$a401280a@phx.gbl...
    >> I have IIS and SQL server on separate machines. The IIS
    >> machine houses a C# class library that implements the
    >> business logic and uses an approle to gain access to
    >> stored procedures on the SQL server.
    >>
    >> If I use the library in a windows app, everything works
    >> fine because my domain account, while it has no added
    >> rights on the SQL Server, can at least talk to it and
    run
    >> the sp_setapprole.
    >>
    >> The problem occurs when I try to use this library in an
    >> ASP.NET application. I get an error "Login failed for
    >> user '(null)'. Reason: Not associated with a trusted SQL
    >> Server connection."
    >>
    >> When I add <identity impersonate="true" /> to my
    >> web.config, I get "Login failed for user 'NT
    >> AUTHORITY\ANONYMOUS LOGON'."
    >>
    >> I've tried to hard code the username and password into
    the
    >> machine.config to be a domain account instead of
    >> machine:AutoGenerate, but the change doesn't seem to
    have
    >> any effect.
    >>
    >> What is the best way to handle this situation? I want
    to
    >> stick to Windows Authentication and not use SQL
    >> Authentication. I will also need windows authentication
    >> for some parts of the site, although most pages should
    be
    >> accessible by anonymous web users.
    >>
    >> I've seen many posts on the net skirting this issue, one
    >> hitting it dead on it seems (in Google) but the link is
    >> dead and the google cache didn't save it.
    >
    >
    >.
    >

  • Next message: Rastio Hodul: "PasswordDeriveBytes and CryptoAPI"

    Relevant Pages

    • Re: Windows Authentication in asp.net 2005 to SQL Server?
      ... If the domains do not trust each other, Windows authentication is not going ... Basic authentication sometimes makes the need for Kerberos delegation go ... generic account to do the backend data stuff on our SQL Server. ...
      (microsoft.public.dotnet.framework.aspnet.security)
    • Re: Remote connection failed
      ... If you are going over a remote connection or are not logging ... into the domain where SQL Server is then no, Windows ... authentication won't work. ...
      (microsoft.public.sqlserver.connect)
    • Re: Changing passwords / Blocking SA login attempts
      ... I went into the Server Config properties and changed to Windows ... My login for Start and Run SQL server was in this format. ... I am supposing this was an SQL authentication, ...
      (microsoft.public.sqlserver.security)
    • Re: SQL and IIS on Separate machines
      ... With impersonation and anonymous authentication, ... Change the IIS process to use the domain ... Windows XP Associate Expert ... > I have IIS and SQL server on separate machines. ...
      (microsoft.public.dotnet.security)
    • Windows Authentication with IIS on separate machines
      ... Yes, setting Basic Authentication in IIS works, but the ... >in SQL server but doesn't work if user account was ... >imported from a Windows account. ...
      (microsoft.public.sqlserver.security)
    • Quantcast