You're viewing Apigee Edge documentation.
Go to the Apigee X documentation. info
On August 18, 2021, we released a new version of Apigee Edge for Private Cloud.
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.50.00
curl https://software.apigee.com/bootstrap_4.50.00.sh -o /tmp/bootstrap_4.50.00.sh
- Install the Edge 4.50.00
apigee-serviceutility and dependencies:
sudo bash /tmp/bootstrap_4.50.00.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:
- Update the
apigee-validateutility on the Management Server:
/opt/apigee/apigee-service/bin/apigee-service apigee-validate update
- Update the
apigee-provisionutility on the Management Server:
/opt/apigee/apigee-service/bin/apigee-service apigee-provision update
- Update all Cassandra nodes:
/opt/apigee/apigee-setup/bin/update.sh -c cs -f configFile
where configFile specifies the configuration file that you used to install Apigee Edge for Private Cloud. For example,
- Update Postgres nodes (master and standby):
/opt/apigee/apigee-setup/bin/update.sh -c ps -f /opt/silent.conf
- On all Edge nodes, execute the
update.shscript for the
/opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
- Execute the
update.shscript for SSO on all nodes:
/opt/apigee/apigee-setup/bin/update.sh -c sso -f configFile
- Execute the
update.shscript for the UI on all nodes:
/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
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.
This release introduces the following new features:
A new pop-up window warns you of end of life (EOL) dates for Edge for Private Cloud
Edge for Private Cloud customers will start seeing warning messages displayed six month prior to the installed version's EOL date. The EOL message will be shown once per browser session: if you close the tab or browser, the session will be lost. If you then re-open Apigee in a browser, the message will be displayed again.
New option to log out users when their passwords are changed
A new flag was added to
apigee.feature.clearSessionOnPasswordUpdate, which lets
you configure whether users are logged out after you change their password.
The default is that users are not logged off.
New flag to set TLS version for SMTP
A new flag has been added to
mail.smtp.ssl.protocols, which specifies the SSL protocol
that are enabled for SMTP connections. This feature lets you configure SSL protocols based on
your security requirements.
Configure forward proxy.
The following flags have been added, which let you configure a forward proxy:
By default the values of the flags are empty.
Enhanced pg-data-purge script to purge parent fact tables from analytics
To run the script, enter the following command:
/opt/apigee/apigee-service/bin/apigee-service apigee-postgresql pg-data-purge org_name env_name number_of_days_to_retain [Delete-from-parent-fact - N/Y] [Confirm-delete-from-parent-fact - N/Y]
The script has the following options:
Delete-from-parent-factDefault : No. Will also delete data older than retention days from parent fact table.
Confirm-delete-from-parent-fact. Default: No. If No, the script will prompt for confirmation before deleting data from parent fact. Set to Yes if the purge script is automated.
Option to change the user label in the login page
A new flag,
apigee.feature.customLoginUserLabel allows you to configure the user label
in the login page based on their preference. The default is Email address.
This section lists the Private Cloud bugs that were fixed in this release.
Deleting an API product from an API product bundle wasn't working.This has been fixed.
Password complexity requirements were not being enforced at installationThis has been fixed.
Customers were able to make GET requests to dailysummaryreports without any CSRF protectionThis has been fixed.
HMAC policy did not appear in the list of policies in the UIThis has been fixed.
404 redirect issue in the Developers tab in the UI.Customers were not able to edit/delete or perform any other operation in the Developers tab in the UI because the developer's email had special characters in it. This has been fixed
Monetization installation was failing on a second Management serverFixed some potential issues due to race condition during installation of Mint Management Server
AND/OR reserved keywords within text of dimensions were causing analytics reports to failThis has been fixed.
Postgres restore failed if Apigee databases were missingWe have improved error logging in Postgres restore script.
Upgrades were failing for apigee-ldapThis has been fixed.
Customer could not add new Cassandra nodesCassandra setup will fail with improved error message if an incorrect
Management Server was not coming up if Cassandra nodes in another data center were downThe enable Cassandra authentication script has been enhanced to handle this.
Management server was not connecting to a local Postgres region.Made improvements to the Management Server algorithm for choosing best Postgres to connect to for analytics queries.
Analytics API filtering issueThis has been fixed.
Permission restrictions were not working for Audits resourceThis has been fixed.
Misformatted numbers within a component's
Fixed issue in datastore registrations during Management Server installation/updates when region names not in the dc-x format are used.See Edge Configuration File Reference.
Mass rollout of API Proxies was slowThis has been fixed.
Improved Message Processor logs to better capture error states
Added a Router level configuration to disable Virtual Host listen options on standard ports 80 & 443.
A 403 error was returned when creating shared flowThe error occurred because an undefined value was being passed to the API. This has been fixed.
The ServiceCallout policy was splitting the header values and sending the headers with same key
and different values to the backend when the
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.
Highcharts Vulnerability issues in Edge UI (Classic)
Cross-Site Scripting (XSS) vulnerability in jQuery
A vulnerability in jquery which reported cross-site scripting (XSS) was fixed.
Vulnerability in Tomcat servlet.
Existing Tomcat servlet 8.0.53 had a security vulnerability. Upgrading Tomcat servlet to 8.5.34 fixes this vulnerability.
See Known issues with Edge for Private Cloud for a complete list of known issues.