Microsoft IIS

CertGuardian allows certificates to be installed automatically on Microsoft IIS servers through the certificates.yaml configuration file.

This file is located inside the agent's config directory:

certguardian-agent/
├── certguardian-agent.exe
└── config/
    └── certificates.yaml

Configuration Example

The following example shows a certificate that will be installed on two different IIS websites:

certificates:
  - id: 1
    installations:
      - id: public-website
        type: iis
        config:
          site: "www.example.com"
          hostname: "www.example.com"

      - id: customer-portal
        type: iis
        config:
          site: "portal.example.com"
          hostname: "portal.example.com"

Configuration Structure

id

Certificate identifier within the CertGuardian platform.

id: 1

This identifier must match the certificate identifier configured in the platform.

installations

List of installations associated with the certificate.

installations:

A certificate can have one or more installations.

installation.id

Unique installation identifier.

id: public-website

This value is used to identify the installation within the configuration file.

installation.type

Installation type that will be executed by the agent.

For IIS installations, this value must be set to:

type: iis

installation.config

Contains the Microsoft IIS-specific parameters.

config:

IIS Parameters

site

Name of the IIS website where the certificate will be installed.

site: "www.example.com"

The name must match exactly the website name configured in IIS Manager.

hostname

Hostname or HTTPS binding where the certificate will be applied.

hostname: "www.example.com"

The agent will locate the corresponding HTTPS binding and update the associated certificate.

Multiple Installations

A single certificate can be associated with multiple IIS installations.

This allows you to:

• Install the same certificate on multiple websites.
• Install the same certificate on different hostnames.
• Manage multiple HTTPS bindings using a single certificate definition.

In the example above, the certificate will be installed on two different websites:

• www.example.com
• portal.example.com

Each installation is independent and can target a different website or hostname.