mirror of
https://github.com/win-acme/win-acme.git
synced 2026-04-27 03:55:56 +03:00
Page:
Installation plugins
Pages
A specified logon session does not exist
Advanced logging
Advanced usage
Apache 2.4 basic usage
Application Logging
Application Settings
Azure DNS validation
Basic usage
CSR Plugins
Command Line Arguments
Command line
Create a SAN certificate
Custom plugins
DNS validation plugins
Development
Enhancement voting
Example Scripts
HTTP Validation Plugins
HTTPS Binding With Specific IP
Home
How To Run
How to Compile From Source Code
IIS 7.5 and Lower
Install script
Installation plugins
Issues and workarounds
Load balancing
Microsoft Exchange
Microsoft Remote Desktop Server
Migration to v1.9.5
Migration to v1.9.9
Migration to v2.0.0
Missing Certificate Chain
Plugins
Renewal Management
Store plugins
Target plugins
Task Scheduler
Uninstall instructions
Upgrades
Validation issues
Validation plugins
web_config.xml
No results
20
Installation plugins
Hefin Sankala edited this page 2019-04-12 18:31:35 +01:00
Installation plugins are responsible for making the necessary changes to your application(s) after successfully creating or renewing a certificate. Currently there are three of these plugins.
IIS Web
Create or update website bindings in IIS
- Existing https bindings in any site linked to the previous certificate are updated to use the new certificate.
- Hosts names which are determined to not yet have been covered by any existing binding, will be processed further.
- All existing https bindings in target site whose hostnames match with the new certificate are updated to use the new certificate. This happens even if they are using certificates issued by other authorities. (Note that if you want to prevent this from happening, you can use the
--excludebindingsswitch). - If no existing https binding can be found, a new binding is created in the target website. It will use port 443 unless a different one is specified with the
--sslportswitch. - New bindings will be created or updated for matching host headers with the most specific match. E.g. if you generate a certificate for
a.b.c.com, the order of preference for the binding creation/change will be:- a.b.c.com
- *.b.c.com
- *.c.com
- *.com
- Default (emtpy) binding
- If the certificate contains a wildcard domain, the order of preference will be:
- *.a.b.c.com
- x.a.b.c.com
- The first preferred option be created from scratch if none of the later options are available.
- All existing https bindings in target site whose hostnames match with the new certificate are updated to use the new certificate. This happens even if they are using certificates issued by other authorities. (Note that if you want to prevent this from happening, you can use the
- Unattended
--installation iis [--installationsiteid x] [-sslport x]
IIS FTP
Create or update FTP site certificate in IIS
- Any existing FTP sites linked to the previous certificate are updated to use the new certificate.
- The target FTP site will be updated to use the new certificate.
- Unattended
--installation iisftp [--installationsiteid x]
Script
Run external script, as described here.
- Unattended
--installation script --script C:\script.bat [--scriptparameters x]
Multiple
More than one plugin can run by choosing them in order of execution.
- Unattended
--installation iis,iisftp,manualor--installation manual,iis
None
Do not run any installation steps
- Unattended
--installation none
Please refer to https://pkisharp.github.io/win-acme/ for up-to-date documentation.