- Edge for Private Cloud release notes

You're viewing Apigee Edge documentation.
Go to the Apigee X documentation.

On June 27, 2022, we released a new version of Apigee Edge for Private Cloud.

Note: This version will be supported until June 27, 2023.

Update procedure

Updating this release will update the components in the following list of RPMs:

  • edge-gateway-4.51.00-0.0.60169.noarch.rpm
  • edge-management-server-4.51.00-0.0.60169.noarch.rpm
  • edge-message-processor-4.51.00-0.0.60169.noarch.rpm
  • edge-postgres-server-4.51.00-0.0.60169.noarch.rpm
  • edge-qpid-server-4.51.00-0.0.60169.noarch.rpm
  • edge-router-4.51.00-0.0.60169.noarch.rpm
  • apigee-mirror-4.51.00-0.0.1028.noarch.rpm
  • apigee-configutil-4.51.00-0.0.616.noarch.rpm
  • apigee-provision-4.51.00-0.0.619.noarch.rpm
  • apigee-adminapi-4.51.00-0.0.609.noarch.rpm
  • edge-analytics-4.51.00-0.0.40065.noarch.rpm
  • apigee-cassandra-2.1.22-0.0.2530.noarch.rpm
  • apigee-cassandra-client-2.1.22-0.0.2515.noarch.rpm

You can check the RPM versions you currently have installed, to see if they need to be updated, by entering:

apigee-all version

To update your installation, perform the following procedure on the Edge nodes:

  1. On all Edge nodes:

    1. Clean the Yum repos:
      sudo yum clean all
    2. Download the latest Edge 4.51.00 bootstrap_4.51.00.sh file to /tmp/bootstrap_4.51.00.sh:
      curl https://software.apigee.com/bootstrap_4.51.00.sh -o /tmp/bootstrap_4.51.00.sh
    3. Install the Edge 4.51.00 apigee-service utility 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.

    4. Use the source command to execute the apigee-service.sh script:
      source /etc/profile.d/apigee-service.sh
  2. Update the apigee-provision utility on the Management Server:
    /opt/apigee/apigee-service/bin/apigee-service apigee-provision update
  3. Update the apigee-adminapi utility:
    /opt/apigee/apigee-service/bin/apigee-service apigee-adminapi update
  4. Update apigee-config util:
    /opt/apigee/apigee-service/bin/apigee-service apigee-configutil update
  5. Update all Cassandra nodes:
    /opt/apigee/apigee-setup/bin/update.sh -c cs -f configFile
  6. On all Edge nodes, execute the update.sh script for the edge process:
    /opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile

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.

Issue ID Description
230857841 A security issue related to CVE-2022-22950 has been fixed by upgrading spring version used in analytics to 5.3.20.
234175444 A security issue related to CVE-2019-2708 has been fixed by updating libdb artifacts for RHEL-8 (in apigee-thirdparty) to 5.3.28-42.

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.

New features

There are no new features in this release.

Bug fixes

This section lists the Private Cloud bugs that were fixed in this release.

Issue ID Description

Upgraded spring jars to 5.3.20 to address vulnerabilities.


Added property conf_allowed_extensions to control or whitelist files to check and print delta log.

This property contains the list of file extensions to print delta log. By default, the following file types/extensions are allowed to print delta log: sh, xml, properties, conf, key, config, json, yaml, yml, policy, toml.

Added new utilities in apigee-adminapi to add and remove AX group properties. Modified apigee-provision so onboarding new AX groups have consumer-type property set appropriately.


Added legacy option to nodetool to maintain compatibility with latest version of Java 8


apigee-mirror was creating directories with incorrect permissions, causing errors when the synchronized repo was served with nginx.

This has been fixed

Improved deployment performance of management server, reducing number of hits to Cassandra.

This improves performance for deployment operations in environments with a large number of deployed proxies

Edge supported ciphers provides limited options and no ability to limit ciphers outside of a hard coded list

This has been fixed. While configuring TLS for management API, ciphers which are blacklisted and whitelisted are no longer filtered by ciphers listed by Apigee. Instead, the lists specified in these configs are directly applied. You can revert this to the prior behavior of Apigee filtered cipher list by setting config conf_webserver.ssl.apigee.cipher.suites.enforce=true in management server.

Known issues

See Known issues with Edge for Private Cloud for a complete list of known issues.