Changes

• Fixed a bug that could cause errors in the log under extremely high concurrent listing requests. (CLOUD-4031)

• Improved error messages when the Elasticsearch index name is incorrectly configured. (CLOUD-4030)

• Introduced a reduced socket timeout to avoid Gateway "hanging" under heavy concurrent load. (CLOUD-4001)

• Fixed rare "Index 0 out of bounds for length 0" error when using SAML and downloading an object. (CLOUD-3948)

• Fixed a bug that could cause failure of S3 multi-delete requests for objects in a version-enabled bucket, which were written before versioning was enabled. (CLOUD-3856)

• Fixed a bug that caused an incorrect audit record to be written with a 500 HTTP response code instead of the actual 200 when listing via SCSP. (CLOUD-3201)

• Fixed a bug that caused attempts to abort a multipart upload into an object-locked bucket with governance/compliance mode and default retention to fail with a 403 error. (CLOUD-4053)

Upgrade Impacts

See Upgrading Gateway to upgrade from a version of Gateway 6 or 7. See Upgrading from Gateway 5.x, if migrating from Elasticsearch 2.3.3 and Gateway 5.

Starting with Gateway 7.8, Elasticsearch 6.8.6 is no longer supported. Remain on Gateway 7.7 until the rolling upgrade from Elasticsearch 6.8.6 to 7.5.2 is completed.

Address the upgrade impacts for this and each prior version since the currently running version:

See Content Gateway 7 Release Notes and for impacts from prior releases.

Watch Items and Issues

These are known operational limitations that exist for Gateway.

• When using the default RHEL/CentOS configuration of IPTABLES, traffic to the Gateway will be blocked unless action is taken to disable IPTABLES or to enable inbound traffic to the front-end protocol port(s).

• Gateway is incompatible with Linux PAM modules that depend on interactive validation operations such as OTP or biometric scanners.

• Gateway 8.0.4 must be restarted after creating a Search Feed to avoid the error: “ResourceUnavailableException: Application resource 'elasticsearch-storage_cluster' is unavailable”. This will be fixed in an upcoming release. (CLOUD-4003)

• Gateway logs display a warning "Elasticsearch built-in security features are not enabled. Without authentication, your cluster could be accessible to anyone". This is harmless and can be avoided by adding "xpack.security.enabled: false" to each Elasticsearch node's /etc/elasticsearch/elasticsearch.yml and doing a rolling restart . (SWAR-10260)

See and for known issues from prior releases that are still applicable, apart from those appearing above as fixed.