General
ForgeRock Identity Platform
Does not apply to Identity Cloud

Maintenance and Patch availability policy

Last updated Mar 9, 2021

The purpose of this article is to set out the details of the ForgeRock policy on making patches available to customers and the structure and contents of maintenance releases.


5 readers recommend this article

Definitions

  • Critical Issue: A critical issue is one where the impact on a customer deployment could potentially be severe.
  • Non-Critical Issue: A non-critical issue is one where the severity of the impact of the issue would be such that it could delay or inconvenience customers without putting their systems at risk of disruption.
  • Security Issue: An issue that applies to ForgeRock's Security Policy. Security issues have four levels; critical, high, medium and low and said levels are defined in the Security Policy.
  • Initial Major Release: An initial major release is the Enterprise release that marks the start of the EOSL timeline for a major release. Refer to the ForgeRock End of Service Life (EOSL) policy for further details.
  • Minor Release: A limited feature release that include maintenance fixes. Refer to the ForgeRock End of Service Life (EOSL) policy for further details.
  • Maintenance Release: A maintenance release is a collection of fixes and minor RFEs that have been grouped together and released to ForgeRock customers as part of ForgeRock's commitment to support our customers. Maintenance releases are released under the terms of the ForgeRock End of Service Life (EOSL) policy.
  • Patch Release: A patch release is a small collection of fixes for customer reported issues. A patch release is non-breaking in terms of API compatibility and does not contain any RFEs. Refer to the ForgeRock End of Service Life (EOSL) policy for further details.
  • End of Service Life (ForgeRock End of Service Life (EOSL) policy): The ForgeRock End of Service Life Policy describes the different types of releases and the duration of support available.
  • Maintenance release regression: A maintenance release regression represents a new issue that was introduced by a fix included in a maintenance release.
  • Patch: A patch represents a fix to a specific issue or set of issues that is provided to a ForgeRock customer separately from a maintenance release or a patch release.
  • Back-port: A back-port is where an issue that has been fixed in a newer version of the product is made available in an older version of the product.
  • Request for Enhancement (RFE): An RFE represents a request from a customer to enhance an existing feature or function of the product, or potentially a whole new feature or function.

Maintenance Release Contents

ForgeRock's maintenance release policy is aligned to the ForgeRock End of Service Life (EOSL) policy and provides maintenance releases for three years after the initial major release. This section describes ForgeRock's policy on providing maintenance releases for each of those three years. ForgeRock reserves the right to amend this policy at any time and without notice. The contents of maintenance releases are decided entirely at ForgeRock's discretion.

  First Year Second Year Third Year
Targeted Content 
  • Fixes for critical and security issues
  • Maintenance release regressions
  • Customer reported issues
  • Fixes for non-critical issues back-ported based on their expected customer impact
  • Fixes for critical and security issues
  • Maintenance release regressions
  • Fixes for customer reported issues on this version for which a patch has been issued
  • Fixes for critical and security issues
  • Maintenance release regressions
  • Fixes for customer reported issues on this version for which a patch has been issued
Optional Content  Small RFEs / customer requests.  Customer reported issues from other versions that should be back-ported due to likely wider customer impact N/A

In all the above cases, ForgeRock reserves the right of refusal over back-ports on a given version if said bugs are caused by architectural issues that may or may not be resolved in later versions of the product. The only RFEs included within a maintenance release are small RFEs that do not change or impact existing functionality.

Patching Policy

The patching policy depends on the product as follows:

  • Access Management: patch releases
  • Agents: patch releases
  • Directory Services: individual patches
  • Identity Management: patch releases
  • Identity Gateway: individual patches
Note

Where possible, customers should upgrade to the latest patch release.

ForgeRock's policy on delivering patch releases/patches for a specific version of the product depends on the nature of the issue, its criticality and the age of the release; this is described in the table below:

  First Year Second Year Third Year
Critical and Security Issues Patch Releases/Patches will be provided for all affected maintenance releases and the current major/minor releases. Patch Releases/Patches will be provided for the latest maintenance release and the previous maintenance release (including the major/minor release if applicable). Patch Releases/Patches will be provided for the latest maintenance release.
Non-Critical Issues Patch Releases/Patches will be provided for all affected maintenance releases and the current major/minor releases. Patch Releases/Patches will be provided for the latest maintenance release and, if less than 6 months since the latest maintenance release, for the previous version.  Patch Releases/Patches will be provided purely at ForgeRock’s discretion.

As described in the ForgeRock End of Service Life (EOSL) policy, in the fourth and final year of service life, patch releases/patches will only be made available for critical issues and security issues at the critical or high severity level, and will only be applied to the latest maintenance release.

Individual patches

Patches are fixes that may be supplied to individual customers to address specific issues. If these fixes are provided in the latest patch or maintenance release, we will advise customers to move to this release in the first instance, only providing individual patch builds in exceptional circumstances. ForgeRock aims to make these fixes available to other customers by including them in the next patch or maintenance release. Fixes for critical issues, where feasible, will be provided as long as the corresponding version hasn’t reached its final EOSL date. If this is not feasible, ForgeRock will provide a solution for the latest maintenance version of any affected releases that have not yet reached EOSL. Patches for non-critical issues will be provided at ForgeRock’s discretion. 

See Also

ForgeRock End of Service Life (EOSL) policy

Checking your product versions are supported

ForgeRock Products Support and Patch Policies


Copyright and Trademarks Copyright © 2021 ForgeRock, all rights reserved.