All versions of this manual
X
Welcome to Linkurious administration manual v4.3.1. Use the menu to access other documentations.
  1. Introduction
  2. Feature Availability
  3. FAQ
  4. Getting started
    1. Version support policy
    2. Release notes
    3. Client requirements
    4. Graph DB Feature Map
  5. Deploying on premise
    1. Technical requirements
    2. Downloading
    3. Installing
    4. Starting Linkurious
    5. Stopping Linkurious
    6. Cluster mode
  6. Configuring
  7. Troubleshooting
    1. Checking Linkurious status
    2. Reading the logs
    3. Getting support
    4. Managing licenses
    5. Vulnerabilities
  8. Importing graph data
    1. Neo4j
    2. Memgraph
    3. Amazon Neptune
    4. Cosmos DB
    5. Spanner Graph
    6. Updating your graph data
  9. Updating Linkurious
    1. Checking for updates
    2. Backing up your data
    3. Update procedure
  10. Configuring data-sources
    1. Neo4j
    2. Amazon Neptune
    3. Memgraph
    4. Google Spanner
    5. Cosmos DB
    6. Alternative IDs
    7. Merging data-sources
    8. Advanced settings
  11. Resource management
    1. Managing spaces
    2. Managing tags
  12. Search index
    1. Search Option Comparison
    2. Neo4j Search
    3. Elasticsearch
    4. Neptune Search
    5. Google Spanner Search
    6. Azure Search
    7. Incremental Indexing
    8. Numerical/Date search
  13. User-data store
    1. Migrating to an external database
    2. Backing-up your store
  14. Web server
  15. Authentication
    1. Getting started
    2. LDAP / Active Directory
    3. SSO with Azure
    4. SSO with Google
    5. SSO with OpenID Connect
    6. SSO with SAML2 / ADFS
    7. Configuration
  16. Access control
    1. Managing users
    2. Managing groups
    3. Standard access-rights
    4. Property-key access-rights
  17. Guest mode
    1. Guest mode
  18. Data Schema
    1. Property types
    2. Hiding data
    3. Strict mode
  19. Alerts
    1. Configuration
  20. Entity resolution
    1. Requirements
    2. Installing
    3. Configuring
    4. Accessing Entity Resolution
    5. Managing mappings
    6. Running Entity Resolution
    7. Viewing Results and explanations
    8. Node Grouping and Collapsing
    9. Managing the license
    10. Troubleshooting tips
  21. Email Notifications
    1. Configuration
  22. Visualizations appearance
    1. Default styles
    2. Default captions
    3. Default properties order
    4. Geographic tiles
  23. Audit trail
    1. Log format
  24. Webhooks
  25. Observability
  26. Plugins
    1. Query AI
  27. Deep link
 

Getting started: Release notes

Changelog for Linkurious Enterprise v4.3.1

Release Date: 2026-01-26

New Features & Improvements (15)

  • (v4.3.0) Query AI: The feature is generally available
  • (v4.3.0) Visualization: Improve the design of the property panel (closed by default, resizable, show long text values, fixed headers in table view)
  • (v4.3.0) Authentication: Add a default value for access.loginTimeout
  • (v4.3.0) Browser Support: Updating the list of supported browsers
  • (v4.3.0) Deployment: Support defining an application-wide HTTP proxy using environment variables
  • (v4.3.0) Elasticsearch: remove official support for Elasticsearch 7
  • (v4.3.0) Embedded Elasticsearch: Remove the Embedded Elasticsearch on macOS
  • (v4.3.0) Embedded Elasticsearch: Update to Elasticsearch 9.2
  • (v4.3.0) Image Export: Deprecate the plugin-in in favor of the application feature
  • (v4.3.0) Neo4j: Drop technical support for Neo4j 4.3 and older
  • (v4.3.0) Queries: Improve the timeout behavior with workers when some queries run for a very long time
  • (v4.3.0) REST Client: Change the constructor parameters of the REST client (agent)
  • (v4.3.0) Search API: Allow more than one value for categoriesOrType parameter
  • (v4.3.0) Security: Increase the default password complexity requirements for local accounts
  • (v4.3.0) Security: Update to Node.js v24

Bug Fixes (27)

  • (v4.3.1) Queries: The Cypher auto-complete menu is sometimes misplaced
  • (v4.3.0) Alerts: An error is shown in the license modal when alerts are disabled
  • (v4.3.0) Alerts: Hiding columns in the Unified Case List only takes effect after refreshing the page
  • (v4.3.0) Alerts: In the unified case list, the model filter disappears once applied
  • (v4.3.0) Azure SSO: After upgrading to the v2.0 endpoint, we sometimes get the wrong email for users
  • (v4.3.0) Data model: Missing styles when you open the data model from the dashboard
  • (v4.3.0) Data-sources: Information in the data-sources admin page is outdated
  • (v4.3.0) Data-sources: Sometimes, when a data-source cannot connect, the whole application does not load
  • (v4.3.0) Deployment: The application is not starting when installed as a service on Red Hat 9.4
  • (v4.3.0) Documentation: Misleading "Shortest path analysis" in the feature map
  • (v4.3.0) Documentation: Missing timeline zoom limitations
  • (v4.3.0) Documentation: Specify that the "id" field is required for Azure Search
  • (v4.3.0) Entity Resolution: Missing confirmation pop up when cancelling after deleting a mapping attribute
  • (v4.3.0) Google Spanner Graph: It is not possible to configure multiple data-sources for different graphs in the same database
  • (v4.3.0) Node grouping: An error is shown when deleting a mix of regular and grouped nodes
  • (v4.3.0) Node grouping: Node counters are not recomputed after an "undo" action
  • (v4.3.0) Node grouping: Node groups are not always collapsed by default
  • (v4.3.0) Node grouping: When selecting a node group, filtered-out nodes are displayed in the table
  • (v4.3.0) Queries: For node inputs, the autocomplete fails if the node input specifies more than one node label
  • (v4.3.0) Search: In some places, the application is using a hardcoded fuzziness instead of the configured defaultFuzziness
  • (v4.3.0) Search: Remote items are sometimes returned when local search is selected
  • (v4.3.0) Telemetry: Possible file handle leak when synching archived events
  • (v4.3.0) Visualization: After pinning and expanding a node group, the pin appear larger
  • (v4.3.0) Visualization: In the property panel, IDs are not aligned correctly
  • (v4.3.0) Visualization: In the selective expand modal, the "limit" input is too small
  • (v4.3.0) Visualization: Thumbnails are sometimes very different from the actual visualization
  • (v4.3.0) Visualization: Wrong values in the timeline after removing items from the visualization

Breaking changes (9)

  • (v4.3.0) The default session timeout is now 3 hours: users get logged out after 3 hours of inactivity. When the access.loginTimeout configuration is not set, the default value is now 10800 seconds. The previous behavior was to never expire sessions when this configuration was not set.
  • (v4.3.0) We are removing support for browser versions released more than 2 years ago. The oldest version supported is now 119 for Google Chrome, 119 for Microsoft Edge, and 120 for Firefox.
  • (v4.3.0) If you are using environment variables like HTTP_PROXY, HTTPS_PROXY or NO_PROXY to enable proxying of outgoing HTTP traffic, you must now set NODE_USE_ENV_PROXY=1 for these environment variables to be taken into account. If you were using the "proxy" option for a Neo4j data-source, this option is now ignored and you must now use the aforementioned environment variables.
  • (v4.3.0) Deployments that use Elasticsearch 7 must update to Elasticsearch 8+
  • (v4.3.0) If you are running the Linkurious Enterprise server on macOS, Embedded Elasticsearch won't be available on macOS anymore. If you need an Elasticsearch instance, we advise you use another way to host Elasticsearch. Please refer to the official Elasticsearch documentation to host it yourself on macOS or other platforms.
  • (v4.3.0) The Image export is no longer an official plug-in, the same functionalities are now integrated in Linkurious Enterprise.
  • (v4.3.0) The lowest supported Neo4j version is v4.4.0.
  • (v4.3.0) The optional parameter agent of the RestClient constructor has been removed. This parameter was normally not meant to be used, besides a few advanced specific use-cases.
  • (v4.3.0) When using default settings, password for local accounts must now have at least 12 characters.