Major Release 8.0 Notes
Major Release 8.0 Notes
October 2020
New Features

Our new module, SSH 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. Key Manager, gives security and network teams a simple, centralized solution to simplify SSH key management and mitigate the risk of emerging SSH-based attacks.
The SSH Key Manager allows you to:
-
Discover: Inventory SSH authorized_keys across your servers and cloud infrastructure
-
Analyze: Review your key inventory to detect and remediate things like unauthorized root access, stale keys, and keys that belong to users that should no longer have access
-
Rotate: Configure automated key rotation alerts and enable self-service key generation and rotation by SSH users
-
Automate: Keep DevOps and admin teams moving with automated key deployment, which can be baked into the server provisioning process in highly automated cloud environments
-
Report: Generate reports to keep an eye on user and service account keys in your environment, including their lifecycle, access, and trust relationships




-
Links to the specific areas of the Keyfactor Command documentation are now available in the application.
-
Adding a certificate to a certificate store has been updated from the previous tree view control to a searchable grid to make management of certificate stores at scale more efficient.
-
Grids have changed to allow selecting via checkboxes and to include tabs to make the less frequently used functions grouped in a less front and center way.
-
Some areas of the application now have expandable/collapsible functionality to hide information when it isn’t needed to provide a cleaner interface.

You can now enter explicit credentials when contacting the CA 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.. The requester will be provided in the request in order to track who is acting on the CA. Additionally, permissions for who can enroll for a certificate can be defined on a Keyfactor Command Security Role level.
Updates and Improvements
-
Installation
Default installation path changes from "Certified Security Solutions" to "Keyfactor".
-
Installation
Installation now requires Remote Server Administration Tools Active Directory PowerShell Module.
-
Administration
Application Settings are now accessible via the gear icon.
-
Certificates
Certificate Collections are now under the Certificates menu item.
-
Certificate Revocation—Hold
Certificates that have been revoked with a reason of "Certificate Hold" can now have the hold removed.
Deprecation/Required Upgrades
-
Windows Server 2012 R2
Support for Windows Server 2012 R2 has been deprecated in Keyfactor Command 8, since it has also been deprecated by Microsoft, and is no longer functioning well with newer backend technologies that our software uses. Customers should upgrade to Windows Server 2019.
-
User Enrollment Portal
In Keyfactor Command 8, the support for the User Enrollment
Certificate enrollment refers to the process by which a user requests a digital certificate. The user must submit the request to a certificate authority (CA). Portal (which allows users to go to a browser page to enroll for a certificate—this is NOT the enrollment section of the Keyfactor Command Management Portal)—are deprecated.
-
iOS enrollment
-
Android enrollment
-
ActiveX PFX
A PFX file (personal information exchange format), also known as a PKCS#12 archive, is a single, password-protected certificate archive that contains both the public and matching private key and, optionally, the certificate chain. It is a common format for Windows servers. enrollment (based on whenever Microsoft phases out Internet Explorer as, at that point, ActiveX will not be available)
-
User PFX enrollment (user build-from-AD certs, NOT the web server PFX in the main Management Portal)
It is recommended not to do new deployments of these features and to plan for migration away or an in-house support option.
-
-
Expiration Renewals
Existing expiration renewals will need to have the URLs updated to point to the KeyfactorAPI instead of the CMSAPI.
-
Active Directory
In future releases the ability to use the Active Directory password on PFX enrollment will be deprecated as we upgrade to allow authentication methods other than Active Directory.
Known Issues/Limitations

-
Daylight Savings Time (DST) is now shown as the time zone locale for the clients using Keyfactor Command, rather than as the UTC offset, which is what Microsoft CA uses. This causes issues during DST in time zones that do not have DST to appear off by an hour.
-
Microsoft IIS settings to change authentication to support the "Use Active Directory Password" application setting for the Keyfactor Command portal must be made manually.
-
When using Basic Authentication, the authentication in Microsoft IIS may need to be configured manually for the KeyfactorAnalysis portal.
-
Authentication between the KeyfactorPortal, KeyfactorAPI, and KeyfactorAnalysis sites needs to be configured with the same authentication type, SSL
TLS (Transport Layer Security) and its predecessor SSL (Secure Sockets Layer) are protocols for establishing authenticated and encrypted links between networked computers., and host name
The unique identifier that serves as name of a computer. It is sometimes presented as a fully qualified domain name (e.g. servername.keyexample.com) and sometimes just as a short name (e.g. servername)..

-
Editing certificate details on a collection
The certificate search function allows you to query the Keyfactor Command database for certificates from any available source based on any criteria of the certificates and save the results as a collection that will be availble in other places in the Management Portal (e.g. expiration alerts and certain reports). for a CA while an initial sync is running on the CA will cause inaccurate numbers to display in the Edit All window.
-
If a CA is not scheduled to sync under "PKI
A public key infrastructure (PKI) is a set of roles, policies, and procedures needed to create, manage, distribute, use, store and revoke digital certificates and manage public-key encryption. Management" it will not appear in lists to select for things like inclusion in "Dashboards and Reports".
-
Syncing an Issuing CA before syncing its parents in the chain causes Keyfactor Command to show the wrong requester for the chain certificates.
-
Keyfactor Command cannot support a CA in the local forest
An Active Directory forest (AD forest) is the top most logical container in an Active Directory configuration that contains domains, and objects such as users and computers. with the same NetBIOS name as a CA in a trusted forest.
-
In some upgrade cases, the Certificate Search page only partially loads or enrollment returns a System.Exception error. Opening the Developer Tools with F12 key and performing an Empty Cache and Hard Reload will resolve this problem.

-
Running large SSL scans can impact Keyfactor Command application performance if the Windows Agent/Orchestrator performing the scan is installed on the same server as the Keyfactor Command portal.
-
If you receive an error when opening the portal that "the underlying connection was closed" please be sure you have all of the latest Windows Updates installed.

-
In Windows, drive mapping is done on a per-user basis. If you would like scheduled reports to be saved to a mapped drive, the timer service account needs to have that mapping created for them beforehand.
-
Exporting a report to Microsoft Excel can fail with a 401 error in Microsoft Edge. Chrome or Firefox can successfully export to Excel. This problem is being worked on by the reporting engine vendor (Logi Analytics).
-
Users configured for Logi Analytics reporting cannot have double quotes in the password field.

-
Occasionally, the "Please Wait" message will hang. Control + F5 will fix this.