search

v3.43.0

We are happy to announce release v3.43.0 of Elimity Insights, released on 7 January 2026.

hashtag
Summary

This section summarizes the most important changes in release v3.43.0.

chevron-rightNew functionalityhashtag

  • SailPoint IIQ built-in connector

  • Webhook-based ITSM integrations

chevron-rightBug fixes & improvementshashtag

  • OAuth2 authentication for all gateway-based built-in connectors

  • Minor bug fixes & improvements

chevron-rightDeployment changeshashtag

  • Required update of the NTFS gateway

  • Removal of the AccessReviewRequestedChangesEmail configuration option

  • Removal of the HttpsEnabled, TLSCertificate, TLSCertificateKey and TLSListeningPort configuration options

  • Removal of the EnableOIDCAuthentication and EnablePasswordAuthentication configuration options

  • End of support for executable-based deployments

hashtag
New functionality

hashtag
SailPoint IIQ built-in connector

Elimity Insights v3.43.0 includes support for SailPoint IIQ in its built-in connector library. This new connector imports users, accounts, entitlements, roles and applications from your SailPoint IIQ instance. Refer to our dedicated documentation for additional information.

hashtag
Webhook-based ITSM integrations

The v3.43.0 release also brings significant improvements for integrating with ITSM systems. Up until now, system admins had to set the AccessReviewRequestedChangesEmail configuration option and parse the incoming emails to create tickets in their ITSM system. We replaced this approach with a more flexible alternative based on webhooks. More specifically, admins can now simply configure a webhook URL which Elimity Insights triggers for each change request. Refer to our dedicated documentation for additional information.

hashtag
Bug fixes & improvements

hashtag
OAuth2 authentication for all gateway-based built-in connectors

Elimity Insights v3.42.0 brought some new configuration options to support strong authentication for imports via custom gateways. From v3.43.0 onwards, these configuration options also apply for all gateway-based built-in connectors. More specifically, Elimity Insights can now also use OAuth2 for authenticating requests to gateways for the following built-in connectors:

We strongly recommend replacing the older authentication method based on secret tokens as soon as possible. Elimity Insights v3.44.0 will only support OAuth2 for gateway authentication.

hashtag
Minor bug fixes & improvements

As always, this new release brings some smaller bug fixes and improvements:

  • The 'IMPORT FROM FILE UPLOADS' button on source detail pages now correctly links to the 'FILE UPLOADS' tab.

  • Labels indicating the archivation status of attribute types and sources now appear in more places throughout the user interface

  • The user interface now no longer constructs invalid or incorrect queries for some complex edge cases

  • We slightly adjusted the look and feel of the usage logs tab on our advanced settings page to increase consistency

hashtag
Deployment changes

hashtag
Required update of the NTFS gateway

Customers using the NTFS built-in connector must update their gateways to major version 2. Note that the secretTokenHash config option is now no longer effective, please configure JWT validation as described in our dedicated documentation.

hashtag
Removal of the AccessReviewRequestedChangesEmail configuration option

Since Elimity Insights now supports webhook-based ITSM integrations, the AccessReviewRequestedChangesEmail configuration value in elimity.yml is no longer effective.

hashtag
Removal of the HttpsEnabled, TLSCertificate, TLSCertificateKey and TLSListeningPort configuration options

From v3.43.0 onwards Elimity Insights no longer supports serving HTTPS traffic directly. We instead require a production-grade HTTPS proxy to provide the best security. This means the HttpsEnabled, TLSCertificate, TLSCertificateKey and TLSListeningPort configuration options in elimity.yml will no longer be effective. Please refer to our dedicated documentation for additional guidance on HTTP(S) proxies.

hashtag
Removal of the EnableOIDCAuthentication and EnablePasswordAuthentication configuration options

To improve security even further we also removed password-based authentication in v3.43.0. More specifically, OIDC-based authentication is now mandatory (we were already strongly recommending it for every production-level deployment); the EnableOIDCAuthentication and EnablePasswordAuthentication configuration options in elimity.yml are no longer effective. This change should affect very few customers; please contact your Elimity representative if you need assistance with migrating to OIDC-based authentication.

hashtag
End of support for executable-based deployments

From v3.43.0 onwards, we only support container-based deployments of Elimity Insights. We provide migration assistance to the few customers that were still using plain executables.

hashtag
Migration information

To migrate from v3.42.x to v3.43.0, we suggest the following steps:

  1. Make a backup of your existing database.

  2. Make a backup of your existing installation directory.

  3. Upgrade your installation by bumping the container image version.

  4. Migrate your database, as described in our dedicated documentation.

  5. Start the server and validate that it works as before.

Previousv3.43.1Nextv3.42.3

Last updated