- Edge for Private Cloud release notes

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

On February 13, 2024, we released a new version of Apigee Edge for Private Cloud.

Note: This version will be supported until February 13, 2025.

Update procedure

This section describes how to install this release if you are updating from the previous release of Edge for Private Cloud. If you need to update from an earlier release, see Applying multiple patch versions.

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

  • edge-gateway-4.52.00-0.0.60210.noarch.rpm
  • edge-management-server-4.52.00-0.0.60210.noarch.rpm
  • edge-message-processor-4.52.00-0.0.60210.noarch.rpm
  • edge-postgres-server-4.52.00-0.0.60210.noarch.rpm
  • edge-qpid-server-4.52.00-0.0.60210.noarch.rpm
  • edge-router-4.52.00-0.0.60210.noarch.rpm
  • edge-ui-4.52.00-0.0.20234.noarch.rpm
  • apigee-sso-4.52.00-0.0.21340.noarch.rpm
  • edge-analytics-4.52.00-0.0.40107.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.52.00 bootstrap_4.52.00.sh file to /tmp/bootstrap_4.52.00.sh:
      curl https://software.apigee.com/bootstrap_4.52.00.sh -o /tmp/bootstrap_4.52.00.sh
    3. Install the Edge 4.52.00 apigee-service utility and dependencies:
      sudo bash /tmp/bootstrap_4.52.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. On all Edge nodes, execute the update.sh script for the edge process:
    /opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
  3. Execute the update.sh script for SSO on all nodes:
  4. /opt/apigee/apigee-setup/bin/update.sh -c sso -f configFile
  5. On all UI nodes, execute the update.sh script for the UI:
    /opt/apigee/apigee-setup/bin/update.sh -c ui -f configFile
  6. If you are using the New Edge experience, execute the following command:
    /opt/apigee/apigee-setup/bin/update.sh -c ue -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 for Private Cloud.
Issue ID Description
CVE-2022-41946 Fixed an issue related to CVE-2022-41946.
CVE-2022-22978 Fixed an issue related to CVE-2022-22978.

Changes to supported software

Support has been added for Red Hat Enterprise Linux 8.9.

See Edge for Private Cloud supported software for a complete list of supported software.

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

Fixed some intermittent deployment issues by improving communication behavior between Message Processor and Zookeeper.


Logout in the classic Edge UI was not redirecting to the login page.

This has been fixed.

Removed deprecated and unused scripts from edge components.


Added some constraints and indexes in postgres to make analytics processing more robust.


Upgraded PostgreSQL driver in the SSO component to version 42.7.1.


Cleaned up some undocumented and non-functional options for router configurations


Fixed an optional feature to retry loading of keystore and related entities from the database if they are not found.


Spring framework in the SSO component has been upgraded to version 5.8.8.

Known issues

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

Applying multiple patch versions

This section describes how to apply multiple patch versions, in case you are updating from a version of Edge for Private Cloud that is earlier than the previous patch release version.

Each patch release contains updates to specific components of Edge for Private Cloud, such as edge-management-server. To apply multiple patch versions, you need to update each Edge component that was included in a patch release later than your currently installed version. You can find these components by looking at the Edge for Private Cloud release notes for all versions later than your current version, and checking the list of RPMs for those releases. See Apigee Release Notes for links to all Edge for Private Cloud release notes.

Note: You only need to update each component once, by installing the RPM for the latest version of the component included in the patch releases. Follow the instructions in the release notes for that version to update the component.

Note: Upgrading a component automatically installs the latest patch version of a component. If you want to upgrade to a patch version that is not the latest, you need to maintain your own tarball copy of Apigee's repo using Apigee mirror, and use this mirror for Apigee installations. For more information, refer to Using a local Edge repository to maintain your Edge version.