| Table of Contents | ||
|---|---|---|
|
...
- Adds management features for long-term SCSP clients using unnamed objects outside of a domain, automatically organizing them into a virtual System domain. Replaces the need for SCSPproxy and unifies metering and access management across all storage domains including the System domain. (CLOUD-3285)
Fixed:
- Folder listings in Content Portal are no longer capped at 2000 entries. (CLOUD-3274)
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.
...
| Excerpt |
|---|
Impacts for 7.3
|
| 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.
These are known issues in this release:
- The cloudgateway_audit.log shows a false 500 http response for SCSP (format=json) listing requests. This can be ignored; the client will receive a 200 OK with the correct list results. (CLOUD-3201)
See Content Gateway 6.4 Release for known issues from prior releases that are still applicable, apart from those appearing above as Fixed.