You're viewing Apigee Edge documentation.
View Apigee X documentation.
On April 28, 2022, we released a new version of Apigee Edge for Private Cloud.
Note: This version will be supported until April 28, 2023.
Updating this release will update the components in the following list of RPMs:
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.51.00
curl https://software.apigee.com/bootstrap_4.51.00.sh -o /tmp/bootstrap_4.51.00.sh
- Install the Edge 4.51.00
apigee-serviceutility and dependencies:
sudo bash /tmp/bootstrap_4.51.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.
- Use the
sourcecommand to execute the apigee-service.sh script:
- Clean the Yum repos:
- On all Edge nodes, execute the
update.shscript for the edge process:
/opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
- If you are using the New Edge experience, execute the following command:
/opt/apigee/apigee-setup/bin/update.sh -c ue -f configFile
- If you are using Apigee mTLS, follow the procedure described in Upgrade Apigee mTLS. For more information, see Introduction to Apigee mTLS.
Security issues fixed
The following is a list of known security issues that have been fixed in this release. To avoid these issues, install the latest version of Edge Private Cloud.
|A security issue has been fixed for non-generic responses that could have leaked configuration data.|
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.
Requests to Python callout in sharedflow were failing due to a
Deploying a proxy was taking too longThis has been fixed.
OASValidation was returning 500 status when validation failedOASValidation now returns the correct 400 status.
Empty JSON parameter was causing a
Added proper log entries for statistics collector custom variables population in Zookeeper
SSO Error handling was not returning correct error messagesThis has been fixed.
Proxy revision was returning a 400 error when used as a target with
VerifyJWT policy was not allowing the
DeleteOAuthV2Info policy was failing to remove the access tokenThis has been fixed.
Converted monit restart command to a configuration so it can be overridden by using configuration
Audited and updated system for the Apigee Edge UI based on the latest Content Security Policy standards
The apigee-service RPM no longer depends on edge-gateway
apigee-mtls-consul is now compatible with Edwards Curve 25519 encryption algorithm
JWT policy was converting int datatype to doubleThis has been fixed.
Upgraded third party library xmlbeans-2.4.0 to xmlbeans-3.1.0
See Known issues with Edge for Private Cloud for a complete list of known issues.