- Edge for Private Cloud release notes

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

On April 28, 2022, we released a new version of Apigee Edge for Private Cloud.

Note: This version will be supported until April 28, 2023.

Update procedure

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

  • edge-gateway-4.51.00-0.0.60167.noarch.rpm
  • edge-management-server-4.51.00-0.0.60167.noarch.rpm
  • edge-message-processor-4.51.00-0.0.60167.noarch.rpm
  • edge-postgres-server-4.51.00-0.0.60167.noarch.rpm
  • edge-qpid-server-4.51.00-0.0.60167.noarch.rpm
  • edge-router-4.51.00-0.0.60167.noarch.rpm
  • edge-management-ui-4.51.00-0.0.20031.noarch.rpm
  • apigee-mtls-consul-4.51.00-0.0.20150.noarch.rpm
  • apigee-mtls-4.51.00-0.0.20242.noarch.rpm
  • apigee-service-4.51.00-0.0.1434.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. 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. If you are using the New Edge experience, execute the following command:
    /opt/apigee/apigee-setup/bin/update.sh -c ue -f configFile
  4. If you are using Apigee mTLS, follow the procedure described in Upgrade Apigee mTLS. For more information, see Introduction to Apigee mTLS.

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
A security issue has been fixed for non-generic responses that could have leaked configuration data.

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

Requests to Python callout in sharedflow were failing due to a java.lang.NoClassDefFoundError

This has been fixed.

Deploying a proxy was taking too long

This has been fixed.

OASValidation was returning 500 status when validation failed

OASValidation now returns the correct 400 status.

Empty JSON parameter was causing a steps.jws.GenerationFailed error

This has been fixed.

Added proper log entries for statistics collector custom variables population in Zookeeper


SSO Error handling was not returning correct error messages

This has been fixed.

Proxy revision was returning a 400 error when used as a target with LocalTargetConnection

This has been fixed

VerifyJWT policy was not allowing the use:sig attribute in JSON Web Key Set public key

This has been fixed.

DeleteOAuthV2Info policy was failing to remove the access token

This has been fixed.

Made AccessControlAction case-insensitive


Converted monit restart command to a configuration so it can be overridden by using configuration monit_restart_program


Audited and updated system for the Apigee Edge UI based on the latest Content Security Policy standards


The apigee-service RPM no longer depends on edge-gateway


apigee-mtls-consul is now compatible with Edwards Curve 25519 encryption algorithm


JWT policy was converting int datatype to double

This has been fixed.

Upgraded third party library xmlbeans-2.4.0 to xmlbeans-3.1.0

Known issues

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