Distributed Engine and Protocol Handler Version Numbers
Secret Server
See full Secret Server Cloud Change Log for more details.
Table: Secret Server Cloud Distributed Engine Versions
| Secret Server Version | DE Version | PH Version | Date Published | Required Upgrade | Notes |
|---|---|---|---|---|---|
| 2025-01-23 | 8.4.45 | 6.0.3.33 | 2025-01-23 | PHWith this version, protocol handler improvements include resolving an issue where all metadata was displayed when more than 10 fields were added to a secret, ensuring proper metadata management. Updating the heartbeat on a secret now generates an audit entry, providing clear documentation of whether the heartbeat was enabled or disabled. Large SSH keys can now be imported on Linux servers, enhancing compatibility and functionality for users managing SSH keys. When a secret is erased, the TOTP key and backup codes are also erased, ensuring complete removal of sensitive information. A cooldown period of 1 hour has been introduced for the Quantum Lock password, improving user experience by reducing the frequency of password entry. An issue with the Secret Dependency Failure default report not running has been fixed, ensuring accurate reporting and monitoring. | |
| 2024-08-03 | 8.4.33.0 | 6.0.3.28 | 2024-08-03 | PH: With the previous version, protocol handler received changes to core internal functionality that prevents automatically updating to version 6.0.3.27 from a prior version. In environments with protocol handler automatic update enabled, the protocol handler will automatically update to version 6.0.3.26. To use the latest functionality and fixes of protocol handler, you must manually redeploy or install version 6.0.3.27 to end-user machines. Following that update, the automatic update will continue to work as before and upgrade to 6.0.3.28. | |
| 2024-04-20 | 8.4.24.0 | 6.0.3.27 | 2024-04-20 | PH: With this version, protocol handler received changes to core internal functionality that prevents automatically updating to version 6.0.3.27 from a prior version. In environments with protocol handler automatic update enabled, the protocol handler will automatically update to version 6.0.3.26. To use the latest functionality and fixes of protocol handler, you must manually redeploy or install version 6.0.3.27 to end-user machines. Following that update, the automatic update will continue to work as before. | |
| 2024-02-10 | 8.4.21.0 | 6.0.3.27 | 2024-02-10 | PH: Yes | PH: With this version, protocol handler received changes to core internal functionality that prevents automatically updating to version 6.0.3.27 from a prior version. In environments with protocol handler automatic update enabled, the protocol handler will automatically update to version 6.0.3.26. To use the latest functionality and fixes of protocol handler, you must manually redeploy or install version 6.0.3.27 to end-user machines. Following that update, the automatic update will continue to work as before. |
| 2023-09-23 | 8.4.16.0 | 6.0.3.26 | 2023-09-23 | PH: The legacy automatic update works up to this version. The next version will require a manual update. After that, the new automatic update will work. See the notes above. |
Secret Server On-Premises
Table: Secret Server On-Premises Distributed Engine Versions
| Secret Server Version | DE Version | PH Version | Date Published | Required DE/PH Upgrade | Notes |
|---|---|---|---|---|---|
| 11.7.000016 | 8.4.32.0 | 6.0.3.28 |
|
DE: Yes | DE: Replacement for 11.7.000015. We pulled down version 11.7.15 (on-premises) to resolve a problem with older versions of RabbitMQ (before 3.10) impacting DE version 8.4.31, which is shipped with SS 11.7.15. This issue does not impact Cloud. |
| 11.7.000015 | 8.4.31.0 | 6.0.3.28 | 2024-05-22 | DE: Pulled down to resolve a problem with older versions of RabbitMQ (before 3.10) impacting DE version 8.4.31, which is shipped with SS 11.7.15. This issue does not impact Cloud. | |
| 11.7.000002 | 8.4.24.0 | 6.0.3.27 |
|
||
| 11.7.000001 | 8.4.24.0 | 6.0.3.27 |
|
PH: Yes | PH: With this version, protocol handler received changes to core internal functionality that prevents automatically updating to version 6.0.3.27 from a prior version. In environments with protocol handler automatic update enabled, the protocol handler will automatically update to version 6.0.3.26. To use the latest functionality and fixes of protocol handler, you must manually redeploy or install version 6.0.3.27 to end-user machines. Following that update, the automatic update will continue to work as before. |
