| Groups | Blog | Home |
iis security : Why doesn't ASP.NET 2.0 use the Network Service account
I have an asp.net 2.0 Intranet app that is installed to a Win2003 Server running IIS 6.0. This production server also hosts asp.net 1.1 apps also. I isolated the two into separate application pool on the IIS. My Intranet app loads but on login authentication, for some strange reason, IIS passes in a network user account rather than the Network Service account. Naturally authentication failed because the database is set up to allow Network Service in and not the network user account, which I know nothing about. This same Intranet app works fine in the test server that also runs on Win2003 server with IIS 6. I spent two days on this and I can't go any further. Does anybody knows what is going on? Thank you for your help in advance. Thanks, Jon
[quoted text, click to view]
On Sep 22, 12:50 am, Homer <HomerS...@gmail.com> wrote: > Hi, > > I have an asp.net 2.0 Intranet app that is installed to a Win2003 > Server running IIS 6.0. This production server also hosts asp.net 1.1 > apps also. I isolated the two into separate application pool on the > IIS. My Intranet app loads but on login authentication, for some > strange reason, IIS passes in a network user account rather than the > Network Service account. Naturally authentication failed because the > database is set up to allow Network Service in and not the network > user account, which I know nothing about. This same Intranet app > works fine in the test server that also runs on Win2003 server with > IIS 6. I spent two days on this and I can't go any further. Does > anybody knows what is going on? Thank you for your help in advance. > > Thanks, > Jon ASP.Net is flexible and allows configuration of user account to run its code. By default for ASP.Net 2.0 it is process identity, which is Network Service on IIS6 by default. If you do not see that, it means that you either configured the Application Pool to use another user identity, or you configured ASP.Net to use another identity. In either case, the problem is not "why doesn't ASP.NET 2.0 use the Network Service account", nor is it "why is IIS passing in a network user account". The problem is "Why did the user misconfigure the wrong user account for their application and don't even know it". Because by default, it should just work, according to your other configuration.. //David http://w3-4u.blogspot.com http://blogs.msdn.com/David.Wang //
As David says, something is up with your configuration:
Places to check: a) What is the web application pool configured to use in IIS Manager? b) Do you have <impersonation> enabled in your web.config file for the application? Cheers Ken -- My IIS Blog: www.adOpenStatic.com/cs/blogs/ken [quoted text, click to view] "Homer" <HomerS007@gmail.com> wrote in message
news:1190447425.532211.21630@22g2000hsm.googlegroups.com... > Hi, > > I have an asp.net 2.0 Intranet app that is installed to a Win2003 > Server running IIS 6.0. This production server also hosts asp.net 1.1 > apps also. I isolated the two into separate application pool on the > IIS. My Intranet app loads but on login authentication, for some > strange reason, IIS passes in a network user account rather than the > Network Service account. Naturally authentication failed because the > database is set up to allow Network Service in and not the network > user account, which I know nothing about. This same Intranet app > works fine in the test server that also runs on Win2003 server with > IIS 6. I spent two days on this and I can't go any further. Does > anybody knows what is going on? Thank you for your help in advance. > > Thanks, > Jon >
On Sep 23, 5:37 am, "Ken Schaefer" <kenREM...@THISadOpenStatic.com>
[quoted text, click to view] wrote: > As David says, something is up with your configuration: > > Places to check: > a) What is the web application pool configured to use in IIS Manager? > > b) Do you have <impersonation> enabled in your web.config file for the > application? > > Cheers > Ken > > -- > My IIS Blog:www.adOpenStatic.com/cs/blogs/ken > > "Homer" <HomerS...@gmail.com> wrote in message > > news:1190447425.532211.21630@22g2000hsm.googlegroups.com... > > > > > Hi, > > > I have an asp.net 2.0 Intranet app that is installed to a Win2003 > > Server running IIS 6.0. This production server also hosts asp.net 1.1 > > apps also. I isolated the two into separate application pool on the > > IIS. My Intranet app loads but on login authentication, for some > > strange reason, IIS passes in a network user account rather than the > > Network Service account. Naturally authentication failed because the > > database is set up to allow Network Service in and not the network > > user account, which I know nothing about. This same Intranet app > > works fine in the test server that also runs on Win2003 server with > > IIS 6. I spent two days on this and I can't go any further. Does > > anybody knows what is going on? Thank you for your help in advance. > > > Thanks, > > Jon- Hide quoted text - > > - Show quoted text - Hi, I created a new application pool in IIS 6 to isolate my asp.net 2.0 apps from asp.net 1.1 apps. I left the pool configuration at default and verified that the predefined identity is "Network Service". I have the same configuration in the test server and it works just fine. I do not turn on imperation in my app so by default IIS should use the Network Service account. Here's my web.config: <?xml version="1.0"?> <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/ v2.0"> <appSettings> </appSettings> <connectionStrings> <add name="csHumanResources" connectionString="Data Source=prodSql;Initial Catalog=HumanResources;Integrated Security=SSPI" providerName="System.Data.SqlClient"/> </connectionStrings> <system.net> <mailSettings> <smtp> <network host="10.162.22.1"/> </smtp> </mailSettings> </system.net> <system.web> <authentication mode="Forms"> <forms loginUrl="~/Default.aspx" timeout="10" slidingExpiration="true" /> </authentication> <membership defaultProvider="CustomizedProvider"> <providers> <add name="CustomizedProvider" type="System.Web.Security.SqlMembershipProvider" connectionStringName="csEmployeeSelfService" enablePasswordReset="true" requiresQuestionAndAnswer="false" applicationName="EOIntranet" passwordFormat="Hashed" maxInvalidPasswordAttempts="5" minRequiredPasswordLength="7" minRequiredNonalphanumericCharacters="0" passwordAttemptWindow="10" passwordStrengthRegularExpression=""/> </providers> </membership> <roleManager enabled="true" defaultProvider="CustomizedRoleProvider"> <providers> <add connectionStringName="csEmployeeSelfService" applicationName="EOIntranet" name="CustomizedRoleProvider" type="System.Web.Security.SqlRoleProvider" /> </providers> </roleManager> <pages styleSheetTheme="Forest"/> <compilation debug="true"> <assemblies> <add assembly="System.Web.Extensions.Design, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/ [quoted text, click to view] > <add assembly="System.Design, Version=2.0.0.0,Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/> <add assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/> <add assembly="System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/> <add assembly="System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/> <add assembly="System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/> <add assembly="System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/> <add assembly="System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/> <add assembly="System.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/> <add assembly="System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/> <add assembly="System.Web.Services, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/> <add assembly="System.DirectoryServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/> <add assembly="System.DirectoryServices.Protocols, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/> <add assembly="System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/> <add assembly="System.ServiceProcess, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/> <add assembly="System.Web.RegularExpressions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/> <add assembly="System.Drawing.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/> </assemblies> </compilation> <siteMap defaultProvider="AspXmlSiteMapProvider" enabled="true"> <providers> <add name="AspXmlSiteMapProvider" siteMapFile="web.sitemap" type="System.Web.XmlSiteMapProvider" securityTrimmingEnabled="true"/> </providers> </siteMap> </system.web> </configuration> Thanks, Jon
The impersonation could eventually be set at the root level.
To make sure set <identity impersonate="false" /> Leave no room for assumptions. Other options are to set a sample .ashx file on the AppDomain where you're seeing this and dump the WindowsIdentity account. Tiago Halm
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |