Installing Certification Authority Web Enrollment (CAWE)

The following describes how to install Certificate Authority Web Enrollment (CAWE).

The certificate authority web registration is a very old feature from Windows 2000 times - and was last adapted with the release of Windows Server 2003. Accordingly, the code is old and potentially insecure. Likewise, the function supports No certificate templates with version 3 or newer - This means that certificate templates that use functions introduced with Windows Vista / Windows Server 2008 or newer cannot be used. It is recommended that you do not use the certificate authority web registration and instead request certificates via on-board resources or the PSCertificateEnrollment PowerShell module.

The following instructions initially install the roller with the default settings. An adjustment is made in the respective course of the instructions.

It is recommended to install the web registration on a dedicated server.

Setting up security permissions and firewall shares

Install role files and dependencies

This step is not strictly necessary because it is done as a dependency anyway. If an Internet Information Service (IIS) Web Server is not yet installed on the target server, it can be installed using the following command with the default settings and management tools.

Install-WindowsFeature Web-Server -IncludeManagementTools

Then the binaries for the CAWE can be installed.

Install-WindowsFeature ADCS Web Enrollment

Setting up the CAWE role

The following PowerShell command is used to set up the CAWE role:

Install-AdcsWebEnrollment -CAConfig "{ConfigSring}" -Force

The placeholders mean the following:

  • The placeholder {ConfigString} denotes the configuration string for the certification authority in the format "fully-qualified-hostname\common-name-of-CA", for example "CA03.intra.adcslabor.de\ADCS Labor Issuing CA 2".

A first test by calling the CAWE can now be done via the following address:

http://{servername-CAWE}/certsrv

At this point, no delegation settings have been made and no SSL certificate is available yet. This means that the credentials are transmitted in plain text and that no certificates can be requested yet. Both will be configured in the further course of the tutorial.

Setting up Secure Sockets Layer for the CAWE

Even if CAWE works without Secure Sockets Layer (SSL), it is recommended to apply for a certificate and allow connections only via SSL. How to configure a certificate template for such a certificate is described in the article "Configuring a Secure Socket Layer (SSL) Certificate Template for Web Server" described.

The activation of SSL for the CAWE is described in the article "Enabling Secure Sockets Layer (SSL) for Certificate Authority Web Enrollment (CAWE)." described.

The identity within the SSL certificate must match either the fully qualified server name, or the alias should the CAWE be operating with one.

Configuring the service account for the CAWE

The configuration of service accounts for CAWE is described in the following articles:

Related links:

External sources

en_USEnglish