microsoft/IIS.Administration

Microsoft IIS Administration API

Documentation is available at https://docs.microsoft.com/en-us/IIS-Administration

Develop and Debug with Visual Studio 2022:

Clone this project
Load the solution (Microsoft.IIS.Administration.sln) in Visual Studio
Try restoring all the NuGet packages

Open src\Microsoft.IIS.Administration\config\appsettings.json, modify the users section as below,

"users": {
  "administrators": [
    "mydomain\\myusername",
    "myusername@mycompany.com",
    "IIS Administration API Owners"
  ],
  "owners": [
    "mydomain\\myusername",
    "myusername@mycompany.com",
    "IIS Administration API Owners"
  ]
},

Run PowerShell as an Administrator
Run Configure-DevEnvironment.ps1 script in the scripts dir
From the visual studio run profile menu select option Microsoft.IIS.Administration and run the application.
If you are not able to browse the site or your getting generic browser error, most like SSL certificate is not configured for that. IIS express installs SSL certificates on port 44300-44399. Try changing the port to one of these in appsettings.json *ex: "urls":"https://:44326"**

Build the Installer:

In the following code, replace the path to match your clone location. It first starts the developer command prompt for Visual Studio 2022, publishes the solution and finally, builds the installer at installer\IISAdministrationBundle\bin\x64\Release.

%comspec% /k "C:\Program Files\Microsoft Visual Studio\2022\Preview\Common7\Tools\VsDevCmd.bat"

cd /d C:\src\repos\IIS.Administration
msbuild -restore Microsoft.IIS.Administration.sln /t:publish

build\nuget.exe restore installer\IISAdministrationSetup\packages.config -SolutionDirectory installer
msbuild installer /p:configuration=release

Installation and Known Issues:

Must first remove preview builds of .Net Core. The service does not work with preview builds of .Net Core.
Must remove previously installed versions of IIS Administration.
Repair does not work. Must do a full uninstall/re-install.
If errors occurred during installation, manually remove folder C:\Program Files\IIS Administration and Windows service "Microsoft IIS Administration".
If the step above does not fix the installation failure, manually remove user group "IIS Administration API Owners" from the host machine if it exists, and run setup again.
If you don't have permissions for the APIs, add yourself to user group "IIS Administration API Owners" on the host machine.
If you still don't have permissions after adding yourself to "IIS Administration API Owners", add yourself to users/administrators and users/owners in appsettings.json.
If you have trouble viewing the Access Token created from the API Explorer in Microsoft Edge, go to edge://settings/reset and reset your browser's settings.
Microsoft.Web.Administration.dll version conflicts with .Net 6.0: Remove all code related to "ms.web.admin.refs" in the future when it is ported to .Net 6.0.
Supports 64 bit Windows Server 2008 R2 and above

Nano Server Installation:

There is a blog post to get up and running on Nano Server located at https://blogs.iis.net/adminapi/microsoft-iis-administration-on-nano-server.

Use APIs through API Explorer

Open https://localhost:55539.
Go to Access Keys and get an access token.
Back to API Explorer and paste the Access Token.
Make sure the local machine has IIS enabled.
Go to https://localhost:55539/#/api/webserver/websites. You should see all local Web sites listed.

Click POST, paste the following as JSON request,

JSON request
{
"name": "Contoso1234",
"physical_path": "C:\\inetpub\\wwwroot",
"bindings": [
{
  "port": 8080,
  "protocol": "http",
  "ip_address": "*"
}
]
}

If you don't have permissions to create Web sites under C:\Inetpub, make sure you have files section in appsettings.json like this,

"cors": {
"rules": []
},
"files": {
"locations": [
  {
    "alias": "inetpub",
    "path": "C:\\inetpub",
    "claims": [
      "read",
      "write"
    ]
  }
}

Click -->, the new Web site should be created.
Open IIS Manager, you should see the newly created Web site under Sites.
Back to the browser, click DELETE, then -->. The newly created Web site should be deleted.

Running Tests:

Run the ConfigureDevEnvironment script with the test environment flag

C:\src\repos\IIS.Administration\scripts\Configure-DevEnvironment.ps1 -ConfigureTestEnvironment

Open the project in Visual Studio as an Administrator and launch without debugging
Make sure the appsettings.json being used is similar to the one at test\appsettings.test.json. Without the "files" section, new Web sites cannot be created. "cors" section is also required.
Open another instance of the project (also as Administrator since tests need to create new local users and enable some IIS features) and run the tests located in the 'test' folder
Tests can also be run with the CLI

Examples

C

Intialize Api Client

var apiClient = new HttpClient(new HttpClientHandler() {
   UseDefaultCredentials = true
}, true);

// Set access token for every request
apiClient.DefaultRequestHeaders.Add("Access-Token", "Bearer {token}");

// Request HAL (_links)
apiClient.DefaultRequestHeaders.Add("Accept", "application/hal+json");

Get Web Sites

var res = await apiClient.GetAsync("https://localhost:55539/api/webserver/websites");

if (res.StatusCode != HttpStatusCode.OK) {
  HandleError(res);
  return;
}

JArray sites = JObject.Parse(res.Content.ReadAsStringAsync().Result).Value<JArray>("websites");

Create a Web Site


var newSite = new {
  name = "Contoso",
  physical_path = @"C:\inetpub\wwwroot",
  bindings = new object[] {
    new {
      port = 8080,
      protocol = "http",
      ip_address = "*"
    }
  }
};

res = await apiClient.PostAsync("https://localhost:55539/api/webserver/websites", 
    new StringContent(JsonConvert.SerializeObject(newSite), Encoding.UTF8, "application/json"));

if (res.StatusCode != HttpStatusCode.Created) {
    HandleError(res);
    return;
}

JObject site = JObject.Parse(res.Content.ReadAsStringAsync().Result);

Update a Web Site


var updateObject = new {
  bindings = new object[] {
    new {
      port = 8081,
      protocol = "http",
      ip_address = "*"
    }
  }
};

var updateRequest = new HttpRequestMessage(new HttpMethod("PATCH"),
    "https://localhost:55539" + site["_links"]["self"].Value<string>("href"));

updateRequest.Content = new StringContent(JsonConvert.SerializeObject(updateObject), Encoding.UTF8, "application/json");

res = await apiClient.SendAsync(updateRequest);

if (res.StatusCode != HttpStatusCode.OK) {
    HandleError(res);
    return;
}

site = JObject.Parse(res.Content.ReadAsStringAsync().Result);

Delete a Web Site

res = await apiClient.DeleteAsync("https://localhost:55539" + site["_links"]["self"].Value<string>("href"));

PowerShell

There is a utils.ps1 script that demonstrates how to generate an access token from PowerShell.

# Replace the path to match your clone location
$accessToken = C:\src\repos\IIS.Administration\scripts\utils\utils.ps1 Generate-AccessToken -url "https://localhost:55539"

Get Web Sites

# Supply an access token to run the example

$accessToken = "{Some Access token}"

$headers = @{ "Access-Token" = "Bearer $accessToken"; "Accept" = "application/hal+json" }

$response = Invoke-RestMethod "https://localhost:55539/api/webserver/websites" -UseDefaultCredentials -Headers $headers

$response.websites