We use service accounts to run IIS App Pools under. Then we use integrated authority in our DB connection strings.
How is this affected by running an ASP.Net core site using IIS as the proxy? Is the App Pool account passed through? Do I have to do something differently in my connection string?
Related
ASP.NET Core out of the box supports hosting in IIS and self-hosting scenarios using the Kestrel and WebListener HTTP servers. Accordingly to web.config / project.json looks like IIS is used, but if so it is not clear for my "why" so, as now IIS is acting just as a reverse proxy and the application itself runs as a separate process using the Kestrel HTTP server.
So the main question is "what" and "why" is used by default, if deploy to Azure?
Yes, when you publish to Azure App Services, IIS is used to host your application. As you said, it acts as a reverse proxy to your application, which is running Kestrel HTTP server. But IIS does more than that - it also manages the application process through application pool, which includes or may include:
restarting the app when web.config changes
starting the app on the first HTTP request
running the app as a specified user
recycling the app pool (and effectively restarting the app) on certain conditions
starting multiple app processes
handle webdeploy (this is what happens when you hit "Publish" in Visual Studio
If I want to selfhost a asp.net web api application with Owin in a windows service, how can I integrate kind of a application pool recycling that IIS offers?
The answer is simple: you cannot. Application pool is an IIS feature that you can only enjoy by hosting on IIS.
I have InstallShield (IS) Basic MSI project, that creates Application Pool and installs web application on IIS under existing website.
On IIS default website is stopped and different website named WebApps using port 80 is running it uses AppPool1. Under WebApps we have several applications that use different App Pool for themselves for example AppPool2, AppPool3. When I install new application under WebApps and set its App Pool to newly created AppPool4 some applications App Pool changes to ASP.NET v4.0 AppPool1.
You can see my Application Pool and Web App settings below from IS.
Does anyone know why this could be happening?
Issue was with Web App .NET Framework version was set to v4.0 and this would cause all the Web Apps under Website to be set to use .NET Framework v4.0
I have a web app from visual studio that is using local IIS server to run. It is an MVC 3 application. I setup the application pool in my IIS (win 7 pro) to use a service account for the application identity. When I browse the site I am getting permission errors for a function on the site which I would not get if it was using the service account. This has been tested by using same service account on a development server as the application pool identity. Application executes with no errors. Could there be something in my local security policy preventing the service account from being used?
Service account is also a member of IIS_IUSRS group.
This is a network service.
How do you set the IIS application pool that a LightSwitch application is deployed to ?
For both IIS 6 and 7 ?
When using MsDeploy ?
If you want to use msdeploy.exe to deploy just the app pool to IIS 7, you can use the appPoolConfig provider. (The provider is not supported on IIS 6.)
If you’re using msdeploy.exe and want to include the application pool as part of an application deployment, you can use the -enableLink:AppPool or -enableLink:AppPoolExtension switches (they are equivalent).
Also, if you want to set the .NET Framework version of the application pool, you can use the Web Deploy appPoolNetFx provider.
Here are some references if you're going to use IIS Manager:
To set the application pool in IIS 7, go to the Application Pools reference page and follow the steps under “How to configure the application pool for an existing site or application”.
To set the application pool in IIS 6, see Configuring Application Pools in IIS 6.0.