Skip to main content

IIS – Avoid giving file access when using Windows Authentication

In our continuous effort to improve security measures and evolve to a 'least privilege' setup, we started to remove user access to disks on our IIS web servers. For most applications this turned out not be an issue, but applications using Windows Authentication started to fail. Let’s investigate what is happening and how we can fix this.

Anonymous Authentication

Let me first explain what is going on for applications that are not using Windows Authentication. These applications are configured to use Anonymous Access and the anonymous user identity is set to a specific user account or the Application pool identity. This means that only these users needs to have access to the folders on disk.

Windows Authentication

Once we move to Windows Authentication the situation gets more complex. Now the user that is authenticated needs access on disk to be able to access the site. So probably the easiest solution would be to grant the user access to disk (or just give the Everyone account access), but of course than we are throwing our ‘least privilege’ philosophy out of the window. 

There are 2 possible solutions for this:

  1. Use the ‘Connect As’ feature
  2. Use the ‘authenticatedUserOverride’ setting

Connect As

  • Go to your site Basic settings in IIS and click on the Connect as… button:

  • Here specify a specific user instead of the application user:

AuthenticatedUserOverride

Starting from IIS 7.5 you get an extra option, you can set the ‘authenticatedUserOverride’ property to ‘UseWorkerProcessUser’.

  • Go to your site and click on the Configuration Editor:

  • Choose the “system.webServer/serverRuntime” section::

  • Update the authenticatedUserOverride property and set it to UseWorkerProcessUser:

Now you are in the same scenario as with the anonymous authentication and you only need to grant specific users access to disk.

More information: jaroslad - What does the authenticatedUserOverrideUser do? (iis.net)

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more