ForgeRock End of Service Life (EOSL) Policy and EOSL Dates | AM, DS and IDM

Last updated Feb 15, 2023

The purpose of this article is to provide EOSL policy details and definitions for ForgeRock Access Management (AM), Directory Services (DS) and Identity Management (IDM). EOSL dates are also provided for the currently supported versions so you can check that the version you are on is still supported and maintained.

31 readers recommend this article

Overview

This article contains details on the EOSL policy and EOSL dates for ForgeRock Access Management (AM), Directory Services (DS) and Identity Management (IDM). This policy applies to users of ForgeRock software with a current, valid subscription. For EOSL policy and dates for ForgeRock Identity Gateway (IG) and Agents, please refer to: ForgeRock Product Lifecycle and Support Policy, and EOSL Dates | IG and Agents.

You can jump straight to the section you're interested in using these quick links:

EOSL Policy Details
Release and EOSL Dates for the following ForgeRock products:
Definitions

Note

This article includes EOSL dates for all supported product versions. See End of Life dates for legacy product versions if you want to know EOSL dates for legacy (unsupported) product versions.

EOSL Policy Details

ForgeRock supports and maintains two Current Versions and one Previous Version per the following definitions:

Current Versions are the two most recent releases (Major or Minor) of the current Major version.
Previous Version is the final Minor release of the previous Major version.

All other releases in the current Major version are supported, but not maintained. This means you can raise tickets, and receive code fixes for Security and Critical Issues if appropriate, but won't receive Maintenance releases.

Support schedule for Major versions

The two most recent releases (Major or Minor) of the current Major version are maintained.
The other releases of the current Major version are supported.
The current Major version will remain supported/maintained until it is superseded by a newer Major version; at this time, the final Minor release of the superseded Major version will become the Previous Version.
- The Previous Version will continue to be supported and maintained for two (2) years after being superseded by a new Major version. After two years, the Previous Version will be EOSL.
- No further Maintenance versions will be released on top of the Previous Version once it is EOSL.
ForgeRock will continue to release Minor or Maintenance versions on top of the two most recent releases of the current Major version.
To remain supported, customers must be running one of the supported versions as outlined above.

Example

AM 7 is the current Major release and AM 7.2 is the latest Minor release, which means:

AM 7 was released on August 10, 2020. It does not currently have an EOSL Date; this will be set when the next Major version is released.
All AM 7.x releases are supported.
AM 7.1 and 7.2 are Current Versions and therefore maintained.
- When AM 7.3 is released, AM 7.1 will no longer be maintained; AM 7.3 and AM 7.2 will become the Current Versions.
AM 6.5 is the Previous Version, and therefore is supported until August 10, 2022.
- The EOSL Date for AM 6.5 is August 10, 2022; two years after the release of the current Major version.
- Extended Limited Support for AM 6.5 (if purchased) will end August 10, 2024.

Practical considerations

All customers are strongly encouraged to use the latest versions of the ForgeRock products.
As subscriptions are not tied to a specific version, there is no additional software licensing cost for upgrading!

EOSL policy for embedded components

ForgeRock software such as Access Management can contain embedded versions of other ForgeRock software products such as Directory Services. When a ForgeRock software product has been embedded and distributed as part of another ForgeRock software release, the EOSL timeline that applies to the top-level software release will also apply to all and any embedded versions of ForgeRock software. This statement only applies to embedded software and does not affect the EOSL timeline of the products when they are distributed as standalone releases.

Access Management Release and EOSL Dates

Major Version	Maintained Versions	Latest Release	Original Release Date	EOSL Date	Extended Limited Support End Date	Latest Release Notes
7	7.1 and 7.2	7.1.3 (October 13, 2022) 7.2 (June 30, 2022)	August 10, 2020	TBD	TBD	7.1 Release Notes 7.2 Release Notes
6	--	6.5.5 (August 2, 2022)	May 9, 2018	August 10, 2022	August 10, 2024	Release Notes

Directory Services Release and EOSL Dates

Major Version	Maintained Versions	Latest Release	Original Release Date	EOSL Date	Extended Limited Support End Date	Latest Release Notes
7	7.1 and 7.2	7.1.4 (October 11, 2022) 7.2.1 (January 26, 2023)	August 10, 2020	TBD	TBD	7.1 Release Notes 7.2 Release Notes
6	--	6.5.6 (August 3, 2022)	May 9, 2018	August 10, 2022	August 10, 2024	Release Notes

Identity Management Release and EOSL Dates

Major Version	Maintained Versions	Latest Release	Original Release Date	EOSL Date	Extended Limited Support End Date	Latest Release Notes
7	7.1 and 7.2	7.1.4 (January 6, 2023) 7.2.1 (September 28, 2022)	August 10, 2020	TBD	TBD	7.1 Release Notes 7.2 Release Notes
6	--	6.5.2 (August 17, 2022)	May 9, 2018	August 10, 2022	August 10, 2024	Release Notes

Definitions

Term	Definition
Major release	A major release may introduce major new functionality, remove redundant or previously deprecated functionality and/or deprecate additional functionality that will be removed in the future. It will also consolidate bug fixes from previous releases. Additionally, it may contain architectural changes that require a review of deployment topology.
Minor release	A minor release may introduce new modified features and enhancements alongside bug fixes. It may also deprecate functionality that will be removed in the next major release. Minor releases have no impact on EOSL.
Maintenance release	A maintenance release only includes bug fixes. These are full releases that require no configuration changes; they are designed as drop-in updates on top of the two most recent Minor releases (or Major release if it's a .0). Security fixes included in maintenance releases may introduce breaking changes; these will be clearly noted in the accompanying security advisory and release notes if this happens.
Version numbering	Version numbering uses the following format: `[Major].[Minor].[Maintenance]` For example: AM 7.1.2, where 7 is the Major version, 7.1 is the Minor version and 7.1.2 is the Maintenance version.
Date of Release	The date of release is the date when the major release of a ForgeRock product is made publicly available.
Current Versions	The last two releases (Major or Minor) of the current Major version are Current Versions.
Previous Version	The final Minor release of the previous Major version is the Previous Version.
Maintained Versions	ForgeRock supports and maintains the two Current Versions and the Previous Version per the above definitions. When a new Major version is released, it becomes the Current Version and the last Minor release of the superseded Major version becomes the Previous Version. The Previous Version is maintained for two (2) years from the date it becomes the previous version (two years from the release date of the new Major version).
Supported Versions	ForgeRock supports all other releases in the current Major version. Supported versions allow customers to raise tickets, and receive code fixes for Security and Critical Issues if appropriate, but they won't receive Maintenance releases.