Content Gateway 7.7 Release
New Features
Enhanced Azure support for Hybrid Cloud repatriation.
Improved audit log for multi-deletes and internal request handling.
S3 updates to signature handling, date formatting, and object locking.
Upgrade Impacts
To upgrade from a version of Gateway 6, see Upgrading Gateway. If you are migrating from Elasticsearch 2.3.3 and Gateway 5, see Upgrading from Gateway 5.x.
Be sure to address the upgrade impacts for this and each prior version since the one you are currently running:
Impacts for 7.7
Version Requirements
Swarm Storage 12.0.1 or higher
Elasticsearch 7.5.2
Content UI 7.4
See 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 is not compatible with Linux PAM modules that depend upon interactive validation operations such as OTP or biometric scanners.
See Content Gateway 6 Release Notes 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.