Overview
This article explains SecureAuth's product support lifecycle phases (Standard, Limited, Extended, and Air-gapped Support) and lists the lifecycle dates for every SecureAuth Identity Platform and legacy SecureAuth IdP release.
Support Lifecycle Phases
The lifecycle for a SecureAuth Identity Platform (previously named SecureAuth IdP) release consists of a Standard lifecycle of two years, followed by one year of Limited Support, then an optional two or more years of Extended Support (available at a fee), and no support thereafter. The table below shows what's included during each phase, provided the customer is current with maintenance or subscription:
| Standard | Limited | Extended b | None | |
| New Features a | Yes | No | No | No |
| Enhancement Requests | Yes | No | No | No |
| Issue Resolution | Yes | Yes c | Yes c | No |
| Critical Security Updates | Yes | Yes | Yes | No |
| Support | Yes | Yes | Yes | No |
| Knowledge Base Access | Yes | Yes | Yes | Yes |
| Forums | Yes | Yes | Yes | Yes |
| Access to Hot Fixes | Yes | Yes | Yes | Yes |
| Access to Documentation | Yes | Yes | Yes | Yes |
a – Available to customers current with maintenance.
b – Extended support is available at a fee.
c – Critical priorities only.
Standard Lifecycle
Provided a customer is current with maintenance or subscription, standard product support is provided for each product release for up to two years. Product support includes hot fixes and patches for software defects that materially prevent product use, and any available workarounds for other non-critical defects. During Standard support and at its discretion, SecureAuth may fix bugs in a current release and deliver a hot fix, or schedule bug fixes in a future release. Customers current with maintenance may request support for any severity level.
Limited Support
Limited product support starts immediately at the end of Standard support and continues for one year. It includes email and telephone support, problem investigation, and resolution recommendations based on existing knowledge and existing supported releases and patches. SecureAuth may provide qualified security updates at its discretion during this phase.
Extended Support
Provided a release qualifies and the customer is current with extended maintenance, Extended Support starts immediately at the end of Limited Support and continues for two or more years, at SecureAuth's discretion. It includes the same email/telephone support, problem investigation, and resolution recommendations as Limited Support, plus qualified critical-priority updates at SecureAuth's discretion.
Air-gapped Support
Provided the customer is current with maintenance or subscription, Air-gapped Support begins immediately after Limited Support concludes and continues for a minimum of three years, for SecureAuth IdP instances deployed in fully air-gapped environments. It includes the same email/telephone support, issue investigation, and resolution recommendations as Limited and Extended support, plus qualified critical updates at SecureAuth's discretion. Contact SecureAuth Support or your Customer Success Manager for full details.
Air-gapped Lifecycle – Legacy Releases (20.06 and earlier)
This phase applies only to air-gapped deployments of release 20.06 and earlier. From SA IdP release 24.04 with update 24.5.0 onward, air-gapped deployments follow the Standard, Limited, and Extended Support phases described below.
Starting with SecureAuth Identity Platform 24.04 with update 24.5.0, air-gapped deployments are supported natively and follow the same lifecycle as hybrid and cloud deployments: Standard Lifecycle, then Limited Support, then Extended Support. See Identity Platform Release Dates for those dates.
SecureAuth may also address a customer issue with significant business impact through a hot fix; each hot fix is subject to the same lifecycle as the release it applies to. SecureAuth aims to provide at least one new release per year, at its discretion.
All dates below for End of Standard Lifecycle, End of Limited Support, End of Extended Support, and End of Air-gapped Support are close approximations and subject to change.
Identity Platform Release Dates
| Release | General Availability | End of Standard Lifecycle | End of Limited Support | End of Extended Support |
| 26.0.0 | Jan 30, 2026 | Jan 30, 2028 | Jan 30, 2029 | Jan 30, 2030 |
| 24.04 | Apr 3, 2024 | Apr 3, 2026 | Apr 3, 2027 | Apr 3, 2029 |
| 23.07 | Jul 18, 2023 | Jul 18, 2025 | Jul 18, 2026 | Jul 18, 2028 |
| 22.12 | Dec 15, 2022 | Dec 15, 2024 | Dec 15, 2025 | Dec 15, 2027 |
| 22.02 | Apr 25, 2022 | Apr 25, 2024 | Apr 25, 2025 | Apr 25, 2027 |
| 21.04 | Apr 4, 2021 | Apr 4, 2023 | Apr 4, 2024 | Apr 4, 2026 |
| 20.06 | Jul 31, 2020 | Jul 31, 2022 | Jul 31, 2023 | Jul 31, 2025 |
| 19.07 | Jul 11, 2019 | Jul 11, 2021 | Jul 11, 2022 | Jul 11, 2024 |
Legacy SecureAuth IdP Release Dates
| IdP Version | General Availability | End of Standard Lifecycle | End of Limited Support | End of Extended Support |
| 9.3 | Jan 22, 2019 | Jan 22, 2021 | Dec 30, 2024 | Dec 30, 2025 |
| 9.2 | Feb 1, 2018 | Feb 1, 2021 | Feb 1, 2022 | Feb 1, 2024 |
| 9.1 | Jul 25, 2017 | Jul 24, 2020 | Jul 24, 2021 | Jul 24, 2022 |
| 9.0.2 | Dec 19, 2016 | Jun 19, 2018 | Dec 19, 2018 | N/A** |
| 9.0.1 | Aug 24, 2016 | Feb 24, 2018 | Aug 24, 2018 | N/A** |
| 9.0.0 | Apr 29, 2016 | Oct 29, 2017 | Apr 29, 2018 | N/A** |
| Earlier releases | -- | Jun 1, 2017 | Dec 1, 2017 | N/A** |
**Extended Support has expired and is not available.
Air-gapped Legacy Release Dates
| Release | General Availability | End of Standard Lifecycle | End of Limited Support | End of Air-gapped Support |
| 9.2 | Feb 1, 2018 | Feb 1, 2021 | Feb 1, 2022 | Feb 1, 2028 |
| 20.06 | Jul 31, 2020 | Jul 31, 2022 | Jul 31, 2023 | Jul 31, 2028 |
SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.
Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.
Comments
0 comments
Please sign in to leave a comment.