Changes

• The scsp.allowSwarmAdminIP setting now also accepts CIDR style ranges like "172.30.128/17" and "172.30.128.0/17" in addition to previously accepted values of "all" or a list of IP addresses. (CLOUD-1191)

• Appropriate warnings are logged on startup if the Content Gateway is configured to run in legacy mode, but is also configured to enable services that are not supported in legacy mode (S3, etc.). (CLOUD-3291)

• Improved error handling of a rare error (500 InternalError, ClientProtocolException) by logging details and retrying. If the retry causes a problem, set debug.retryClientProtocolException = 0. (CLOUD-3321)

• The managementPassword setting is no longer optional and is now required. Always verify managementUser and managementPassword configured. (CLOUD-2617)

Fixed

Resolved issues with replication feeds targeting a Content Gateway version 7.1, 7.2, 7.3, or 7.4. Upgrade to Swarm 12.1 and Gateway 7.5 where this is now fixed. (CLOUD-3323)

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.

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 is 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.