====== Installation automatique de certificat Harica sur Windows avec WIN-ACME ======

Télécharger la dernière version sur https://www.win-acme.com

Dézipper le fichier sur le disque C:\DSI-ISR

Modifier la valeur **DefaultBaseUri** dans le fichier settings.json
<code>
"Acme": {
    "DefaultBaseUri": "https://acme-v02.harica.gr/acme/f570e4e0-82e5-43a9-b6f0-bc23672fbe28/directory",
    ...
</code>

Suivre les instructiona à l'écran (exemple salto.local.enit.fr)
<code>

 A simple Windows ACMEv2 client (WACS)
 Software version 2.2.9.1701 (release, trimmed, standalone, 64-bit)
 Connecting to https://acme-v02.harica.gr/acme/f570e4e0-82e5-43a9-b6f0-bc23672fbe28/directory...
 Connection OK!
 Scheduled task not configured yet
 Please report issues at https://github.com/win-acme/win-acme

 N: Create certificate (default settings)
 M: Create certificate (full options)
 R: Run renewals (0 currently due)
 A: Manage renewals (0 total)
 O: More options...
 Q: Quit

 Please choose from the menu: M

 Running in mode: Interactive, Advanced
 Source plugin IIS not available: No supported version of IIS detected.

 Please specify how the list of domain names that will be included in the
 certificate should be determined. If you choose for one of the "all bindings"
 options, the list will automatically be updated for future renewals to
 reflect the bindings at that time.

 1: Read bindings from IIS
 2: Manual input
 3: CSR created by another program
 C: Abort

 How shall we determine the domain(s) to include in the certificate?: 2

Description:         A host name to get a certificate for. This may be a
                     comma-separated list.

 Host: salto.local.enit.fr,www.salto.local.enit.fr,salto.loacl.uttop.fr,www.salto.local.uttop.fr

 Source generated using plugin Manual: salto.local.enit.fr and 3 alternatives

 Friendly name '[Manual] salto.local.enit.fr'. <Enter> to accept or type desired name: <Enter>

 By default your source identifiers are covered by a single certificate. But
 if you want to avoid the 100 domain limit, want to prevent information
 disclosure via the SAN list, and/or reduce the operational impact of a single
 validation failure, you may choose to convert one source into multiple
 certificates, using different strategies.

 1: Separate certificate for each domain (e.g. *.example.com)
 2: Separate certificate for each host (e.g. sub.example.com)
 3: Separate certificate for each IIS site
 4: Single certificate
 C: Abort

 Would you like to split this source into multiple certificates?: 4

 The ACME server will need to verify that you are the owner of the domain
 names that you are requesting the certificate for. This happens both during
 initial setup *and* for every future renewal. There are two main methods of
 doing so: answering specific http requests (http-01) or create specific dns
 records (dns-01). For wildcard identifiers the latter is the only option.
 Various additional plugins are available from
 https://github.com/win-acme/win-acme/.

 1: [http] Save verification files on (network) path
 2: [http] Serve verification files from memory
 3: [http] Upload verification files via FTP(S)
 4: [http] Upload verification files via SSH-FTP
 5: [http] Upload verification files via WebDav
 6: [dns] Create verification records manually (auto-renew not possible)
 7: [dns] Create verification records with acme-dns (https://github.com/joohoi/acme-dns)
 8: [dns] Create verification records with your own script
 9: [tls-alpn] Answer TLS verification request from win-acme
 C: Abort

 How would you like prove ownership for the domain(s)?: 2

 After ownership of the domain(s) has been proven, we will create a
 Certificate Signing Request (CSR) to obtain the actual certificate. The CSR
 determines properties of the certificate like which (type of) key to use. If
 you are not sure what to pick here, RSA is the safe default.

 1: Elliptic Curve key
 2: RSA key
 C: Abort

 What kind of private key should be used for the certificate?: 2

 When we have the certificate, you can store in one or more ways to make it
 accessible to your applications. The Windows Certificate Store is the default
 location for IIS (unless you are managing a cluster of them).

 1: IIS Central Certificate Store (.pfx per host)
 2: PEM encoded files (Apache, nginx, etc.)
 3: PFX archive
 4: Windows Certificate Store (Local Computer)
 5: No (additional) store steps

 How would you like to store the certificate?: 4

 1: [My] - General computer store (for Exchange/RDS)
 2: [Default] - Use global default, currently My

 Choose store to use, or type the name of another unlisted store: 2

 1: IIS Central Certificate Store (.pfx per host)
 2: PEM encoded files (Apache, nginx, etc.)
 3: PFX archive
 4: Windows Certificate Store (Local Computer)
 5: No (additional) store steps

 Would you like to store it in another way too?: 5

 Installation plugin IIS not available: No supported version of IIS detected.

 With the certificate saved to the store(s) of your choice, you may choose one
 or more steps to update your applications, e.g. to configure the new
 thumbprint, or to update bindings.

 1: Create or update bindings in IIS
 2: Start external script or program
 3: No (additional) installation steps

 Which installation step should run first?: 3

Terms of service:    C:\ProgramData\win-acme\acme-v02.harica.gracmef570e4e0-82e5-43a9-b6f0-bc23672fbe28directory\SA-ToU.pdf

 Open in default application? (y/n*) - no

 Do you agree with the terms? (y*/n) - yes

 This ACME endpoint requires an external account. You will need to provide a
 key identifier and a key to proceed. Please refer to the providers
 instructions on how to obtain these.

 Key identifier: jW7GENsd4f0DsytW7AkW

 Key (base64url encoded): *******************************************
 Plugin Manual generated source salto.local.enit.fr with 4 identifiers
 Plugin Single created 1 order
 Downloading certificate [Manual] salto.local.enit.fr
 Store with CertificateStore...
 Installing certificate in the certificate store
 Adding certificate [Manual] salto.local.enit.fr @ 2026/7/27 in store My
 Adding certificate CN=GEANT TLS RSA 1, O=Hellenic Academic and Research Institutions CA, C=GR in store CA
 Adding certificate CN=HARICA TLS RSA Root CA 2021, O=Hellenic Academic and Research Institutions CA, C=GR in store CA
 Adding Task Scheduler entry with the following settings
 - Name win-acme renew (acme-v02.harica.gracmef570e4e0-82e5-43a9-b6f0-bc23672fbe28directory)
 - Path C:\DSI-ISR\win-acme
 - Command wacs.exe --renew --baseuri "https://acme-v02.harica.gr/acme/f570e4e0-82e5-43a9-b6f0-bc23672fbe28/directory"
 - Start at 09:00:00
 - Random delay 04:00:00
 - Time limit 02:00:00

 Do you want to specify the user the task will run as? (y/n*)
</code>

Une tâche planifiée est créé automatiquement par le programme et vérifie chaque jour si les certificats doivent être renouvelés

{{:win-acme.png |}}