ASPNET and NETWORK SERVICE accounts hitting SQL Server

Ask a Question related to ASP.NET Security, Design and Development.

  1. #1

    Default ASPNET and NETWORK SERVICE accounts hitting SQL Server

    Hello.

    Running IIS 6 and ASP.NET, the only way an application can access SQL Server
    seems to be as "NT AUTHORITY / NETWORK SERVICE" (or an alias specified in
    the <identity> element within "web.config"). This is analagous to the
    "ASPNET" user for IIS 5 and ASP.NET.

    In a secure (SSL) web running in IIS 6, we're interested in getting from
    ASP.NET the behavior we get from ASP 3.0. When the ASP application logs
    onto the SQL Server database, it does so under the logon of the actual user.
    There does not appear to me to be a way to make this happen. And, as a
    result, we feel as though we have lost a layer of security--the security of
    the database.

    Any ideas or suggestions are welcome.

    Thanks,
    Jim


    Jim Moon Guest

  2. Similar Questions and Discussions

    1. Acrobat Pro 9 crashes when opened on network accounts
      As was mentioned before a local user has no problem. With a networked user (home on a 10.5.4 server) we observe the same lockup as described above....
    2. Access Denied - Network Service vs Local Service
      I have been struggling with my ASP.NET (V1.1 sp1) websites getting an 'Access Denied' message. I have track down the problem (I think) to the IIS...
    3. Server 2003 upgrade - XP accounts
      We currently have an NT4.0 single server domain with XP workstations that have domain user accounts set up. We are looking on updating the NT4.0...
    4. ASPNET Account Security Problem - Running a Web Application over a network share
      All, If anyone has been following my trials over the last week see(Setting up a Web Application on IIS 5.1 and ASP.Net Security Problems). I'm...
    5. URGENT: Loss of wireless connection when hitting another wireless network
      1. change the channel on the wireless router 2. make sure the SSID name is not what shipped in the box 3. uncheck the advanced setting to...
  3. #2

    Default Re: ASPNET and NETWORK SERVICE accounts hitting SQL Server

    Inside
    <system.web>
    I added
    <identity impersonate="true" />

    It worked like a charm!

    Jim




    "Jim Moon" <jmoon()at()uab.edu> wrote in message
    news:%23Vv1BatXEHA.3156@TK2MSFTNGP12.phx.gbl...
    > Hello.
    >
    > Running IIS 6 and ASP.NET, the only way an application can access SQL
    Server
    > seems to be as "NT AUTHORITY / NETWORK SERVICE" (or an alias specified in
    > the <identity> element within "web.config"). This is analagous to the
    > "ASPNET" user for IIS 5 and ASP.NET.
    >
    > In a secure (SSL) web running in IIS 6, we're interested in getting from
    > ASP.NET the behavior we get from ASP 3.0. When the ASP application logs
    > onto the SQL Server database, it does so under the logon of the actual
    user.
    > There does not appear to me to be a way to make this happen. And, as a
    > result, we feel as though we have lost a layer of security--the security
    of
    > the database.
    >
    > Any ideas or suggestions are welcome.
    >
    > Thanks,
    > Jim
    >
    >

    Jim Moon Guest

  4. #3

    Default Re: ASPNET and NETWORK SERVICE accounts hitting SQL Server

    Inside
    <system.web>
    I added
    <identity impersonate="true" />

    It works great!

    Jim



    "Jim Moon" <jmoon()at()uab.edu> wrote in message
    news:%23Vv1BatXEHA.3156@TK2MSFTNGP12.phx.gbl...
    > Hello.
    >
    > Running IIS 6 and ASP.NET, the only way an application can access SQL
    Server
    > seems to be as "NT AUTHORITY / NETWORK SERVICE" (or an alias specified in
    > the <identity> element within "web.config"). This is analagous to the
    > "ASPNET" user for IIS 5 and ASP.NET.
    >
    > In a secure (SSL) web running in IIS 6, we're interested in getting from
    > ASP.NET the behavior we get from ASP 3.0. When the ASP application logs
    > onto the SQL Server database, it does so under the logon of the actual
    user.
    > There does not appear to me to be a way to make this happen. And, as a
    > result, we feel as though we have lost a layer of security--the security
    of
    > the database.
    >
    > Any ideas or suggestions are welcome.
    >
    > Thanks,
    > Jim
    >
    >

    Jim Moon Guest

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139