Changes

• Fixed slow LDAP/Active Directory connections. The default values for the new "ldap" IDSYS fields "connectTimeout" and "readTimeout" are 5000 (milliseconds). Remove the /usr/lib/jvm/jre-1.8.0/lib/jndi.properties files that were created to fix the problem with an older release. (CLOUD-3632)

• Gateway was waiting the default 3 seconds for the 100-continue response for writes to storage nodes. Now [storage_cluster] continueWaitTimeout (default 30 seconds) is used. Error logging is also improved. (CLOUD-3579)

• The new [metrics] metricsHost configuration allows port 9100 to bind to a specific Gateway server IP, such as a private IP that Prometheus can reach, instead of all IP addresses. (CLOUD-3573)

• Improved error logging when [storage_cluster] managementPassword is not set or incorrect. (CLOUD-3514)

• Fixed the incorrect permissions on the /etc/caringo/cloudgateway/examples directory so that the files inside can be accessed without having to change the permissions manually. (CLOUD-3777)

• Overlapping configuration items [folder_listings]enhancedListingConsistency and [s3]enhancedListingConsistency are consolidated. Use only [s3]enhancedListingConsistency. Both configuration items are still supported, but warnings may be logged if [folder_listings]enhancedListingConsistency is used. The configuration item [folder_listings]enhancedListingConsistency will be removed in a future release. (CLOUD-3758)

• For easy troubleshooting, the Gateway client request ID is propagated to Swarm Storage during object locking operations. (CLOUD-3742)

• A PUT object?retention request would return a 500 Internal Error if the object did not exist. It now gives the right 404 NoSuchKey or NoSuchVersion. (CLOUD-3817)

• Before Content Gateway 7.10.6, S3 listings with object names that used some Unicode 2.0 characters were in the wrong order. S3 listings are now organized as UTF-8, just like AWS S3. (CLOUD-3807)

Upgrade Impacts

See Upgrading Gateway, to upgrade from a version of Gateway 6 or 7. See Upgrading from Gateway 5.x, 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:

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 on 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 Release Notes for known issues from prior releases that are still applicable, apart from those appearing above as fixed.