Page tree
Skip to end of metadata
Go to start of metadata

Magnolia end-of-life policy

Magnolia International Ltd. supports each major release of Magnolia for at least two years after the release of the following major version. For example, Magnolia 4.4 is supported for at least two years after the release of 4.5.

When the supported life of a version ends, we announce end of life (EOL) on this page. We do not provide formal support, bug fixes or security fixes for Magnolia instances that run an EOL version of the product. However, we do our best to assist customers who encounter issues with EOL versions of Magnolia. Enterprise customers who run an EOL version can use their support contract to verify issues, ask questions about the product, and get help with migration to a newer, supported version of the product.

Currently supported releases

SupportedReleasedEnd of life
Magnolia 5.62017-11-172020-06-30
Magnolia 5.52016-11-152019-11-15
Magnolia 5.4



UnsupportedReleasedEnd of life
Magnolia 5.3



Magnolia 5.2



Magnolia 4.5



Magnolia 4.4



End-of-life announcements

Magnolia end-of-life announcements

  • Magnolia 5.4 will reach end of life (EOL) on November 15, 2018. The 5.4 branch will not be maintained or supported after this date.
  • Magnolia 5.3 reached end of life (EOL) on June 30, 2017. The 5.3 branch is no longer maintained or supported.
  • Magnolia 5.2 reached end of life (EOL) on June 30, 2016. The 5.2 branch is no longer maintained or supported.
  • Magnolia 4.5 reached end of life (EOL) on June 30, 2016. The 4.5 branch is no longer maintained or supported.
  • Magnolia 4.4 reached end of life (EOL) on June 30, 2015. The 4.4 branch is no longer maintained or supported.

We encourage you to upgrade your sites to the latest release in the Magnolia 5.x branch. Learn more about Magnolia 5 features and benefits.

Versions earlier than those listed above are also in end-of-life status.

NTLM Connector module deprecation (21 November 2017)

The Magnolia NTLM (NT LAN Manager) Connector module is no longer supported. The module provided single sign-on (SSO) functionality for Windows systems within a trusted domain environment.

Microsoft no longer recommends the use of NTLM in applications due to security constraints:

Implementers should be aware that NTLM does not support any recent cryptographic methods, such as AES or SHA-256. It uses cyclic redundancy check (CRC) or message digest algorithms (RFC1321) for integrity, and it uses RC4 for encryption. Deriving a key from a password is as specified in RFC1320 and FIPS46-2. Therefore, applications are generally advised not to use NTLM.

Following Microsoft's recommendation, Magnolia ends support for the NTLM Connector module. This means we will not fix bugs related to the NTLM protocol. NTLM is no longer supported on any Magnolia version.

As a replacement we recommend the LDAP Connector and CAS modules:

CAS module enables Central Authentication Service (CAS) in Magnolia. CAS is a single sign-on (SSO) Web protocol that permits a user to log in once to a system and then automatically gain access to all related systems to which they have been granted permission as per their credentials. This avoids the need to log into each system individually. The Magnolia CAS module handles authentication only. When a user logs into CAS, the system authenticates their identity to participating services because the user has been authenticated to CAS.

Google Analytics module deprecation (November 15, 2017)

The Google Analytics module has been deprecated and removed from EE bundles. The module has modern replacements: Google Universal Visualization Analytics and Marketing Tags (module and app), which together provide the same functionality. Another reason for the deprecation of the module is that it used obsolete technology, namely third-party plugins that are no longer actively maintained.

Standard Templating Kit (STK) deprecation (September 15, 2017)

Standard Templating Kit (STK) was deprecated on September 15, 2017 and will reach end of life on December 31, 2018.

The replacement for STK is Magnolia Templating Kit (MTK), first released with Magnolia 5.4 on July 3, 2015. MTK is quicker to learn than STK and requires fewer skills. MTK is aimed at the increasing number of front-end developers who looked for something leaner and less time-consuming. MTE is front-end framework agnostic, which means you can integrate it with any modern framework such as Bootstrap or Foundation.

STK timeline:

  • 2009: First release
  • 2015: Maintenance mode
  • 2017: Deprecation
  • 2018: End of life

With the the release of Magnolia 5.6 we have stopped producing preconfigured bundles and webapps with the STK based demo. If you still rely on STK, see how to add STK to your bundle

Deprecated Web browsers for Magnolia (March 16, 2016)

On January 12, 2016, Microsoft ended support for Internet Explorer versions 8, 9 and 10. Internet Explorer 11 is the last version of Internet Explorer, and will continue to receive security updates, compatibility fixes, and technical support.

Following Microsoft's decision, Magnolia ends support for IE 8, 9 and 10. This means we will not fix bugs related to these end-of-life browsers. IE 8, 9 and 10 are no longer supported on any Magnolia version.

While Magnolia will continue to work with these older browsers, we recommend that you follow Microsoft's advice and upgrade to the latest version of Internet Explorer for security reasons.
Magnolia will continue to support IE 11 and Microsoft's new browser Edge.

Check out the Certified stack page for the list of supported browsers.

Raising issues for supported versions

You can raise issues for supported versions of Magnolia at Getting a fix may require upgrading to a version that includes the fix. Critical security fixes are backported to currently supported versions.

Extended support

To get extended support for your EOL version of Magnolia, contact Support for EOL instances is provided only under special terms agreed with the client.

Upgrading to a supported version

Magnolia International provides assistance upgrading your EOL version to a supported version. Contact to get help. Our experienced Services team will help manage and implement a smooth migration. A workshop done together with Magnolia experts and your team speeds up the move.

  • No labels