- Edge for Private Cloud release notes

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

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

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

Update procedure

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

  • edge-gateway-4.51.00-0.0.60166.noarch.rpm
  • edge-management-server-4.51.00-0.0.60166.noarch.rpm
  • edge-message-processor-4.51.00-0.0.60166.noarch.rpm
  • edge-postgres-server-4.51.00-0.0.60166.noarch.rpm
  • edge-qpid-server-4.51.00-0.0.60166.noarch.rpm
  • edge-router-4.51.00-0.0.60166.noarch.rpm
  • apigee-sso-4.51.00-0.0.21104.noarch.rpm
  • edge-analytics-4.51.00-0.0.40064.noarch.rpm
  • apigee-mirror-4.51.00-0.0.1024.noarch.rpm
  • apigee-mtls-4.51.00-0.0.20235.noarch.rpm
  • edge-ui-4.51.00-0.0.20209.noarch.rpm
  • edge-management-ui-4.51.00-0.0.20029.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. Execute the update.sh script for SSO on all nodes:
    /opt/apigee/apigee-setup/bin/update.sh -c sso -f configFile
  4. On all UI nodes, execute the update.sh script for the UI:
    /opt/apigee/apigee-setup/bin/update.sh -c ui -f configFile
  5. If you are using the New Edge experience, execute the following command:
    /opt/apigee/apigee-setup/bin/update.sh -c ue -f configFile
  6. 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

No security issues were 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.

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

The Trace tool was not displaying spaces correctly after decoding

This has been fixed.

Fixed analytics dependency of the management server rpm when installing Edge for Private Cloud


SAML configuration error on login page was not visible

This has been fixed.

Error messages for Apigee SSO installation have been improved.


An authentication issue with Apigee SSO has been fixed


Reset password was not working for LDAP configurations

This has been fixed.

Portal SSO shows the Apigee domain when hovering over footer links in third-party web pages

This has been fixed.

Directories of edge-analytics were world writeable.

This has been fixed.

Improved resilience and logging of DNS management code in message processors


Several configuration variables for apigee-mtls differed from what was publicly documented

This has been fixed.

apigee-mirror was leaving root-owned RPMs on the filesystem if a sync failed

This has been fixed. Failures will be properly reflected in shell return code.

Known issues

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