- Edge for Private Cloud release notes

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

On March 30, 2023, we released a new version of Apigee Edge for Private Cloud.

Note: This version will be supported until March 30, 2024.

Update procedure

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

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

  • edge-gateway-4.51.00-0.0.60186.noarch.rpm
  • edge-management-server-4.51.00-0.0.60186.noarch.rpm
  • edge-postgres-server-4.51.00-0.0.60186.noarch.rpm
  • edge-qpid-server-4.51.00-0.0.60186.noarch.rpm
  • edge-router-4.51.00-0.0.60186.noarch.rpm
  • apigee-postgresql-10.17-0.0.2535.noarch.rpm
  • edge-mint-gateway-4.51.00-0.0.40322.noarch.rpm
  • edge-mint-management-server-4.51.00-0.0.40322.noarch.rpm
  • edge-mint-message-processor-4.51.00-0.0.40322.noarch.rpm
  • apigee-sso-4.51.00-0.0.21244.noarch.rpm
  • apigee-attribution-4.51.00-0.0.723.noarch.rpm
  • apigee-sosreport-5.0-0.0.2508.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 Postgres nodes (master and standby):
    /opt/apigee/apigee-setup/bin/update.sh -c ps -f configFile
  3. On all Edge nodes, execute the update.sh script for the edge process:
    /opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
  4. Execute the update.sh script for SSO on all nodes:
    /opt/apigee/apigee-setup/bin/update.sh -c sso -f configFile

New features

This release introduces the following new feature:

TLS 1.3 for southbound traffic

This release adds support for TLS 1.3 for southbound traffic (traffic between a Message Processor and the backend server). See Configuring TLS 1.3 for southbound traffic for more information.

Security issues fixed

There are no security issues fixed in this release.

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.

Bug fixes

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

Issue ID Description

Lack of trailing spaces after condition operators was causing deployment failures.

This has been fixed by improved handling of new lines in condition statements of proxies.

Updated Postgres driver version in Gateway and Monetization to 42.5.4.


A few properties were missing when target details of a proxy were fetched as JSON.

This has been fixed.

Modified audit data of developer app related APIs.

The consumer secret is now consistently logged in a masked manner. You can set CWC conf_keymanagement_app.auditlog.mask.secret to false in Management server to prevent the secret from being masked, in case you want to log plaintext secret in audit.

Added fixes to optimize loading of Open API Spec resources as part of OASValidation policy.

This should speed up message processor boot time if MP has to load many OAS resources. This should also prevent unnecessary error and warn logs from being generated while loading the proxies containing OAS resources.

External entities are not allowed to be loaded by default in XSLTransform Policy.

This can be enabled by setting flag conf_feature-flags_xsl.allow.external.entities=true in message processor.

Some Cassandra tables were still using SizeTieredCompactionStrategy by default.

This has been changed to LeveledCompactionStrategy. Note that this change is only applicable to new installations of Apigee Edge for Private Cloud.

Fixed a minor regression in a pre-install script of apigee-postgresql where taking a backup of configuration files was failing under some conditions.


Removed unexpected parameter credentialsLoaded from API response of fetching apps.


The following API fields, which were recently added to Apigee, are visible in Edge for Private Cloud. However, they have no effect in Edge for Private Cloud, so you can safely ignore them if you encounter them.

  • proxy_deployment_type
  • sense_action_id
  • sense_flag_headers
  • x_apigee_grpc_status
  • x_apigee_grpc_service_name
  • x_apigee_grpc_rpc_name

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.