Initial Configuration

Once the installation and configuration is complete, only a few configuration tasks remain before Keyfactor Command will be up and running at a basic level. This section details the basic post-install configuration steps that need to be completed to get Keyfactor Command up and running. See the Keyfactor Command Reference Guide for more advanced configuration guidance. See the separate installation guides for client components such as the Keyfactor Universal OrchestratorClosed The Keyfactor Universal Orchestrator, one of Keyfactor's suite of orchestrators, is used to interact with servers and devices for certificate management, run SSL discovery and management tasks, and manage synchronization of certificate authorities in remote forests. With the addition of custom extensions, it can provide certificate management capabilities on a variety of platforms and devices (e.g. Amazon Web Services (AWS) resources, Citrix\NetScaler devices, F5 devices, IIS stores, JKS keystores, PEM stores, and PKCS#12 stores) and execute tasks outside the standard list of certificate management functions. It runs on either Windows or Linux servers or Linux containers. and Keyfactor CAClosed A certificate authority (CA) is an entity that issues digital certificates. Within Keyfactor Command, a CA may be a Microsoft CA or a Keyfactor gateway to a cloud-based or remote CA. Gateways.

After you have completed all the steps in this guide, the certificate search and report functions in the Keyfactor Command Management Portal should be functioning. Further configuration, as described in the Keyfactor Command Reference Guide, is required to make these features function: