3 function deploy_challenge {
4 local DOMAIN="${1}" TOKEN_FILENAME="${2}" TOKEN_VALUE="${3}"
6 # This hook is called once for every domain that needs to be
7 # validated, including any alternative names you may have listed.
11 # The domain name (CN or subject alternative name) being
14 # The name of the file containing the token to be served for HTTP
15 # validation. Should be served by your web server as
16 # /.well-known/acme-challenge/${TOKEN_FILENAME}.
18 # The token value that needs to be served for validation. For DNS
19 # validation, this is what you want to put in the _acme-challenge
20 # TXT record. For HTTP validation it is the value that is expected
21 # be found in the $TOKEN_FILENAME file.
24 function clean_challenge {
25 local DOMAIN="${1}" TOKEN_FILENAME="${2}" TOKEN_VALUE="${3}"
27 # This hook is called after attempting to validate each domain,
28 # whether or not validation was successful. Here you can delete
29 # files or DNS records that are no longer needed.
31 # The parameters are the same as for deploy_challenge.
34 function deploy_cert {
35 local DOMAIN="${1}" KEYFILE="${2}" CERTFILE="${3}" FULLCHAINFILE="${4}" CHAINFILE="${5}"
37 # This hook is called once for each certificate that has been
38 # produced. Here you might, for instance, copy your new certificates
39 # to service-specific locations and reload the service.
43 # The primary domain name, i.e. the certificate common
46 # The path of the file containing the private key.
48 # The path of the file containing the signed certificate.
50 # The path of the file containing the full certificate chain.
52 # The path of the file containing the intermediate certificate(s).
55 HANDLER=$1; shift; $HANDLER $@