Skip to main content

System- und Netzwerkanforderungen

Vergewissern Sie sich, dass Ihr System und Ihr Netzwerk die Mindestanforderungen erfüllen, bevor Sie den DigiCert ACME-Automatisierungs-Agent installieren.

Der Agent muss auf demselben System installiert sein wie die automatisierten TLS/SSL-Zertifikate.

Systemanforderungen

Die ACME-Agent-Software läuft auf Linux- und Windows-Systemen mit den folgenden Anforderungen:

Red Hat Enterprise Linux 7.x, 8.x, und Ubuntu 20.04 oder höher

  • Root-Rechte

  • 64-Bit-Version und US-Gebietsschema erforderlich

  • 2 GB RAM (4 GB RAM empfohlen)

  • 2 GB freier Speicherplatz (Minimum)

  • CLI utilities awk, grep, and sed must be installed

Microsoft Windows 10, Server 2012 R2, 2016 und 2022

  • Als Administrator ausgeführt

  • 64-Bit-Version

  • Microsoft .NET Framework 3.5

  • 2 GB RAM (4 GB RAM empfohlen)

  • 2 GB freier Speicherplatz (Minimum)

Netzwerkanforderungen

Der lokale ACME-Agent muss Folgendes können:

Der lokale ACME-Agent muss Folgendes können:

  • Eine ausgehende Verbindung zu HTTPS (Port 443) herstellen.

  • Eine ausgehende Verbindung mit der öffentlichen IP-Adresse 216.168.244.42 herstellen (für acme.digicert.com und daas.digicert.com).

Hinweis

If the agent will use a local DigiCert​​®​​ sensor as proxy, make sure port 48999 is open on the sensor and can be accessed by the agent.

Additional requirements for private on-premises DigiCert ONE users

Users with a private on-premises DigiCert ONE deployment need to install the private DigiCert ONE certificate into the local truststores of any systems that will run agent-based automations.

Below are basic instructions for how to meet these private trust requirements. For more details about how to install and manage the CA certificates in a local truststore, consult the documentation for your operating system version.

Note: These requirements only apply to private on-premises DigiCert ONE users. They do not apply to users of the cloud-hosted DigiCert ONE service.

Windows truststore requirements

To automate certificates on a Windows system via a private on-premises DigiCert ONE server, install the private DigiCert ONE certificate into the Windows truststore as described below.

Active Directory deployment

Refer to this page on the Microsoft website for instructions about how to distribute the DigiCert ONE certificate via Active Directory.

Standalone deployment

To install the DigiCert ONE certificate on a standalone Windows system:

  1. Copy the private DigiCert ONE certificate to the Windows system as a PEM-encoded file (.crt file extension). Note the certificate file location.

  2. Launch the Windows certlm.msc tool as an administrator to manage the certificates on the local machine.

  3. Use the Import action to browse and import the DigiCert ONE certificate file into the list of Trusted Root Certification Authorities > Certificates.

Linux truststore requirements

To automate certificates on a Linux system via a private on-premises DigiCert ONE server, install the private DigiCert ONE certificate into the Linux truststore as follows:

  1. Copy the private DigiCert ONE certificate to the Linux system as a PEM-encoded file (.crt file extension). Note the certificate file location.

  2. Make sure the Linux ca-certificates package is installed. Install it if needed, for example, by running apt-get install ca-certificates or yum install ca-certificates as root.

  3. Copy the .crt file for DigiCert ONE into the CA certificates directory. The location of this directory depends on your Linux distribution and version. See the table below for some possible locations.

  4. Run the command as root to update the local truststore based on the current CA certificate files. The name of this command depends on your Linux distribution and version. See the table below for some possibilities.

Linux distribution

CA certificates directory

Command to update truststore

CentOS/RHEL

/etc/pki/ca-trust/source/anchors/

update-ca-trust

SUSE

/usr/share/pki/trust/anchors/

update-ca-certificates

Ubuntu

/usr/local/share/ca-certificates/

update-ca-certificates