Knowledge Discovery 25.2.1
25.2 Release Notes

# ACI Server Framework

Many Knowledge Discovery components are built on the ACI server framework. This section lists the changes in the ACI server layer, which affect all ACI servers.

## 25.2.0

### New Features

There were no new features in this release.

### Resolved Issues

- Values imported into the application configuration as secrets, for example from environment variables, or HashiCorp® Vault, were displayed in the results of service actions that return a configuration file. Imported values are now removed or obscured in the results of service actions:

  - The `GetConfig` action replaces the value with ******, and annotates the key with a comment showing the original import line.

  - The configuration files packaged in the zip created by the `Diagnostic` are similarly redacted.

  - The `ValidateConfig` action does not include secret values in the response. Instead, these keys have a tag `<autn:keysecret>true</autn:keysecret>`.

## 25.1.0

### New Features

- Your configuration files can now include values to read from an external source. This option allows your system to inject sensitive settings, such as passwords, at run time, rather than storing them in the configuration file.

  ACI servers can read values from environment variables. This functionality can be used to access, for example, Kubernetes Secrets. A shared library is provided that can retrieve values from a key/value secrets engine in a HashiCorp® Vault installation.

  When you include a parameter from another configuration file, you can use a different name parameter name in the source and target files.

  For more information, refer to the Introduction to Configuration topic in the help for your component.

### Resolved Issues

- An `actions` directory was sometimes created at start up, even when the `Path` configuration parameter in the `[Actions]` section was configured to use a different location. This issue could affect all ACI servers that supported asynchronous actions.

## 24.4.0

### New Features

- The `autpassword` utility can encrypt configuration parameter values using a HashiCorp Vault Transit secrets engine. The encryption and decryption key is stored in the vault. You can add the encrypted string to an ACI server configuration file, and the server can decrypt the value when it is needed, by making a request to the vault.

### Resolved Issues

- The `QueueInfo` action did not return the correct number of results when the `MaxResults` parameter was set and the `Start` parameter was greater than 1.

  IMPORTANT: The `MaxResults` parameter specifies the maximum number of results to return (`&Start=2&MaxResults=3` returns results 2, 3 and 4, not 2 and 3). Applications depending on the incorrect behavior might need to be updated.

## 24.3.0

### New Features

There were no new features in this release.

### Resolved Issues

- The Lua function `send_http_request` sent a plain HTTP request (not HTTPS) when an HTTPS URL was specified in parts by using the `site`, `port`, and `uri` named parameters.

## 24.2.0

There were no new features or resolved issues in this release.

## 24.1.0

### New Features

There were no new features in this release.

### Resolved Issues

- Sending a long unknown action to an ACI server could cause an interruption of service.

## 23.4.0

### New Features

- ACI servers no longer reflect a null origin request header in their Access-Control-Allow-Origin response header (in line with W3C guidance).

### Resolved Issues

- The `BackupServer` action could fail to backup the datastore files for connector tasks.

## 23.3.0

### New Features

There were no new features in this release.

### Resolved Issues

- An IDOL ACI server (running on Linux) would stop if it received a SIGPIPE signal.
- An IDOL ACI server would fail to start if the fully-qualified host name could not be resolved to an IP address.

- Attempting to POST a large file (larger than 2GB) to an ACI server (for example Media Server) resulted in an error.

## 23.2.0

### New Features

- IDOL ACI servers now use OpenSSL3 to provide FIPS 140-2 support on both Windows and Linux. This change means that you can run FIPS-enabled IDOL components with the standard component downloads and installers.

  For information about how to configure FIPS with these new packages, refer to the FIPS Enablement Technical Note.

  NOTE: The FIPS-enabled packages for Red Hat Enterprise Linux (RHEL) 7 and RHEL8 platforms are still available, with the existing configuration. These packages use the system version of OpenSSL (expected to be in the 1.0.x series for RHEL7 and the 1.1.x series for RHEL8).

- When the `LogEcho` configuration parameter is set to `True`, components now print license and service errors to stdout, as well as the log file. This change makes it easier to view these errors, particularly when using components in containers.

### Resolved Issues

- Links in the ACI server `GetRequestLog` HTML now work correctly when the server is behind a reverse proxy.

Copyright 2025 Open Text
Version 25.2.1 | Last updated April 2025

Send documentation feedback

Close

Send documentation feedback

To send feedback using your default email client, open an email window.

Otherwise, send your feedback and the information below to MFI-swpdl.idoldocsfeedback@opentext.com.

We appreciate your feedback!

Product: Knowledge Discovery 25.2.1

Topic Title: ACI Server Framework