Release notes for build #8073, release Apr 09, 2026

Build 3.7.8073

Improvements

Introducing support for HTTP file linking. This allows external files to be linked within the filespace by supplying a URL as part of the link request.
Use cases include linking data from web-based platforms that expose data through the HTTP/HTTPS protocol such as Google Drive, OneDrive, Dropbox, Box, Frame.io, and others.
HTTP file linking also supports providing pre-signed URLs generated by S3-compatible storages as an alternative to LucidLink-managed data stores and external entries.
Important notes:
- Creation of a data store is not required to leverage HTTP file links - you can create external entries with HTTP file links directly.
- Note that depending on the provider and implementation these types of URLs typically have a limited lifespan and must be refreshed periodically.
- Unlike external files linked by data store, HTTP file URLs are not refreshed automatically by LucidLink. Authentication with external services and retrieval/refresh of URLs for HTTP file linking is the responsibility of the customer.

Fixed a bug where the SSO enforcement setting could not be configured for LLMP-managed workspaces.