System Requirements

Table 1354: System Requirements provides the recommendations for minimum system specifications used by Keyfactor Command components. Keyfactor Command installations on Windows may be deployed as virtual machines and may be part of a clustering or load-balanced architecture, if desired. If the Keyfactor Command roles are co-located, the specifications may need to be scaled accordingly. All Microsoft-supported methods for making SQL Server highly available are supported. For most SQL high availability requirements, Keyfactor recommends using always on availability groups (see SQL Server).

Important:  SSHClosed The SSH (secure shell) protocol provides for secure connections between computers. It provides several options for authentication, including public key, and protects the communications with strong encryption. management in Keyfactor Command with the Keyfactor Bash OrchestratorClosed The Bash Orchestrator, one of Keyfactor's suite of orchestrators, is used to discover and manage SSH keys across an enterprise. (see SSH) is only supported when using Keyfactor Command installations on Windows and Active Directory as an identity provider. The SSH option in the Management Portal will only appear when Keyfactor Command is installed using Active Directory as an identity provider (and with a license that supports SSH).

Table 1354: System Requirements

Component

Windows Install Minimum Requirements

 Kubernetes Install Minimum Requirements

Keyfactor Command Server
Add
(Management Portal, Keyfactor API, CA Connector API, and Services roles)

  • Kubernetes 1.26+

  • Helm v3.14+

  • Ingress controller for Kubernetes

  • x64 CPU Architecture

  • CPU and RAM defaults and minimums as defined in the helm chart and custom values file

  • Keyfactor Command license key for the current release

Note:  Installations under Kubernetes have the following limitations:

  • Direct communication with Microsoft CAs is not supported. A Keyfactor CA Connector Client is required to facilitate communication.

  • SSH management with Keyfactor Command is not supported.

  • Native client certificate authentication for the Keyfactor Universal Orchestrator is not supported. Client certificate authentication via a proxy can be supported.

  • Using Active Directory as an identity provider for Keyfactor Command is not supported.

  • Event handlers in the legacy alerting system are not supported; use workflows instead.

  • Custom PowerShell scripts in workflows and legacy alert handlers are not supported; workflows of type Set Variable Data are supported.

Microsoft SQL Database

Ability to connect to a Microsoft SQL Server 2017, 2019, 2022, or 2025 all with TLS encryption enabled and compatibility level 130 or higher. SQL should be installed with a case-insensitive collation setting.

16 GB RAM, 4 CPUs, 500 GB disk

Note:  These are minimum requirements. Actual requirements can vary significantly depending on your specific implementation.
Tip:  For information on upgrading the database compatibility level, see:
https://learn.microsoft.com/en-us/sql/t-sql/statements/alter-database-transact-sql-compatibility-level
Browser to Access the Management Portal

Keyfactor Command supports the current stable release and the two previous major releases of the following desktop browsers:

  • Google Chrome

  • Mozilla Firefox

  • Microsoft Edge

Older browser versions might not support all functionality used by the Keyfactor Command Management Portal. For the best experience, use the latest stable browser version.
EJBCA CA (Optional)

  • Refer to the Current Compatibility Matrix for the list of EJBCA versions supported by Keyfactor Command.

  • The EJBCA REST API must be enabled to interoperate with Keyfactor Command (see System Configuration -> Protocol Configuration in the EJBCA administration portal).

  • Post-quantum computing will not work prior to version 9.1.