• Changes

• Upgrade Impacts

  • Impacts for 8.2.1

• Watch Items and Issues

Changes

• Moved PAM authentication out of process to prevent authentication failures under load, requiring a Gateway restart. (CLOUD-3931)

• Listing Cache now supports custom delimiters; only the standard delimiter (forward slash "/") reaps performance benefits from caching. (CLOUD-4036)

• Removed the default admin domain name from gateway.cfg; manual entry is now required. (CLOUD-4071)

• Removed internet access requirement for Swarm Lifecycle installation. (CLOUD-3661)

• Added trailing headers (chunked encoding) support with checksums (CRC32, CRC32C, SHA1, SHA256) in Gateway 8.2.1, but it does not return or persist them. (CLOUD-4120)

• Added %displayName% macro in quota mail templates to expand to the full tenant/domain.bucket name, now used in the default template. (CLOUD-4150)

• Upgrading with a customized logging.yaml causes extra log entries per request. To fix, update to the latest logging.yaml.rpmnew, merge customizations, and replace the old file. See also Gateway Logging | Upgrading logging.yaml to a Newer Version (CLOUD-4181)

Upgrade Impacts

See Upgrading Gateway to upgrade to an existing installation. See Upgrading from Gateway 5.x, if you are 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 Content Gateway 6 Release Notes 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 8.0.4 and later versions must be restarted after creating a Search Feed to avoid the error: “ResourceUnavailableException: Application resource 'elasticsearch-storage_cluster' is unavailable”. (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 Rolling Restart of Elasticsearch. (SWAR-10260)

• The video clipping feature does not work in Gateway v8.0. (CLOUD-4082)

• Gateway 8.1.0 may report an incorrect IsTruncated status in rare cases where ?max-keys=0. (CLOUD-4027)

See Content Gateway 7 Release Notes and Content Gateway 6 Release Notes for known issues from prior releases that are still applicable, apart from those appearing above as fixed.