You're viewing **Apigee Edge** documentation.  
[Go to the
**Apigee X** documentation](http://cloud.google.com/apigee/docs). info

On May 1, 2020, we released a new version of Apigee Edge for Private Cloud.

> [!NOTE]
> For more information, see the following resources:
>
> - *[Edge for Private Cloud 4.19.01
>   documentation](https://docs.apigee.com/private-cloud/v4.19.01)*
> - *Questions or issues?* Contact [Apigee Edge Support](https://docs.apigee.com/api-platform/troubleshoot/support)
> - *Release notifications* : See [Get Apigee Edge release notifications](https://docs.apigee.com/release/get-release-notifications)

## 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.01 `bootstrap_4.19.01.sh` file to `/tmp/bootstrap_4.19.01.sh`:

      ```
      curl https://software.apigee.com/bootstrap_4.19.01.sh -o /tmp/bootstrap_4.19.01.sh
      ```
   3. Install the Edge 4.19.01 `apigee-service` utility and dependencies:

      ```
      sudo bash /tmp/bootstrap_4.19.01.sh apigeeuser=uName apigeepassword=pWord
      ```

      Where <var translate="no">uName:pWord</var> are the username and password you received from Apigee.
      If you omit <var translate="no">pWord</var>, 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. Run the `update.sh` script on all nodes. On each node, execute the following command:

   ```
   /opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
   ```

   Where <var translate="no">configFile</var> specifies the configuration file that you used to install
   Apigee Edge for Private Cloud.
3. **If you use Apigee Developer Services portal (or simply, *the portal*),** upgrade PHP, Drupal, and SmartDocs. For more information, see [Upgrade the portal](https://docs.apigee.com/private-cloud/v4.19.01/portal-upgrading).

## Supported software

This release upgrades the following software used by Apigee Developer Services portal (or simply, *the portal*):

- PHP to 7.0.32
- Drupal core to 7.69
- Drush to 8.3.2

For more information, see
[Upgrade the portal](https://docs.apigee.com/private-cloud/v4.19.01/portal-upgrading).

## Deprecations and retirements

No changes.

## Bugs fixed

The following table lists the bugs fixed in this release:

| Issue ID | Description |
|---|---|
| 146511514 | **XSS Vulnerability in SmartDocs** This release fixes a security vulnerability in SmartDocs. Sites using SmartDocs are urged to upgrade immediately. |
| 148198065 | **Policy execution order** In some cases, the order of execution for policies was not as expected. |
| 148231209 | **Qpid server logging** The Qpid server process was logging messages about the `x_forwarded_proto` property. |
| 154867155 | **Requests with unavailable targets could result in multiple responses** When faults occurred during the processing of a request without a target, Edge for the Private Cloud sometimes sent multiple responses. |
| 154868912 | **Shared flows in PostClientFlow** The Message Processor was going into an infinite loop when a proxy referenced a shared flow that was not deployed in the environment. |

## Known issues

The following table describes the known issues for this release:

| Issue ID | Description |
|---|---|
| n/a | **OpenJDK incompatibilities** Do not use the following builds of OpenJDK 1.8.0: - 1.8.0.**251** - 1.8.0.**252** If you are running one of these versions, Apigee recommends that you downgrade to a previous version. For more information, see [How to download and install prebuilt OpenJDK packages](https://openjdk.java.net/install/). |
| 76087166 | **KVMs in multi-data center environment** If an organization spans multiple datacenters (for example, dc-1, dc-2), the Management Server *should* connect only to the Cassandra nodes in the local data center for key management and Key Value Map (KVM) operations. However, the Management Server randomly connects to any of the datacenters. |