You're viewing Apigee Edge documentation.
View Apigee X documentation.
On September 23, 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
- Update the
sudo /opt/apigee/apigee-service/bin/apigee-service apigee-lib 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
/opt/apigee/apigee-service/bin/apigee-service apigee-adminapi update
/opt/apigee/apigee-service/bin/apigee-service apigee-machinekey update
/opt/apigee/apigee-service/bin/apigee-service apigee-configutil update
- Update all Cassandra nodes:
/opt/apigee/apigee-setup/bin/update.sh -c cs -f configFile
configFilespecifies the configuration file that you used to install Apigee Edge for Private Cloud. For example,
- 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.shscript for SSO on all nodes:
/opt/apigee/apigee-setup/bin/update.sh -c sso -f configFile
- Execute the update.sh script 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
- If you are using Apigee mTLS, follow the procedure described in Upgrade Apigee mTLS. For more information, see Introduction to Apigee mTLS.
Changes to supported software
There are no changes to the 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:
New wrapper around the nodetool repair tool
The wrapper does a sanity check on disk space (where Cassandra is mounted) before running the nodetool repair. The wrapper also supports JMX authentication and SSL over JMX related configurations.
Added support in the LDAP policy for dynamic string substitution for the <BaseDN> element.
The LDAP policy's
specifies the base level of LDAP under which all of your data exists.
In this release, we have added a
ref attribute to the element, which you can
use to specify a flow variable containing the
<BaseDN> value, such as
ref takes precedence over an explicit BaseDN value. If you specify both
ref and value,
ref has priority. If
ref does not resolve at runtime, value is used.
This section lists the Private Cloud bugs that were fixed in this release.
Fixed inconsistent jQuery script path in classic UI
Enhanced logging for UI was failing due to a misconfiguration of the
404 error while navigating to a developer from the developer apps pageThis has been fixed.
Companies were not appearing in the Edge UIThis has been fixed.
Self-signed certs trust issues in the Edge UIThis has been fixed.
This has been fixed.
There was a minor bug in the way data center names are sorted in Cassandra setup scripts.This has been fixed.
Apigee SSO was incorrectly returning stack traces in responses.This has been fixed. Note that the stack traces are still logged.
apigee-validate was failing with obscure messageThis has been fixed. Error logging for apigee-validate script has been improved.
syslog messages were incorrectly being droppedThis has been fixed.
Removed legacy keys from Gateway & Machinekey components
A failure in the permissions API was causing compatibility issues between the Edge UI and GatewayThis issue, which occurred when external LDAP authentication was enabled, has been fixed.
Removed trailing and leading spaces from all the HTTP request and response limit properties
Removed some unused configurations from Gateway components
Mint Management Server needs to be updated when Postgres failover is performedAn enhanced script was created to change Postgres connection details for Mint Management Server. See Handling a PostgresSQL database failover.
A large SSL handshake message was causing issues in Java 1.8.0_3XXThis has been fixed.
The ip command was not prefixed with the absolute pathThis has been fixed. Apigee scripts now fully qualify path of the commands.
Management update was failing when Cassandra JMX Authentication or SSL was enabledAdded feature to provide Cassandra JMX authentication and SSL configurations when running setup or update on Management server.
Edge UI Analytics dashboards were not able to fetch dataFixed a bug in which Analytics queries were failing for environments with a period in their name.
Reserved keywords AND/OR within text of dimensions were causing Analytics reports to fail.This has been fixed.
Extra whitespace in IP address list of
Java Management Extensions (JMX) is no longer enabled by default for the Apigee SSO module.
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.
Passwords were being logged in Edge for Private Cloud, due to normal logging of configuration file delta changes. You can prevent logging of configuration changes as follows:
|N/A||Improved security of passwords and related data stored in the platform.|
|CVE-2015-9251||Cross-site Scripting (XSS) is fixed when a cross-domain Ajax request is performed without the dataType option in jQuery.|
|N/A||Added additional protections against SAML assertion replay attacks.|
See Known issues with Edge for Private Cloud for a complete list of known issues.