Content Gateway 8.0.1 Release

Changes

  • RPMs now use SHA256 for the digest calculation to support secure RHEL installs. (CLOUD-3926)

  • Fixed bug that prevented deletes from propagating during replication. (CLOUD-3922)

  • Fixed the bug that could log sensitive information. (CLOUD-3917)

Upgrade Impacts

See https://perifery.atlassian.net/wiki/spaces/public/pages/2443817319 to upgrade from a version of Gateway 6 or 7. See https://perifery.atlassian.net/wiki/spaces/public/pages/2443817356, 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:

Impacts for 8.0.1

  • Version Requirements

    • Swarm Storage 14.1.0 or higher

    • Elasticsearch 7.5.2 or 7.17.9 (required with Swarm Storage 15.3 or higher)

    • Content UI 7.9.1

    • Storage UI 3.5.0

 

See https://perifery.atlassian.net/wiki/spaces/public/pages/3417342224 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 not compatible with Linux PAM modules that depend on interactive validation operations such as OTP or biometric scanners.

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

© DataCore Software Corporation. · https://www.datacore.com · All rights reserved.