The Release Notes for Assets Server contain information about the new features, changes, fixed issues, known issues and upgrade instructions for each release of WoodWing Assets Server.
The versions are sorted by version number in descending order. Use the Navigation block to the right of the page to quickly navigate to the information of a released version, or filter the article by version to only show that version.
Note: This article contains the Release Notes for Assets Server version 6.116 (released March 2025) and higher. For the Release Notes for other Assets Server versions, see these articles.
|
Filter by version:
|
Assets Server 6.122
Assets Server version: 6.122.1.1303
Release date: 11 August 2026
New features
The following features have been added in this release of Assets Server:
- Security features: Additional HTTP response security headers have been added. To improve the security of Assets Server, the following HTTP response security headers have been added:
- Cross-Origin-Embedder-Policy
- Cross-Origin-Opener-Policy
- Cross-Origin-Resource-Policy
- Feature-Policy
- Permissions-Policy
- Referrer-Policy
For details, see Assets Server security features overview.
- Synchronous GET API requests in the 'Stats cleanup' API have been changed to asynchronous POST API requests and can be monitored in the Management Console. In the Stats cleanup API, previously blocking synchronous GET API requests have been changed to asynchronous POST API requests.
The following operations now run asynchronously:
- removeActivity
- removeHistory
- removeSearch
- removeUsage
They return the ID of the started process on the Server Status page of the Management Console under Processes > Running.
Their progress can be observed and canceled from the Management Console, and their output is added to the server log.
- User names that are e-mail addresses may now contain a +-character. In e-mail addresses, it is quite common to create a variation on an already existing e-mail based on a user name by including a +-character. In previous versions of Assets Server, the +-character was not allowed to be part of a user name, which meant that e-mail-based user names could not be used. This has now changed, and a +-character is now also allowed as part of a user name.
Changes
No changes have been made in this release of Assets Server.
Fixed issues
The following issues have been fixed in this release of Assets Server:
LVS-20462 File saved to S3 without file extension.
LVS-20436 Asset search response includes folders.
LVS-20425 Reduced redundant searches and oversized count requests in the web client.
LVS-20407 Update bundled JDK 8 to the latest build.
LVS-20315 Fix double URL decoding of usernames in Management API.
LVS-20297 Reduce search result page sizes and remove duplicate checkout data fetch.
LVS-20296 Inconsistent IP address masking in Management Console.
LVS-20279 Rapid consecutive renames failing with metadata errors.
LVS-20213 Keep renamed group selected in the Groups list after rename.
LVS-20212 Auto-scroll to and highlight the newly created user in the Users list.
LVS-20211 Preserve Users list filter after creating a new user.
LVS-20199 Allow the "+" character in email-based usernames.
LVS-20148 Improve performance of linked files requests to the backend and Elasticsearch.
LVS-20132 Restored folder is not removed from Trash Can page and folder.
LVS-20126 Optimize search queries for Pinned Collections.
LVS-20123 Profile requests trigger unnecessary security cache rebuilds.
LVS-20120 Users not listed under groups with spaces in Management Console.
LVS-20090 Archive flow incorrectly clears sceUsed on Production Zone variants that are themselves registered shadow objects.
LVS-20039 URLs with parentheses cut off in metadata fields.
LVS-19940 Stats removeHistory API fails to delete history entries for orphaned assets.
LVS-18390 Index Revision page inaccessible after a re-index completes.
LVS-17815 Automatic version cleanup failing to remove old versions.
Known issues
The following known issue exists in this release of Assets Server:
- Localization API does not return default messages used in the client. The localization API does not return default messages from the client. However, it still returns field labels and custom messages. If your customization relies on a message key from Assets Server, add the key and expected value as a custom message.
Installing and upgrading
Use one of the following installation paths:
- Installing Assets Server on a system on which it is not yet installed
- Upgrading an existing installation of Assets Server
Downloads
The download files for this release of Assets Server can be found in the Release announcement.
Documentation
The following changes to the documentation have been made in this release of Assets Server:
- Assets Server security features overview - updated
- Assets Server API - Stats cleanup - updated
- Managing users and user groups in Assets Server - updated
Assets Server 6.121.2 Quick Patch
Assets Server version: 6.121.2.1280
Release date: 28 May 2026
Fixed issues
The following issue has been fixed in this release of Assets Server:
LVS-19959 The Shared Link dialog does not close, and the confirmation message is not displayed after sharing assets.
LVS-20027 Context menu persists in folder hierarchy when clicking the browser Back button.
LVS-20284 Brand portal: File extensions are missing in the Filter.
Installing and upgrading
Use one of the following installation paths:
- Installing Assets Server on a system on which it is not yet installed
- Upgrading an existing installation of Assets Server
Downloads
The download files for this release of Assets Server can be found in the Release announcement.
Assets Server 6.121
Assets Server version: 6.121.1.1277
Release date: 12 May 2026
New features
The following features have been added in this release of Assets Server:
- Support for Red Hat Enterprise Linux 10.
- Support on Linux for files in JPEG XL (.jxl), OpenEXR (.exr), and AV1 (.avif) format.
Changes
The following changes have been made in this release of Assets Server:
- Processing LibreOffice documents on Linux is now done using Unoserver.
- The AWS SDK libraries used by Assets Server have been updated to AWS SDK for Java 2.x. As part of this update, IMDS v2 (Instance Metadata Service Version 2) is now supported.
- Support has been added for using the @-character in user names. E-mail addresses are often used as the user name. In previous versions, the @-character was not supported in user names. This has now changed, which makes it possible to use e-mail addresses as user names.
Fixed issues
The following issues have been fixed in this release of Assets Server:
LVS-19410 Add a bulk folder deletion API endpoint.
LVS-19582 Use native rawProcessor for CR3 files.
LVS-19583 Migrate Linux office document processing to Unoserver,.
LVS-19584 Support JPEG XL and OpenEXR image processing on Linux.
LVS-19585 Add support for RHEL 10.
LVS-19710 The Re-index progress page shows an incorrect state in a multi-node cluster deployment.
LVS-19902 User migration loses permissions for usernames containing uppercase characters.
LVS-19940 Stats removeHistory API fails to delete history entries for orphaned assets
LVS-19941 User migration is stuck due to duplicate user entries.
LVS-19958 Performance regression in authcred API request handling.
Known issues
The following known issue exists in this release of Assets Server:
- Localization API does not return default messages used in the client. The localization API does not return default messages from the client. However, it still returns field labels and custom messages. If your customization relies on a message key from Assets Server, add the key and expected value as a custom message.
Installing and upgrading
Use one of the following installation paths:
- Installing Assets Server on a system on which it is not yet installed
- Upgrading an existing installation of Assets Server
Downloads
The download files for this release of Assets Server can be found in the Release announcement.
Documentation
The following changes to the documentation have been made in this release of Assets Server:
- Compatibility of Assets Server - updated
- Supported file types in Assets Server - updated
- Managing users and user groups in Assets Server - updated
Assets Server 6.120.3 Quick Patch
Assets Server version: 6.120.3.1266
Release date: 16 March 2026
Fixed issues
The following issue has been fixed in this release of Assets Server:
LVS-19902 Internal users with capital characters in their name are not correctly migrated after upgrading to Assets 6.120.
Installing and upgrading
Use one of the following installation paths:
- Installing Assets Server on a system on which it is not yet installed
- Upgrading an existing installation of Assets Server
Downloads
The download files for this release of Assets Server can be found in the Release announcement.
Assets Server 6.120
Assets Server version: 6.120.2.1265
Release date: 10 February 2026
New features
No features have been added in this release of Assets Server.
Changes
The following changes have been made in this release of Assets Server:
- Managing internal users and user groups in the Management Console is now done through dedicated pages instead of through a configuration file. When no external LDAP system is available, managing users and user groups is done in Assets Server itself. This is typically the case when a very small setup is used such as a demo environment installed on a single laptop. Dedicated pages have now been added to the Management Console to make the process of managing these internal users and user groups more efficient, user friendly, and secure. In previous versions, this was done through the internal-users.properties.txt file.
The following has been added:
- On the Users page, a Profile tab has been added. It is used for enabling or disabling an account, and setting up the user's full name, initial password and the groups the user should belong to.
- On the Groups page, a Users tab has been added. It is used for managing which users should belong to the selected group.
When upgrading from a lower version of Assets Server, users that are defined in the internal-users.properties.txt are automatically migrated to the Elasticsearch index. After migration, the index is the single source of truth and the properties file is no longer used.
For more details, see Managing users and user groups in Assets Server.
- The Search REST API has been updated with a parameter with which it is possible to retrieve relations for multiple assets in a single search request. A parameter 'includeRelations' has been added to the Search REST API. When set to true, each hit in the search results will include a relatedAssetIds property containing the IDs of all assets related to that hit.
This makes it possible to retrieve relations for multiple assets in a single search request instead of making separate relation queries for each asset.
Fixed issues
The following issues have been fixed in this release of Assets Server:
LVS-18644 Master ID field is not embedded into the XMP metadata of a file.
LVS-19183 Include asset relations in the Search API.
LVS-19330 Unable to process JPG images with progressive compression.
LVS-19373 Preview generation fails for high-resolution JPEG images.
LVS-19546 Update Linux processing tools.
LVS-19566 PDF previews are generate with Incorrect text spacing.
LVS-19612 Improve internal users and groups management.
Known issues
The following known issue exists in this release of Assets Server:
- LVS-19902 Internal users are not correctly migrated after upgrading to Assets 6.120. This issue occurs when internal user names contain a capital letter (such as 'userName'). When that is the case, the permissions for the user are not linked correctly. In the permissions, it appears that there are two users, one with the capitalization and one without (such as 'username' and 'userName'). The permissions previously assigned will be visible for 'userName', but the user will log in with the permissions assigned to 'username'.
We are working on a fix and will be releasing a quick patch as soon as possible.
- Localization API does not return default messages used in the client. The localization API does not return default messages from the client. However, it still returns field labels and custom messages. If your customization relies on a message key from Assets Server, add the key and expected value as a custom message.
Installing and upgrading
Use one of the following installation paths:
- Installing Assets Server on a system on which it is not yet installed
- Upgrading an existing installation of Assets Server
Downloads
The download files for this release of Assets Server can be found in the Release announcement.
Documentation
The following changes to the documentation have been made in this release of Assets Server:
- Managing users and user groups in Assets Server - updated
- Upgrading Assets Server - updated
- Assets Server REST API - search - updated
Assets Server 6.119
Assets Server version: 6.119.1.1245
Release date: 16 December 2025
New features
The following has been added in this release of Assets Server:
- Support for Red Hat Linux 9 has been added. Red Hat Linux 8 remains the recommended version.
Changes
The following changes have been made in this release of Assets Server:
- Support for modern HEIC format images has been improved. Assets Server already generated previews for images in HEIC format, but this sometimes failed for images in this format that were generated by modern devices such as the latest smart phones. Support for generating previews for these images has now been improved.
Fixed issues
The following issues have been fixed in this release of Assets Server:
LVS-19049 Improve support for modern HEIC format images.
LVS-19155 Disable the deduplication logic during reindexing.
LVS-19193 Reduce the logs verbosity for the Lucene queryparser.
LVS-19344 Prevent unnecessary watermarked thumbnail regeneration.
Known issues
The following known issue exists in this release of Assets Server:
- Localization API does not return default messages used in the client. The localization API does not return default messages from the client. However, it still returns field labels and custom messages. If your customization relies on a message key from Assets Server, add the key and expected value as a custom message.
Installing and upgrading
Use one of the following installation paths:
- Installing Assets Server on a system on which it is not yet installed
- Upgrading an existing installation of Assets Server
Downloads
The download files for this release of Assets Server can be found in the Release announcement.
Documentation
The following changes to the documentation have been made in this release of Assets Server:
- Supported file types in Assets Server - updated
- Compatibility of Assets Server - updated
Assets Server 6.118
Assets Server version: 6.118.1.1243
Release date: 23 September 2025
New features
No features have been added in this release of Assets Server.
Changes
No changes have been made in this release of Assets Server.
Fixed issues
The following issues have been fixed in this release of Assets Server:
LVS-15959 Error 'Failed to invoke @ExceptionHandler method warning' is logged on server restart.
LVS-18728 Trash Can plug-in: Unclear message for non-admin users when deleting a folder.
LVS-18761 The Folder metadata update API returns a 'FolderNotFoundException' error when creating a folder on one node and trying to update it on another node.
LVS-18790 The API allows the creation of a Shared Link without a subject.
LVS-18800 Inconsistent Shared Link behavior between the API and UI: Collections are not Included via the API.
LVS-18915 The current Assets ulimit in the service definition causes major cluster instability during re-indexing.
LVS-18977 Add option to include processing queue content to the Support Tools.
LVS-19025 When uploading an image, the image dimensions are incorrectly set in the metadata.
LVS-19044 Webhook with asset_create_by_copy event is not working for Collections.
Known issues
The following known issue exists in this release of Assets Server:
- Localization API does not return default messages used in the client. The localization API does not return default messages from the client. However, it still returns field labels and custom messages. If your customization relies on a message key from Assets Server, add the key and expected value as a custom message.
Installing and upgrading
Use one of the following installation paths:
- Installing Assets Server on a system on which it is not yet installed
- Upgrading an existing installation of Assets Server
Downloads
The download files for this release of Assets Server can be found in the Release announcement.
Documentation
No changes to the documentation have been made in this release of Assets Server.
Assets Server 6.117
Assets Server version: 6.117.1.1239
Release date: 17 June 2025
New features
No features have been added in this release of Assets Server.
Changes
No changes have been made in this release of Assets Server.
Fixed issues
The following issues have been fixed in this release of Assets Server:
LVS-17972 Vast number of 'ERROR Caught exception while sending e-mail notification' messages in Assets Server logging after upgrading to Assets 6.107.
LVS-18548 The ExifTool is outdated.
LVS-18566 LibreOffice vulnereabilities CVE-2024-12426 and CVE-2024-12425.
LVS-18694 Unable to remove groups with an umlaut character in their name.
LVS-18703 When deleting files, the 'RemoveByQuery' process is not cleared.
Known issues
The following known issue exists in this release of Assets Server:
- Localization API does not return default messages used in the client. The localization API does not return default messages from the client. However, it still returns field labels and custom messages. If your customization relies on a message key from Assets Server, add the key and expected value as a custom message.
Installing and upgrading
Use one of the following installation paths:
- Installing Assets Server on a system on which it is not yet installed
- Upgrading an existing installation of Assets Server
Downloads
The download files for this release of Assets Server can be found in the Release announcement.
Documentation
No changes to the documentation have been made in this release of Assets Server.
Assets Server 6.116
Assets Server version: 6.116.1.1234
Release date: 25 March 2025
New features
No features have been added in this release of Assets Server.
Changes
No changes have been made in this release of Assets Server.
Fixed issues
The following issues have been fixed in this release of Assets Server:
LVS-18402 ImageMagick versions show significant performance difference.
LVS-18438 Error in Studio when archiving files: 'Archiving this layout failed. An error occurred while communicating with Assets Server. (S1144)'
LVS-18495 Allow underscores and hyphens in custom metadata fields when creating or updating webhooks.
Known issues
The following known issue exists in this release of Assets Server:
- Localization API does not return default messages used in the client. The localization API does not return default messages from the client. However, it still returns field labels and custom messages. If your customization relies on a message key from Assets Server, add the key and expected value as a custom message.
Installing and upgrading
Use one of the following installation paths:
- Installing Assets Server on a system on which it is not yet installed
- Upgrading an existing installation of Assets Server
Downloads
The download files for this release of Assets Server can be found in the Release announcement.
Documentation
No changes to the documentation have been made in this release of Assets Server.
Other Assets Server versions
For the Release Notes for other Assets Server versions, see these articles.
Comments
0 comments