- Edge for Private Cloud release notes

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

On November 3, 2021, we released a new version of Apigee Edge for Private Cloud.

Update procedure

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

  • apigee-setup-4.51.00-0.0.1131.noarch.rpm
  • apigee-provision-4.51.00-0.0.618.noarch.rpm
  • apigee-service-4.51.00-0.0.1431.noarch.rpm
  • apigee-postgresql-10.17-0.0.2521.noarch.rpm
  • edge-gateway-4.51.00-0.0.60146.noarch.rpm
  • edge-management-server-4.51.00-0.0.60146.noarch.rpm
  • edge-message-processor-4.51.00-0.0.60146.noarch.rpm
  • edge-qpid-server-4.51.00-0.0.60146.noarch.rpm
  • edge-postgres-server-4.51.00-0.0.60146.noarch.rpm
  • edge-router-4.51.00-0.0.60146.noarch.rpm
  • edge-management-ui-4.51.00-0.0.20025.noarch.rpm
  • edge-ui-4.51.00-0.0.20205.noarch.rpm
  • edge-mint-management-server-4.51.00-0.0.40243.noarch.rpm
  • edge-mint-gateway-4.51.00-0.0.40243.noarch.rpm
  • edge-mint-message-processor-4.51.00-0.0.40243.noarch.rpm
  • apigee-mtls-4.51.00-0.0.20234.noarch.rpm
  • apigee-mtls-consul-4.51.00-0.0.20140.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:pWord are the username and password you received from Apigee. If you omit pWord, you will be prompted to enter it.

    4. Update the apigee-setup utility:
      sudo /opt/apigee/apigee-service/bin/apigee-service apigee-setup update
    5. 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 Postgres nodes (master and standby):
    /opt/apigee/apigee-setup/bin/update.sh -c ps -f /opt/silent.conf
  4. On all Edge nodes, execute the update.sh script for the edge process:
    /opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
  5. Execute the update.sh for the UI on all nodes:
    /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
  7. 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 supported software in this release.

Deprecations and retirements

There are no new deprecations or retirements in this release.

New features

This release introduces the following new features:

Added ability to set TLS Ciphers in the New Edge UI

You can now configure TLS ciphers in the New Edge UI using the property MANAGEMENT_UI_TLS_ALLOWED_CIPHERS. See TLS configuration properties.

Enabled Envoy Adapter configuration in Edge for Private Cloud API Products UI

You can now configure the Envoy Adapter proxy in Edge for Private Cloud. See the the Envoy Adapter documentation.

Bug fixes

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

Issue ID Description

Users were unable to edit the end date of a rate plan

This has been fixed.

Certain APIs used by UE (new UI) were failing when external role mapping was enabled

This has been fixed.

Certain APIs were not returning correct secrets when credential secret encryption was enabled

This has been fixed.

apigee-mtls was failing to detect already installed consul users by default

This has been fixed.

apigee-mtls was experiencing segmentation faults on a bad topology

This has been fixed.

Fixed system requirement checks during installation of qpid component to match documented recommendations of 16 GB RAM rather than 8 GB


Postgres database upgrades were being attempted even though there was no Postgres database change

This has been fixed.

A message processor would sometimes boot up successfully even though it was not able to load all underlying repositories

This has been fixed. A failure in loading a repository will cause a failure in booting up of MP.

apigee-provision has been excluded from apigee-all status output


apigee-mirror should fail if repo is not found

This has been fixed.

apigee-mirror was not working on RHEL-8

This has been fixed.

Corrected the regular expressions for user password rules


apigee-all version command didn't show version of apigee-provision component installed on the node.

This has been fixed

Improved error alert logic for password update page


Fixed an issue in which edge-management-ui-static was not upgrading to the latest patch


Fixed a console error in sharedflow for undefined flow method variable

Security issues fixed

There are no security issues fixed in this release.

Known issues

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