| Table of Contents | ||
|---|---|---|
|
Changes
Changed the message about SOSAPI being enabled or disabled to print only once during Gateway startup. (CLOUD-3780)
Preserved object locking headers for greater S3 compatibility when an object lock expires. (CLOUD-3767)
Fixed bug in which deleted folders would still be included in non-versioned S3 delimiter listings when [folder_listings] usePaths=true. (CLOUD-3772)<Feature 1>
<Feature 2>
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 | ||
|---|---|---|
| ||
Impacts for 7.10.45
|
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
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)
...