v3.44.0
We are happy to announce release v3.44.0 of Elimity Insights, released on 19 March 2026.
Summary
This section summarizes the most important changes in release v3.44.0.
New functionality
Configure visible attribute types for access reviews
Elimity Insights v3.44.0 includes support for configuring visible attribute types for access reviews. You can now manage and select visible attribute types directly when creating access reviews. This functionality is also available in the campaign template creation wizard and when editing campaign templates.
Support for editing campaign names and due dates
In this release, campaign names and due dates can now be easily edited after a campaign has been created.
Support for configuring the access review toolbar text color
The v3.44.0 release includes support for configuring the text color of the access review toolbar. You can now add the accessReviewToolbarTextColor configuration option to your config.hjson file. This works similarly to the existing accessReviewToolbarBackgroundColor option and defaults to white.
Bug fixes & improvements
Access profiles no longer apply for access reviews and access review managers
Access profiles no longer apply to access reviews. Users assigned the Access Review Manager role can now fully manage access reviews and campaigns, bypassing any previous access profile restrictions. This also means that access review managers can view identity data for all sources, so make sure to reassign roles as needed before you upgrade.
Support authenticating to Postgres via Azure Managed Identity
For customers deploying in Azure environments, Elimity Insights now supports authenticating to your Postgres database using Azure Managed Identity, streamlining credentials management.
To enable this feature, simply set the pgAzureManagedIdentity flag to true in your config.hjson file. When enabled, Elimity Insights will retrieve an access token from Azure and use it as a password for authentication with PostgreSQL.
Support reading configuration from a config file for the migration CLI
To simplify the database migration process, the migration CLI now supports reading configuration from a config.json file instead of requiring lengthy command-line arguments.
Minor bug fixes & improvements
As always, this new release brings some smaller bug fixes and improvements:
Added 'Created by' column to the table of access reviews on the campaign details page; previously you could only find this information on the access review details page.
Fixed an issue where filtering descriptions for data tables on entity detail pages showed incorrect counts.
The Entra ID built-in connector now includes 'app' and 'LastSuccessfulSignInDateTime' attribute types.
We've added a few enhancements for the SharePoint built-in connector:
you can exclude files based on a configurable glob pattern, and
we added some extra attributes for each imported site.
Customers using our SCIM built-in connector can now provide a bearer token instead of username and password for authentication.
Deployment changes
Required update of the SharePoint and Jira Data Center gateways
Customers using the SharePoint and Jira Data Center built-in connectors must update their gateways to major versions 5 and 3 respectively.
Added support for reading configuration from a single environment variable or file
Previously, configurations and secrets were split across two separate files (elimity.yml and secrets.yml).
Moving forward, you can consolidate your entire configuration into a single config.hjson file. Alternatively you can pass this unified configuration using a single new environment variable: INSIGHTS_CONFIG_HJSON. See our dedicated documentation for more information.
Please note that this will be the last release to support YAML file configuration.
Official support for Postgres 15 and 17
Elimity Insights now officially supports PostgreSQL 15 and 17.
Please note that this will be the last release to support PostgreSQL 15.
Migration information
To migrate from v3.43.x to v3.44.0, we suggest the following steps:
Make a backup of your existing database.
Make a backup of your existing installation directory.
Upgrade your installation by bumping the container image version.
Migrate your database, as described in our dedicated documentation.
Start the server and validate that it works as before.
Last updated