You're viewing Apigee Edge documentation.
View Apigee X documentation.
On April 19, 2023, we released a new version of Apigee Edge for Private Cloud.
Note: This version will be supported until April 19, 2024.
Updating this release will update the components in the following list of RPMs:
- apigee-sso-4.52.00-0.0 Are there .21245.noarch.rpm
You can check the RPM versions you currently have installed, to see if they need to be updated, by entering:
To update your installation, perform the following procedure on the Edge nodes:
On all Edge nodes:
- Clean the Yum repos:
sudo yum clean all
- Download the latest Edge 4.52.00
curl https://software.apigee.com/bootstrap_4.52.00.sh -o /tmp/bootstrap_4.52.00.sh
- Install the Edge 4.52.00
apigee-serviceutility and dependencies:
sudo bash /tmp/bootstrap_4.52.00.sh apigeeuser=uName apigeepassword=pWord
where uName and pWord are the username and password you received from Apigee. If you omit pWord, you will be prompted to enter it.
- Update the
sudo /opt/apigee/apigee-service/bin/apigee-service apigee-setup update
- Use the
sourcecommand to execute the apigee-service.sh script:
- Clean the Yum repos:
- Update the
apigee-provisionutility on the Management Server:
/opt/apigee/apigee-service/bin/apigee-service apigee-provision update
- Update Postgres nodes (master and standby):
/opt/apigee/apigee-setup/bin/update.sh -c ps -f configFile
- On all Edge nodes, execute the
update.shscript for the edge process:
/opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
- Execute the update.sh script for SSO on all nodes:
/opt/apigee/apigee-setup/bin/update.sh -c sso -f configFile
Security issues fixed
No security issues were fixed in this release.
Changes to supported software
There are no changes to supported software in this release.
Deprecations and retirements
There are no new deprecations or retirements in this release.
There are no new features in this release.
This section lists the Private Cloud bugs that were fixed in this release.
OASValidation policy was consuming too much heap memory allocationThis has been fixed.
Added more checks to prevent smuggling a GET request inside another POST request.
Modified audit data of developer app related APIs.The consumer secret is now consistently logged in a masked manner. You can set configuration
Apigee-provision was creating empty lines while adding cron entries.This has been fixed.
Enhanced rebuildindex so non ID based index APIs function appropriately when there are more than 10k apps per entity.
Fixed a regression in MGMT API which was causing incorrect content types to be returned when accept header in requests had a wildcard.This was also causing failures while downloading trace file in the UI.
For security reasons, external entities are now not allowed to be loaded by default in XSLTransform Policy.You can override this by setting the flag
Modified audit data of developer app related APIs.The consumer secret is now consistently logged in a masked manner. You can the configuration
Fixed a bug introduced in OPDK v4.52.00 which was causing certain API and Accept header combinations to fail.
Apigee was not populating some target variables, such as URL and Host, when a target server was used and a target error was encountered.This has been resolved.
Cassandra and cassandra-client were not upgrading to latest versions when upgrading from Edge for Private Cloud v4.51 to v4.52.This has been fixed
Updated Postgres driver version in Gateway to 42.5.4.
Updated Postgres driver version in Monetization to 42.5.4.
Improved handling of new lines in condition statements of proxies.
Added a column in Analytics Fact Tables which captures the top three polices that took the longest to run.
Removed unexpected parameter
There was a problem upgrading from Edge for Private Cloud 4.50 to 4.52.This has been fixed.
Apigee-postgresql is having issues with upgrading from version 4.50 or 4.51 to version 4.52. The issues mainly occur when the number of child fact tables is greater than 500. See Postgresql upgrade when updating to version 4.52 in Known issues with Edge for Private Cloud for a workaround.
See Known issues with Edge for Private Cloud for a complete list of known issues.