You're viewing Apigee Edge documentation.
Go to the
Apigee X documentation. info
This section describes version 4.50.00 of the Edge for Private Cloud Feature Release.
Release summary
The following table summarizes the changes in this release:
| New Features | This release includes the following new features: ○ TLS connection information now available in API proxies○ Zookeeper upgrade ○ Availability of the Drupal 8 portal, and EOL of Drupal 7 For more information about each of these new features, see New features. |
| Backward Compatibility |
The following issues affecting backward compatibility were introduced in this version
of Apigee Edge for Private Cloud:
|
| Included Releases | Since the previous Edge for Private Cloud Feature Release, the following releases have occurred and are included in this release: |
| Retirements | None |
| Deprecations | With the release of 4.50.00:
Features deprecated in this release include:
For more detailed information about the deprecations including removal timelines, see Apigee deprecations and retirements. |
| Bug Fixes | This release includes the following bug fixes: ○ Message Processor fails to load environments when keystores are configured with similar names or aliases. (154428338)○ QPid dependency conflict while installing patch (152574421) ○ Cache memory limiter not respecting max L1 cache size (151449163) ○ Backup scripts failing (150710952) ○ QPid server sending extra log messages (148231209) ○ Backup of Postgresql not storing SSO information (147458330) ○ apigee-nginx version not upgraded. (146872858) ○ `Try the new UI` message no longer appearing (145419621) ○ Apigee SmartDocs API Vulnerability (145340106) ○ Postgres backup script fails (145254693) ○ Various security fixes (142150706) ○ High rate of Router to Message Processor timeouts (138107618) ○ SSO setup script failure (135616498) ○ JMX ports (132044907) ○ Intermittent 404s for runtime traffic due to race condition (130653816) ○ OpenLDAP corruption during upgrade (120799182) ○ DataAccessException in multiple data center configurations (76087166) ○ FormatMessage set to false in MessageLogging policy not working (68722102) For more information about each of these fixes, see Bug fixes. |
| Known Issues | This release includes the following known issues: ○ JWT validation fails (159788170)○ Mint rating servers memory leak (137865184) ○ apigee-monit not supported on Amazon Linux 1 (122370980)○ Message Processor backup not backing up the correct set of files (121095148) ○ Increased Cache miss ratio after upgrade (160109014) ○ HTTP 408 response for GET request with empty body and Content-Encoding: gzip. (159858015) For more information about each of these known issues, including workarounds, see Known issues. |
Upgrade paths
The following table shows the upgrade paths for this release:
| From 4.19.01 or 4.19.06 | Directly upgrade from 4.19.01/4.19.06 → 4.50.00 |
| From 4.18.05 | Directly upgrade from 4.18.05 → 4.50.00 |
New features
This section lists new features in this release. Additionally, this release includes all features in the Edge UI, Edge Management, and Portal releases listed in Included Releases.
In addition to the following enhancements, this release also contains multiple usability, performance, security, and stability enhancements.
TLS connection information now available in API proxies
During a request to an API proxy through a virtual host that supports TLS, Edge can capture information about the TLS connection. Your API proxy can now access that information through flow variables to perform additional analysis and validation. See Accessing TLS connection information in an API proxy for more.
Zookeeper upgrade
This release contains Zookeeper 3.4.14.
Availability of the Drupal 8 portal, and EOL of Drupal 7
Drupal 8 has succeeded Drupal 7 as the Apigee-recommended developer portal for Private Cloud. Because Drupal 7 itself will reach the end of its long term support in November, 2021, the Apigee modules for Drupal 7 will not be supported as of November, 2021. While still available, the install/upgrade scripts for Drupal 7 should no longer be used and will be removed in a future release.
To learn about the Drupal 8 modules that integrate with Apigee, see: Build your portal using Drupal 8.
Supported software
This release includes the following changes to supported software:
| Support Added | No Longer Supported |
|---|---|
|
This release adds support for the following platforms:
|
The following platforms are no longer supported with this release:
|
For a complete list of supported platforms, see Supported software and supported versions.
Bug fixes
This section lists the Private Cloud bugs that were fixed in this release. Additionally, this release includes all bug fixes in the Edge UI, Edge Management, and Portal releases shown in Included Releases.
| Issue ID | Description |
|---|---|
| 154428338 |
Message Processor fails to load environments when keystores are configured with similar names or aliases. We have fixed a regex lookup conflict when loading keystores that have similar naming convention. This was causing the Message Processor to fail to load environments associated to the keystore, or fail to start when multiple conflicting keystores were returned during the lookup. |
| 152574421 |
QPid dependency conflict while installing patch The correct version of QPid is now installed. |
| 151449163 |
Cache memory limiter not respecting max L1 cache size The Cache memory limiter now respects max L1 cache size. |
| 150710952 |
Backup scripts failing The backup procedure has been updated based on the updated backup scripts. |
| 148231209 |
QPid server sending extra log messages The QPid server no longer sends extra log messages. |
| 147458330 |
Backup of Postgresql not storing SSO information Postgresql backup now storing SSO information. |
| 146872858 |
apigee-nginx version not upgraded. apigee-nginx version now upgraded correctly. |
| 145419621 |
`Try the new UI` message no longer appearing The UI no longer displays the `Try the new UI` message. |
| 145340106 |
Apigee SmartDocs API Vulnerability Updated Apigee SmartDocs proxy to address security vulnerability. See the SmartDocs installation procedure for further information and required steps. |
| 145254693 |
Postgres backup script fails The Postgres backup script now works correctly. |
| 142150706 |
Various security fixes Fixes for security issues, including #111390246. |
| 138107618 |
High rate of Router to Message Processor timeouts This issue has been resolved. |
| 135616498 |
SSO setup script failure An issue was fixed where using file-scheme URLs caused SSO setup script failure. |
| 132044907 |
JMX ports JMX ports should not be open to external access, only to internal servers. |
| 130653816 |
Intermittent 404s for runtime traffic due to race condition Fixed a race condition during MP bootstrap which led to some proxies not being deployed correctly. |
| 120799182 |
OpenLDAP corruption during upgrade This issue has been resolved. |
| 76087166 |
DataAccessException in multiple data center configurations In multiple data center configurations, if one datastore becomes unavailable, you no longer see the DataAccessException error. |
| 68722102 |
FormatMessage set to false in MessageLogging policy not working You can now set FormatMessage to false in the MessageLogging policy. |
Known issues
The following table lists known issues in this release:
| Issue ID | Description |
|---|---|
| 159788170 |
JWT validation fails JWT validation fails for RSA keys smaller than 2048 bits. Workaround: Ensure that your keys are 2048 bits or larger. |
| 137865184 |
Mint rating servers memory leak When a new Qpid instance is registered in an mxgroup, the queues build without consumers, which results in the queue depth growing until it uses all available resources. Workaround: None. |
| 122370980 |
Workaround: None. |
| 121095148 |
Message Processor backup not backing up the correct set of files Workaround: Run the backup a second time and it should back up the correct set of files. |
| 160109014 |
Increased Cache miss ratio after upgrade After upgrade to release 4.50.00, proxies may exhibit an increased cache miss ratio. These misses may be accompanied by increased error messages in the MP logs similar to: InvalidClassException when fetching cps cache entry from second level - com.apigee.jsonparser.LinkedJSONObject; local class incompatible: stream classdesc serialVersionUID = -8575741446425131573, local class serialVersionUID = 752634431212433936. Considering it as cache miss. Workaround: None. The cache hit ratio is expected to stabilize over time. |
| 159858015 |
HTTP 408 response for GET request with empty body and Content-Encoding: gzip. An API client will receive a 408 Timeout response when it makes a GET request with the header Workaround: Omit the |
Next step
To get started with Edge for Private Cloud 4.50.00, use the following links:
- New installations:
- New installation overview
- Existing installations:
- Upgrade paths