You're viewing Apigee Edge documentation.
View Apigee X documentation.
On February, 16, 2022, we released a new version of Apigee Edge for Private Cloud.
Note: This version will be supported until February 16, 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.
- 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
/opt/apigee/apigee-service/bin/apigee-service apigee-machinekey update
- On all Edge nodes, execute the
update.shscript for the edge process:
/opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
- On all UI nodes, execute the
update.shscript for the UI:
/opt/apigee/apigee-setup/bin/update.sh -c ui -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
- On all Apigee Developer Services portal nodes, update the devportal process by executing the following command:
/opt/apigee/apigee-setup/bin/update.sh -c dp -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
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.
Setting mail.smtp.ssl.protocols to an empty string caused SMTP emails to failThis has been fixed.
In the GenerateJWT policy, when specifying jwk as an additional header claim, the policy did not correctly handle the payloadThis has been fixed.
Analytics data was missing in PostgresSQL after an update to version 4.51.00This has been fixed.
When a forward proxy was used between a Message Processor and target server, analytics captured inconsistent target detailsTarget details in analytics were sometimes for the actual target and sometimes for the proxy. This behavior has been fixed, so target details captured in analytics are always those of the actual target.
Drupal-related warning messages were based on Drupal 8 instead of Drupal 9This has been fixed.
Some user actions, such as getting the version of
Access control policy reported errors when x-forwarded-for headers contained ip:port formatThis has been fixed.
Permissions containing both a wildcard (*) and special character (such as a comma) were not working as expectedThis has been fixed.
|215555851, 210780867, 217323200||
Apache Log4j 2.17.1 is now shipped in the thirdparty library of ApigeeThe
An issue with the Korean language input for the Edge Proxy Editor has been fixed
The Edge UI failed to open due to an empty cookie set in the headerThis has been fixed by deleting the empty cookie.
Bash scripts were returning undesired warning messagesThis has been fixed by replacing
Fixed an error when
Unwanted rotation and logs were being printed with TIME_SIZE rotation policyThis has been fixed.
The behavior of MP has changed: it will now reuse existing target IPs once if DNS resolution fails during DNS cache refresh
See Known issues with Edge for Private Cloud for a complete list of known issues.