Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
maxLevel2

Changes

  • Changed the message about SOSAPI being enabled or disabled to print only once during Gateway startupImproved S3 listing performance when no prefix is specified. (CLOUD-3780)Preserved object locking headers for greater S3 compatibility when an object lock expires3788)

  • Buckets that contain only version delete markers cannot be deleted, to match AWS' behavior. (CLOUD-3767)Fixed bug in which deleted folders would still be included in non-versioned S3 delimiter listings when [folder_listings] usePaths=true3797)

  • Hybrid Cloud copies to S3 now preserve custom metadata. (CLOUD-37723799)

Upgrade Impacts

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

...

Excerpt
nameContent Gateway 7.10.3 5 Release

Impacts for 7.10.

4

5

  • Version Requirements

    • Swarm Storage 14.1.0 or higher

    • Elasticsearch 7.5.2

    • Content UI 7.9.0

Insert excerpt
Content Gateway 7.10.4 Release
Content Gateway 7.10.4 Release
nopaneltrue

Insert excerpt
public:Content Gateway 7.10.3 Releasepublic:
Content Gateway 7.10.3 Release
nameContent Gateway 7.10.3 Release
nopaneltrue

Insert excerpt
public:Content Gateway 7.10.2 Releasepublic:
Content Gateway 7.10.2 Release
nopaneltrue

Insert excerpt
public:Content Gateway 7.10.1 Releasepublic:
Content Gateway 7.10.1 Release
nameContent Gateway 7.10.1 Release
nopaneltrue

Insert excerpt
public:Content Gateway 7.10 Releasepublic:
Content Gateway 7.10 Release
nameContent Gateway 7.10 Release
nopaneltrue

Insert excerpt
public:Content Gateway 7.9 Releasepublic:
Content Gateway 7.9 Release
nameContent Gateway 7.9 Release
nopaneltrue

Insert excerpt
public:Content Gateway 7.8 Releasepublic:
Content Gateway 7.8 Release
nameContent Gateway 7.8 Release
nopaneltrue

Insert excerpt
public:Content Gateway 7.5 Releasepublic:
Content Gateway 7.5 Release
nopaneltrue

Insert excerpt
public:Content Gateway 7.4 Releasepublic:
Content Gateway 7.4 Release
nopaneltrue

Insert excerpt
public:Content Gateway 7.3 Releasepublic:
Content Gateway 7.3 Release
nopaneltrue

Insert excerpt
public:Content Gateway 7.2 Releasepublic:
Content Gateway 7.2 Release
nopaneltrue

Insert excerpt
public:Content Gateway 7.1 Releasepublic:
Content Gateway 7.1 Release
nopaneltrue

Insert excerpt
public:Content Gateway 7.0 Releasepublic:
Content Gateway 7.0 Release
nopaneltrue

See See Content Gateway 6 .4 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.

  • Gateway SCSP and Portal do not allow a bucket with object locking to be deleted, even if it is empty. It must be deleted by an S3 client e.g. using "rclone purge" to delete all objects and versions. (CLOUD-3516)

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

...