/
Changelog (tC)

Changelog (tC)

When Updating from a version < 3.4.0 to a version >= 3.4.0, it must be ensured, when using a database metaservice, that there are not multiple content servers using the same database.
With version 3.4.0 a change in the database structure was made, which is not compatible with prior versions. The database change is done automatically upon first start. The parallel usage of the same database with tia core server instances with version < 3.4.0 and version >= 3.4.0 is therefore not possible.

3.18.0

06.05.2026

Features

Improvements

  • Improved error message when failing volume connection check test.

Fixes

  • ProxyMetaService now deletes Objects in Primary and Secondary

  • TimestampRequests from KgsStore can now be correctly validated

3.17.7

14.04.2026

Fixes

  • Added another fallback with migrated data.

  • Updated Libraries.

3.17.6

01.04.2026

Fixes

  • fix an issue that prevents deletion from secondary ContentService in proxy scenarios when AzureV2 is used as primary ContentService

  • add a fallback encoding to increase compatibility with documents that where stored with tia ContentServer classic and Migrated to tia ContentServer Core

  • increase resilience for Volume Counter export

  • Optimize Indices for MetaService with Oracle Databases

  • Increase performance with CMIS MetaService Queries in large repositories for Oracle and Microsoft databases


3.17.5

11.03.2026

Fixes

  • Updated multiple libraries und base container image.

3.17.4

23.02.2026

This release is not published as war file.

Fixes

  • Updated the base container image.

3.17.3

30.01.2026

Fixes

  • Fixed offset handling with S3 and Azure. This issue was introduced with 3.17.0. This is relevant for ArchiveLink, ILM and CMIS.

3.17.2

19.01.2026

Fixes

  • A bug was fixed that had prevented TSR validations from being executed.

3.17.1

13.01.2026

Features

  • ICAS hardware lock is now also executed when the ICAS and ContentServer times differ by 1 second.

Fixes

  • The ArchiveLink API now returns the correct HTTP status code 401 instead of 403, when the certificate is not found or the secKey is not valid


3.17.0

29.12.2025

Features

  • The WAR-Deployment requires Java 21.

  • ArchiveLink:

    • Added a new config setting <repo>.saphttp.enforceContentLengthHeader (default:false). When enabled, PUT-Requests to create new components without a valid Content-Length header are rejected.

    • Added new settings for forcing Content-Disposition to specific values depending on the results MimeType. The parameter <repo>.saphttp.mimemapping.<n>.contenttype defines the Mimetype to which the mapping applies and <repo>.saphttp.mimemapping.<n>.contentdisposition the Content-Disposition header on component get.

Improvements

  • Reworked Offset handling for all endpoints to only fetch requested bytes for Azure V2 and all S3 content service types.

  • Updated the TimeStampRequest authority certificates.

  • When validating existing TimeStampRequests, the validation is successful when the initial signer certificate has expired now but was valid at the time of signing.

  • The amount of memory used for caching files can be changed. The parameter tia.streamprocessor.memoryfraction can be set for the whole instance. The default is 0.005 (which means 0,5% of the available memory can be used).

  • The volume reporting does not happen every time an instance is started.

  • Added retries for ContentService filesystem based storage for delete and lock.

  • Added a fallback when reading x-amz-meta-content-disposition from s3 compatible storage to handle encoding.

  • Added new indices for Oracle metaservices.

Fixes

  • Fixed the protocol entries for ArchiveLink operations resulting in 500 Server error.

  • Fixed an issue with connections in aws s3 introduced with 3.16.0.


3.16.1

05.12.2025

Improvements

  • Added fallbacks for kgsStore when accessing s3 and fs with codedId components.

Fixes

  • Fixed rendition service for multipagetiff when encountering non-standard mime types.

3.16.0

04.11.2025

Features

  • Change the location of all elements in the .kgs folder and always separate by repository regardless of ContRepInPath setting.

  • ArchiveLink:

    • Added new setting saphttp.forcecomponent. When set to true a get request without a component id tries to return a component even in case there is no component named data or data1. Additionally a list saphttp.forcecomponent.ignorelist defines which componentnames are not taken into account.

  • CMIS:

    • Added support for queries using <>, IS NOT NULL and NOT LIKE.

    • Added support for IN/NOT IN with value lists.

Improvements

  • The field bucket will be filled when using ProxyContentService.

  • The volume counter export which is sent automatically is now compressed.

Fixes

  • Fixed kgsStore not respecting existing data with DataEncoding = 1.

  • Fixed ProxyMetaService not sending updates to secondary and failing to initialize secondary.

  • Fixed Volumecounter writing data always to first used root in SplitFileSystemV3 (and derived). Now it uses the at the time active root. This applies also to metadata-definitions.

  • Fixed rendition service for multipagetiff when encountering non-standard mime types.

  • Fixed an error with a connection not properly closed.

  • CMIS:

    • Fixed boolean queries when using database based metaservice.

    • Fixed like queries when using database based metaservice.

3.15.1

26.08.2025

Improvements

  • Changed storage for volume counter files to always separate by repository regardless of contrepinpath setting.

  • Fixed library for Azure when using kgsstore, no need vor manual add of libs any more.

  • Improved logging error responses with Azure.

Fixes

  • Removed validation for contRepInPath added in 3.15.0

  • Fixed issue with space running into error on info request.

  • Removed credentials in CMIS repository info.

3.15.0

01.08.2025

Features

  • ArchiveLink:

    • Added parameter <repo>.saphttp.allowedclients to limit write access to specified IPs or hostnames. Defaults to *.

    • Added parameter <repo>.saphttp.allowedcsadminclients to limit the use of SAP CSAdmin function to specified IPs or hostnames. Defaults to *.

    • Added parameter <repo>.saphttp.trustedforwardedservers to specify IPs or hostnames which are trusted as proxy servers. Defaults to *.

Improvements

  • Added validation for filesystem-based storage backends to prevent using the same archive folder with multiple repositories without using ContRepInPath=true.

  • Improved stability of VolumeCounter connection check.

  • Hide internal file operations from protocol. Added option <repo>.protocolservice.writeinternal, set to true enabled those entries. Default is false.

Fixes

  • Fixed usage of S3 with kgsstore as secondary with contentservice proxy.

  • Fixed access to TimeStampSignatures when using kgsstore.

  • Fixed issue with high load when using storage-based keystore for ArchiveLink certificates.

  • Fixed an issue with not working WAR-Deployments.

  • Fixed bucket creation for S3-Netapp.

  • Fixed an error when using TSR and configData type storage.

3.14.2

24.06.2025

Improvements

  • ArchiveLink:

    • Added another fallback for component id replacing spaces with +

Fixes

  • ArchiveLink:

    • Removed wrong header Content-Encoding from responses.

3.14.1

23.05.2025

Improvements

 

3.14.0

13.05.2025

Improvements

 

3.13.3

15.04.2025

Fixes

  • Added more fallbacks for encoding in kgsstore

  • added option to set CMIS baseurl globally (tia.cmis.baseurl) or per request (X-tia-cmis-baseurl) using a scheme of http://somewhere.host:8999/browser/{repositoryId}

3.13.2

03.04.2025

Fixes

  • Fixed an error with ArchiveLink and LogLevel debug with potential loss of data introduced with 3.13.0.

3.13.1

27.03.2025

Fixes

  • Fixed checking of writeable files in icas and icasv3.

  • Fixed setting no hardwarelock for icas and icasv3 despite having configured retention.

  • Fixed an error with compressed files in kgs store and sending wrong content size.

3.13.0

14.03.2025

Features

  • ArchiveLink: Added support for pVersion 0047. Default is 0047, added new parameter <repo>.saphttp.pversion=0046sending 0046. Due to the requirement that a virusscan should be performed (unless parameter scanPerformed=true is set) a message is printed out (level info) that now scan actually happened when no customVirusScan is configured (which is the default).

  • Added support for CustomMetaService with tia link.

  • Added option to include TraceContext in the protocol. Can be enabled by using the key traceid with the new configuration parameter <repo>.protocolservice.additional.properties = traceid

Improvements

  • ArchiveLink:

    • Added the possibility to log all Headers and Body for ArchiveLinkRequests. Disabled by default due to performance issues, can be enabled by logging.level.com.software.kgs.autodigit.saphttp.configuration.CxfLoggingConfig=DEBUG

    • In case an invalid MIME-Type was stored, the request returns the generic application/octet-stream instead of failing.

    • Improved performance when using Proxy with KgsStore and retrieving files by stream position.

  • Removed limit of 5GB when using S3 storage.

  • Improved performance of protocol-database delete routine.

  • When using a file based storage, the real storage path is logged.

  • When using the custom services, the TraceContext is sent along to the backend.

  • When using the CustomVirusScan, a header X-ObjectPath is sent along containing the path of the object.

Fixes

  • CMIS:

    • When opening the getContent-link for an object without sending credentials and auth is active, the user is now asked for credentials.

    • Fixed an issue when setting Retention on objects on initial requests.

    • Fixed issue with CMIS and using no meta service.

  • Fixed issue in SplitFileSystemV3 now allowing to store files with a filename longer than 250 chars (encoded).

  • Fixed an issue with Proxy and SplitFileSystemV3 retrieving files with very long names from the secondary when the primary is SplitFileSystemV3.

  • Fixed an issue with a failing connection check to VCRS. Ensure that the parameter volumecounter.mode: file is set. Otherwise the button will now not be visible.

  • Fixed an issue when using Proxy with KgsStore and S3.

3.12.4

17.02.2025

This release is not published as war file.

Fixes

  • improve support for Icas and readOnly files

3.12.3

05.02.2025

This release is not published as war file.

Fixes

3.12.2

31.01.2025

Fixes

  • Fixed an performance issue with SAP CMIS Queries

  • Fixed an issue with CMIS secKey when special characters are used in the key

3.12.1

06.01.2025

Fixes

  • Fixed an issue when using kgsStore with S3 or Azure backend.

3.12.0

30.12.2024

Feature

  • Added compression service available as <repo>.compressionservice.type with values no_compression (default), gzip or bzip2.

    • Added support for storing compressed files using GZIP or BZIP2

    • Support for extracting compressed files with kgsstore

Fixes

  • Fixed RenditionService in combination with AzureBlobStore (both versions)

  • Fixed multiple inconsistent included libraries.

3.11.3

16.12.2024

Fixes

  • Fixed Azure Managed Identity with Database.

  • FIxed error with MultiPageTiffRendition whensource files already have multiple pages

  • CMIS: Fixed error with out of memory when using cmis putCert

3.11.2

06.12.2024

Fixes

  • Fixed issues with contentservicetype s3hcpblobstore.

Features

  • Added the setting versioningstatus for all S3-Based ContentServices, with values auto (default)/enabled/disabled. With enabled/disabled, the call to ask the bucket whether it supports versioning is skipped and the defined state is used.

3.11.1

26.11.2024

Fixes

  • Fixed an issue with getting content with no or invalid mimetype in content-disposition.

3.11.0

19.11.2024

Features

  • Added feature to combine single file tiff components to one multipage tiff. This can be basically enabled by adding <repo>.rendition.multipagetiff.mode=on_demand.

    • CMIS: The rendition is triggered by using the stream-ID multipagetiff. It then combines all tiff-files in the current directory to one multipagetiff.

    • SAPHTTP: In case a compGET is executed for compIDs data, data1, DATA or DATA1 and it is a tiff-file, all tiff components are combined to one multipagetiff and returned.

Improvements

  • Added a fallback when fetching ArchiveLink components: if the original request fails with a “Not found”, it tries again with all “+” in the compID replaced by “ “ (space). Similar to how classic worked.

Fixes

  • Fixed an issue with s3 contentService and configdata.type=storage with an error message.

  • Fixed when sending no compID on compGET to return either data or data1 component if it exists.

  • Fixed when creating an object and this fails and the rollback in delete produces and error, the original create error was discarded. The delete error is no logged and the original error is thrown.

  • Fixed when using proxy with kgsstore with s3 failing on startup.

3.10.0

06.11.2024

Features

  • CMIS: Implemented support for secKey usage in CMIS with new option .authentication.cmis.type = tokenseckey.

Fixes

  • Certificates were not shown in UI and SAP when using keystore.type storage and pkcs12_storage after restart.

  • Fixed an issue with using Custom VirusScan and RetentionService was not possible.

  • Added a fallback behavior for ArchiveLink getComponent: When the first attempt fails with a “Component not found” alternative encodings for the same component id are also tested.

3.9.0

11.10.2024

Fixes

  • Within type definitions, the setting required=true for properties is no longer be ignored. Any property with this setting and no value provided, the operation will fail.

  • Fixed an issue with missing protocol entries when using elastic or opensearch protocol service with fallback active.

  • Fixed an issue when using sfsv3 or netappv3 with wrong storage introduced with version 3.7.2. Existing objects may require manual work if errors occur on object update.

Features

  • A new option for custom virusscan scangetrequestswas added. Defaults to false, when set to true every get-Request leads to a virusscan.

  • The result of the virusscan is also available in the protocol as property virusscan.

Improvements

 

3.8.2

04.10.2024

Fixes

  • Fixed an issue with ArchiveLink when fetching an encrypted document

3.8.1

13.09.2024

Fixes

  • Fixed an issue with Content-Disposition header and special characters in ArchiveLink when using war deployment or container deployment with version before 3.7.0

3.8.0

09.09.2024

Features

  • Added option to set destructionDate using retentionService with destructionperiod = which now allowed expirationperiod to be 0 0 0 0 0

  • Added option to use ManagedIdentity for blob store and database

Fixes

  • Fixed using Splitfilesystemv3 (and variants in icas and netapp) as proxy primary.

  • Fixed using tia encryption with s3 (and variants).

  • Fixed error with retention inheritance when using <repo>.hardwarelock.mode=nolock.

  • Added new tia link endpoint for storage (customv2) to solve issue with / in object ids. Usage requires the implementation of the v2 endpoint for the tia link api.

  • Fixed visibility of volume counter test button.

  • Increased time between sending volume data.

3.7.2

15.08.2024

Fixes

  • Fixed using password for OpenSearch Serverless in AWS as alias in KeyStore

  • Fixed handling of iCAS storage for both icas and icasV3. All files are now archived. Existing files will not be changed until update happens

3.7.1

02.08.2024

Fixes

 

3.7.0

30.07.2024

Fixes

  • Swagger UI (OpenAPI) is using the servlet path and can be used in war deployments

  • OSGI: fix an issue that prevent starting the application

  • Elastic Search Meta-/Protocolservice: Fix a thread issue when Fallback is used

  • Status Webapp: Fix a wrong display of the features, when the license is refresh during runtime

Improvements

  • Elastic Search Meta-/Protocolservice: Improve offline recognition of indexes

 

3.6.1

08.07.2024

Fixes

  • fix an issue when retention is expired and the file is getting deleted for iCAS Storages

3.6.0

08.07.2024

Improvements

  • new ContentService SplitFileSystemV3 available (V2 and V1 are still supported but in maintenance mode) see