Viewing Orchestrator Details

To view details of an orchestratorClosed Keyfactor orchestrators perform a variety of functions, including managing certificate stores and SSH key stores., double-click the orchestrator, right-click the orchestrator and choose View Details from the right-click menu, or highlight the row in the grid and click View Details at the top of the grid. The orchestrator details dialog includes this information:

The GUID of the orchestrator.

The host name of the orchestrator machine, either short or fully qualified depending upon how the machine reports itself.

The Active Directory user account the orchestrator is using to authenticate to Keyfactor Command, which may or may not be the same as the user account under which the orchestrator is running. For example, the Keyfactor Windows Orchestrator service runs as a service account on the orchestrator machine but its identity on the Keyfactor Command server will be a service account in the Keyfactor Command forest. This identity may be different from that of the service account on the orchestrator machine, which may be in a remote forest.

The platform of the orchestrator—Java for the Java Agent, .NET Core for the Keyfactor Universal Orchestrator, .NET for the Keyfactor Windows Orchestrator, Bash for the Keyfactor Bash Orchestrator, and ObjectiveC for the Mac agent, for example.

The version number that the orchestrator has reported.

Whether the orchestrator has been approved for operations with the Keyfactor Command server. Newly registered orchestrators show New in this column. Disapproved orchestrators show Disapproved.

The date and time when the orchestrator last contacted the Keyfactor Command server.

The target types that are supported by that orchestrator—e.g. AWS, F5, FTP, IIS, JKS, NS (NetScaler), PEM, SSH, SSL, Windows—as appropriate for the type of orchestrator. This includes custom AnyAgent capabilities. Keyfactor Command also has LOGS capabilities for Keyfactor Universal Orchestrators, Native Agents, and any orchestrators built on the AnyAgent platform.

The last blueprint applied to the orchestrator, if any (see Orchestrator Blueprints).

The thumbprint of the certificate previously used by the orchestrator for client certificate authentication before a certificate renewal operation took place (rotating the current thumbprint into the legacy thumbprint). The legacy thumbprint is cleared once the orchestrator successfully registers with a new thumbprint.

The thumbprint of the certificate that Keyfactor Command is expecting the orchestrator to use for client certificate authentication.

The last error code, if any, reported from the orchestrator when trying to register a session. This code is cleared on successful session registration.

The thumbprint of the certificate that the orchestrator most recently used for client certificate authentication. In most cases, this will match the Current Thumbprint.

The last error code, if any, reported from the orchestrator when trying to register a session. This code is cleared on successful session registration.

The last error code, if any, reported from the orchestrator when trying to register a session. This message is cleared on successful session registration.

Figure 276: View Details for an Orchestrator