Release and support
Toggle navigation
About
Release and support
Release notes
Changelog
Required upgrade actions
Deprecation announcement
Incubating features
Installation and upgrade
Operation
Initial configuration
Configuration management
Authentication
Self-services
Target applications
OAuth and OIDC
SAML
API access control
Flows (Airlock IAM concept)
Loginapp Configuration
Adminapp Configuration
Service Container Configuration
Transaction Approval Configuration
IAM REST APIs
Customizing UIs and texts
Security best practices
Third-party licenses
Release and support
Release and support
Â
Info
See what is new in
IAM 8.7
:
IAM 8.7 - Release notes
.
Release lifecycle
Airlock IAM provides two
Long Term Support (LTS)
releases per year:
Spring LTS release
: Typically end of March
Fall LTS release
: Typically end of September
During the year, several
bugfix releases (BFRs)
are made available for supported LTS releases. Airlock decides which bugs are backported to which release.
Each LTS release is supported for
21 months
after its release date, until it reaches
end of support
. Supported releases are covered by the
Airlock support process
, allowing customers and partners to open support cases that will be investigated by our support team.
The following table summarizes the support lifecycle for Airlock IAM LTS releases:
LTS release version
Published
End of support
8.7
09/2026
06/2028
8.6
03/2026
12/2027
8.5
09/2025
06/2027
8.4
03/2025
12/2026
No longer supported:
8.3
09/2024
06/2026
8.2
04/2024
01/2026
Extended support
Ergon offers the possibility to extend the support services beyond the end-of-support date. Support for Airlock IAM can be extended by a maximum of 12 months, and is granted in blocks of at most 6 months each. This service is subject to an additional charge. To request a proposal for extended support, please contact
order@airlock.com
.
Update types
To deliver new features, improvements, and security fixes, Airlock IAM provides the following update types:
Major release updates
Introduce significant enhancements or architectural changes. Upgrading to a new major release requires a fresh installation.
Minor release updates
Deliver new features, improvements, and regular bug fixes. Updates from any minor release (X.Y) to the subsequent minor release (X.Y+1) are supported. Minor release updates cannot be uninstalled; downgrades reqiure a new installation.
Bugfixes and security updates
Promptly address critical security issues and other bugs in all supported release versions. Bugfix releases for LTS versions are provided for up to 21 months after the LTS release date.
Airlock semantic versioning
Airlock IAM versions are expressed as
x.y.z
:
x
is the major version.
y
is the minor version.
z
is the bugfix version.
This scheme follows the
Airlock semantic versioning
terminology.
A release is considered
major
whenever it contains
breaking changes
.
Breaking changes
require manual changes to existing features in one of the following areas:
Documented REST APIs
Configuration (XML or YAML,
instance.properties
, environment variables)
Loginapp Design Kit
DB schemas
Â
Notice
Changes on non-published features or features marked as incubating (see
Incubating features
) are not considered breaking.
Release artifacts
We provide additional artifacts that can be used with Airlock IAM. This may include documentation, examples, tutorials, and other resources. In general, these artifacts are only maintained for the most recent version. Airlock decides which artifacts are also maintained for older versions.
Chapter content
IAM 8.7 - Release notes
IAM 8.7 - Changelog
IAM 8.7 - Required upgrade actions
IAM 8.7 - Deprecation announcement
Incubating features