Google is committed to advancing racial equity for Black communities. See how. - Edge for Private Cloud release notes

On August 19, 2020, we released a new version of Apigee Edge for Private Cloud.

Update procedure

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.19.06 file to /tmp/
      curl -o /tmp/
    3. Install the Edge 4.19.06 apigee-service utility and dependencies:
      sudo bash /tmp/ 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 script:
      source /etc/profile.d/
  2. On all Edge nodes, execute the script for the edge process. To do this, execute the following command on each node:
    /opt/apigee/apigee-setup/bin/ -c edge -f configFile

    where configFile specifies the configuration file that you used to install Apigee Edge for Private Cloud. For example, /opt/silent.conf.

Supported software

No changes.

Deprecations and retirements

The privateKeyExportable query parameter on the Aliases API has been deprecated.

New Features

No changes.

Bugs fixed

The following table lists the bugs fixed in this release:

Issue ID Description

Keystores with multiple certificates were not supported for certs with multiple SANs.

Management servers were failing to start and returning the error "KeyStores with multiple certificates are not supported," which was caused by certificates with multiple SANs.

Note: Certificates with multiple SANS are supported.