Innovation Release Filr 24.1 is an update for Filr 23.4 includes new features, enhancements, and defect fixes.
If you have suggestions for documentation improvements, click Comment on this topic at the bottom of the specific page in the HTML version of the documentation posted on the Filr Documentation page.
This section summarizes the new features and enhancements in the Filr 24.1 release and patches.
Filr 24.1.1 patch release for Filr/Search /CE appliance and 23.4.1 patch for PostgreSQL appliance.
The following are the defects fixed in Filr 24.1.1:
After updating to 24.1, a Null Pointer Exception is triggered, and the user fails to log in.
If the partition label does not have "vastorage", then the update to Filr 24.1 fails and the user cannot log in to Filr.
filr.service starts even before the network is up.
"Register User Profiles Automatically" option does not work after upgrading to 23.4.
In the Filr Desktop Client, the folder name changes if the folder name contains non-ASCII characters.
If the Filr server is using a self-signed certificate, then upgrading from 4.3.1.3 to 5.0 and then updating to 24.1/24.1.1 will fail.
Filr Administration Mail Settings is honored by GroupWise Plugin. GroupWise integration with Filr lets you send file attachments as Filr links. Filr lets you protect, expire, and clean up mail attachment links. In addition, you can also send links to Filr files from My Files, Shared With Me, and Net Folders in a GroupWise mail. For more information, see Integrating Microsoft and GroupWise with Filr in the OpenText Filr 23.4: Administrative UI Reference.
Filr deployment can be effectively monitored using Prometheus and Grafana. You are allowed to Monitor system metrics Filr, Search, and Postgres Appliances (Large Deployment). For more information, see OpenText Filr 23.4: Monitoring Server Health with Prometheus and Grafana.
Filr can now be configured with two PostgreSQL appliances with one acting as a standby appliance. This database is a replica of the primary database that the Filr application uses. If the primary database server fails to respond, the standby database is activated and acts as a primary database. Filr can then be pointed to use this database. For more information, see Standby Database Appliancein the OpenText Filr 23.4: Installation, Deployment, and Upgrade Guide.
Beginning with Filr 24.1, the following are the supported platform changes:
Table 1 Supported Platforms
|
Components |
Filr Appliance 23.4 |
Filr Appliance 24.1 |
|---|---|---|
|
Android Phones and Tablets |
|
|
|
OES (Standalone and Clustered environment) |
IMPORTANT:You must apply the latest Scheduled Maintenance Update, otherwise the NCP server can fail.
|
IMPORTANT:You must apply the latest Scheduled Maintenance Update, otherwise the NCP server can fail.
|
|
MariaDB |
|
|
For more information, see Filr System Requirements in the OpenText Filr 23.4: Installation, Deployment, and Upgrade Guide.
The following are the customer issues resolved in Filr 24.1:
After you sign out from Filr web client, you are redirected to the authorized web interface. It is possible to use the web interface even after successful sign out.
The following are the known issues in Filr 24.1:
The application appears to trust the user-supplied Host header. During the audit, it was found that the Host header is vulnerable to the user's input due to a lack of server-side input validation.
To avoid "Host Header Injection" the admin has to add host.header.validate=true in /opt/novell/filr/apache-tomcat/webapps/ssf/WEB-INF/classes/config/ssf-ext.properties and retsart filr.service
MS Outlook plugin login is not working when AAF is enabled.
Updating Filr and Search Appliances: Filr 24.1.1 is available as an online update to Filr 5.0 appliances or later. For more information, see Updating Filr through Online Update Channel.
Updating Content Editor Appliance: You must update the Content Editor appliance to version 24.1.1 For more information, see Applying Online Updates.
Updating PostgreSQL Appliance: You must update the PostgreSQL appliance to 23.4.1, see Applying Online Updates.
Copyright 2023-2024 Open Text
The only warranties for products and services of Open Text and its affiliates and licensors (“Open Text”) are as may be set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Open Text shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.