If your organization is running an older version of a Keyfactor product, consider reviewing the latest available releases and upgrade guidance. Keeping your Keyfactor products on the current support version will help ensure that you have access to the latest security advisories, performance improvements, and platform enhancements. Being on the most current version may also help reduce encountering bugs or other issues addressed in newer releases. This will help enable your organization to take advantage of the latest capabilities offered in your product.
Why upgrade?
- Improve stability and reliability. Newer versions include improvements that are designed to improve overall platform stability and resiliency. Staying on the most current version can help ensure your environment benefits from ongoing product improvements and helps you receive support on the latest platform capabilities.
- Access new automation capabilities. As certificate management requirements continue to grow, automation becomes increasingly important. Recent messaging around Keyfactor Command upgrades highlights investments in automation and features designed to help organizations operate more efficiently and scale certificate management activities more effectively.
- Prepare for future cryptographic requirements. Newer platform releases may include enhancements that help organizations prepare for evolving security needs, including crypto agility initiatives and future cryptographic requirements. Maintaining a current version can help ensure your organization is better positioned to adopt new capabilities as they become available.
- Maintain a supported environment. Running a supported version helps ensure access to the latest fixes, updates, and product improvements. Organizations that stay current with upgrades can more easily take advantage of new functionality and avoid challenges commonly associated with older software versions.
Common issues that may be resolved through upgrades
While every environment is different, support investigations often identify situations where upgrading to a newer version is recommended because fixes and improvements have already been incorporated into later releases.
For example, some customers experience portal performance issues, including slow page loading, delayed responsiveness, or difficulties accessing the Command portal. In certain cases, these issues can be associated with background processing activities, API batch jobs, configuration problems, or older platform versions. Upgrading to a newer supported release is frequently recommended as part of the resolution process.
Similarly, customers running older versions may encounter issues that have already been addressed through product fixes, performance improvements, or enhancements delivered in subsequent releases. Staying current helps reduce the risk of encountering known issues that have been resolved in newer versions.
Before you upgrade
Before planning an upgrade, consider the following best practices:
- Review the release notes for your target version.
- Verify any prerequisites and environmental requirements.
- Review compatibility considerations specific to your deployment.
- Plan and test the upgrade according to your organization's change management process.
- Consult with Keyfactor resources if you have questions about upgrade planning or version selection.
Comments
Please sign in to leave a comment.