Changes
Fixed S3 authentication for requests that have a query argument including characters (an asterisk (*) or 32-bit Unicode characters). (CLOUD-3592)
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 |
---|
name | Content Gateway 7.10.1 Release |
---|
|
Impacts for 7.10.1 |
...
Insert excerpt |
---|
| Content Gateway 7.8 Release |
---|
| Content Gateway 7.8 Release |
---|
name | Content Gateway 7.8 Release |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| Content Gateway 7.7 Release |
---|
| Content Gateway 7.7 Release |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| Content Gateway 7.6 Release |
---|
| Content Gateway 7.6 Release |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| Content Gateway 7.5 Release |
---|
| Content Gateway 7.5 Release |
---|
nopanel | true |
---|
|
...
Insert excerpt |
---|
| Content Gateway 7.0 Release |
---|
| Content Gateway 7.0 Release |
---|
nopanel | true |
---|
|
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.
See Content Gateway 6 .4 Release Notes for known issues from prior releases that are still applicable, apart from those appearing above as Fixed.