Want the full details? Click the link below!
What’s Changed in Reporting Only Module 3.2
PostgreSQL 18 Support
The Reporting Only module now supports PostgreSQL 18. We recommend planning your migration
before PostgreSQL 14 reaches end of life in November 2026, staying on an unsupported
version means no further security patches, which introduces risk in environments subject
to compliance requirements.
Other enhancements
- Upgraded the application to .NET 10.
- Improved overall page rendering performance across the application.
- Migrated the frontend build tooling, significantly improving page load times.
- Added warning banners to alert users when credential profiles become corrupted or the database goes offline.
- Added an error message in the installer when the PowerShell execution policy prevents installation.
- Improved the database migration experience in the setup wizard to reduce friction for upgrade scenarios.
Bug Fixes and Miscellaneous Updates
- Fixed Okta OIDC integration sometimes preventing web console from loading. (Escalation 432708)
- Fixed the installer warning message colors not matching the updated design.
- Fixed an infinite request loop and gray screen occurring after a successful SAML/OpenID Connect login.
- Fixed Active Directory moved objects being logged as renamed instead of moved.
- Fixed the error recovery screen not allowing navigation to configuration pages.
- Fixed a user-friendly error message not appearing when NTM starts with PostgreSQL stopped.
- Fixed the “About Threat Manager” system settings page displaying an error screen.
- Fixed AD synchronization history showing no results.
- Fixed the backend service monitor not functioning correctly after service startup.
- Fixed an installer version detection issue that blocked installation when the same or newer version was already installed.
- Fixed the authentication provider settings displaying the wrong value after switching providers.
- Fixed Favorites investigations remaining visible after user permissions were removed.
- Fixed excessive duplicate logout requests being sent during sign-out.
- Fixed incorrect target and client column data for file system events from Isilon data sources.
- Fixed various UI components displaying outdated visual styles and misaligned checkbox elements.
- Fixed an empty error notification appearing for invalid integration URLs.
- Fixed the database availability API endpoint returning incorrect responses.
Need help with this update?
There are many different ways to get help with our products!
| Situation | Action |
|---|---|
| If you feel the product is broken and not working as intended… | Contact Support |
| If you have a question you’d like to ask other experts… | Create a discussion in the community: Threat Prevention > Discussions & Questions |
| If you have a feature request… | Let our product team know directly: Threat Prevention > Ideas |
| If you have something cool to show… | Show everyone what you built: Threat Prevention > Show & Tell |
What are your thoughts?
We are always happy to hear from our users on what you like, and what you hope to see in the future. Please, share your thoughts below!