You're viewing Apigee Edge documentation.
Go to the Apigee X documentation. info
On May 26, 2022, we released a new version of Apigee Edge for Private Cloud.
Note: This version will be supported until May 26, 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
- Execute the update.sh script for SSO on all nodes:
/opt/apigee/apigee-setup/bin/update.sh -c sso -f configFile
- On all UI nodes, execute the update.sh script 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
- 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 related to YAML processing has been fixed.
|The Apigee Edge UI has been audited and updated based on the latest Content Security Policy standards.
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.
In the Audits API, a few records were missing when
Installing the New Edge UI was returning the error "Authentication failed for client ssoadmin" in setup-root.logInstallation has been updated to support HTTP/2, which fixed the issue.
LDAP was not working with
The Edge UI only supported usernames in email formatA config property has been added to allow non-email usernames.
Installing SSO was returning uninformative error messages when curl responses were non-200This has been fixed.
Using a service callout twice in a proxy was appending URL path to itself during runtimeThis has been fixed.
Mint has been enhanced so that Transaction Success Criteria based on txnProviderStatus can be evaluated on Message Processors and transactions dropped if the criteria fails
For Apigee SSO, there were no configurable properties for cipher suitesThis has been fixed.
An error message for creating aliases was not informativeChanged error message for Invalid RSA key from "Failed to load PKCS File :Failed to convert pem to der" to "Failed to load PKCS File :Invalid RSA key".
A Base64 decode exception was occurring for apps whose secrets had non-ASCII charactersThis has been fixed.
This has been fixed.
Message processors were not reading all properties set on Analytics groupsThis has been fixed.
See Known issues with Edge for Private Cloud for a complete list of known issues.