With each new DataMiner version, certain features and third-party software integrations reach the end of their life cycle. Some of these are already no longer supported, while others will be phased out in future releases.
If a DataMiner functionality reaches End of Engineering, it will no longer be updated, but we will continue to support it for now. Once a feature has reached End of Support, it will no longer be updated or supported. The final step in the life cycle is the End of Life phase, during which the feature or compatibility will be removed.
These are the two most important features for which the life cycle has been updated recently:
- Two-site redundant indexing clusters are no longer supported when using Elasticsearch or OpenSearch. This has already been the case for some time, but now we also know when this feature will reach End of Life, i.e. in DataMiner 10.7 (Q4 2026). If you require redundancy for your data, we strongly recommend switching to STaaS, which offers two types of storage redundancy: zone-redundant storage and geo-redundant storage.
- Support for RADIUS authentication has reached End of Engineering. This type of authentication is deprecated as it is widely considered insecure because of several inherent flaws. If you still use this type of authentication, we strongly recommend switching to a more secure alternative such as SAML.
A life cycle update has also been added for several other features, including:
- Atlassian Crowd authentication
- The use of the displayColumn attribute in tables and the dllName option in the QAction options attribute within DataMiner connectors
- Logger tables of type DirectConnection with a primary key
Finally, for many features that were already marked as End of Support, such as the use of JScript and VBScript in QActions, we have now also added information about when these are planned to reach the End of Life phase. To find out more details, go to our software support life cycles page.