You're viewing Apigee Edge documentation.
Go to the Apigee X documentation. info
On October 28, 2020, we released a new version of Apigee Edge for Private Cloud.
Updating this release will update the components in the following list of RPMs:
Note: The RPM of apigee-drupal-contrib-4.19.06 has been updated to release 0.0.303. This RPM is identical to release 0.0.302 and was updated to resolve certain Drupal dependencies. If you patch from earlier versions, the RPM version might not change.
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.19.06
curl https://software.apigee.com/bootstrap_4.19.06.sh -o /tmp/bootstrap_4.19.06.sh
- Install the Edge 4.19.06
apigee-serviceutility and dependencies:
sudo bash /tmp/bootstrap_4.19.06.sh apigeeuser=uName apigeepassword=pWord
Where uName: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
- Clean the Yum repos:
- On all Edge nodes, execute the
update.shscript for the
edgeprocess. To do this, execute the following command on each node:
/opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
- If you are using the New Edge experience, execute the folowing command on all
New Edge UI nodes:
/opt/apigee/apigee-setup/bin/update.sh -c ue -f configFile
- On all Apigee Developer Services portal nodes, update the
devportalprocess by executing the following command:
/opt/apigee/apigee-setup/bin/update.sh -c dp -f configFile
Deprecations and retirements
No new deprecations or retirements.
No new features.
The following table lists the bugs fixed in this release:
Apigee SSO was not verifying a digital signature, which caused a potential security issue.
Dependencies defined within Gateway were preventing the latest libraries from being utilized.
SSO config file did not have a setting to specify a home redirect from SSO to the Edge UI.
As a result, logging in through SSO (port 9099) was failing with the message "Where to?".
This has been fixed. You can now set a home redirect from SSO to the Edge UI by the following steps:
apigee-service apigee-sso restart
Installing the Edge UI was causing a segmentation fault.
The error message was
Executable permissions were missing for "group" and "world" on some directories.
As a result, running the command
Unable to get UI trace for transactions with large values assigned to flow variable.
A Dev Portal 403 Access denied problem was fixed for CSS/JS URLs in all modules
added to the
For a list of known issues with Edge Private Cloud, see Known issues with Edge Private Cloud.