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

On October 28, 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.06
>   documentation](https://docs.apigee.com/private-cloud/v4.19.06)*
> - *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

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

- edge-gateway-4.19.06-0.0.20097.noarch.rpm
- edge-management-server-4.19.06-0.0.20097.noarch.rpm
- edge-message-processor-4.19.06-0.0.20097.noarch.rpm
- edge-postgres-server-4.19.06-0.0.20097.noarch.rpm
- edge-qpid-server-4.19.06-0.0.20097.noarch.rpm
- edge-router-4.19.06-0.0.20097.noarch.rpm
- edge-management-ui-4.19.06-0.0.20017.noarch.rpm
- apigee-drupal-7.73-0.0.305.noarch.rpm
- apigee-drupal-devportal-4.19.06-0.0.318.noarch.rpm
- apigee-sap-drupal-devportal-4.19.06-0.0.318.noarch.rpm
- apigee-drupal-contrib-4.19.06-0.0.303.noarch.rpm

**Note:** The RPM of apigee-drupal-contrib-4.19.06 has been updated to release 0.0.303.
This RPM is identical to release 0.0.302 and was updated to resolve certain Drupal dependencies.
If you patch from earlier versions, the RPM version might not change.

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

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

      ```
      sudo bash /tmp/bootstrap_4.19.06.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. On all Edge nodes, execute the `update.sh` script for the `edge` process. To do this, execute the following command on each node:

   ```
   /opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
   ```
3. If you are using the New Edge experience, execute the following command on all New Edge UI nodes:

   ```
   /opt/apigee/apigee-setup/bin/update.sh -c ue -f configFile
   ```
4. On all Apigee Developer Services portal nodes, update the `devportal` process by executing the following command:

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

## Supported software

No changes.

## Deprecations and retirements

No new deprecations or retirements.

## New Features

No new features.

## Bugs fixed

The following table lists the bugs fixed in this release:

| Issue ID | Description |
|---|---|
| 179079634 | **Apigee SSO was not verifying a digital signature, which caused a potential security issue.** The setting `SSO_SAML_SIGNED_ASSERTIONS=y` has been added to the config file, which solves the issue. See [Install and configure Edge SSO for HTTP access](https://docs.apigee.com/private-cloud/v4.19.06/install-and-configure-edge-sso#installandconfigureedgessoforhttpaccess). |
| 170341798 | **Dependencies defined within Gateway were preventing the latest libraries from being utilized.** |
| 120556489 | **SSO config file did not have a setting to specify a home redirect from SSO to the Edge UI.** As a result, logging in through SSO (port 9099) was failing with the message "Where to?". This has been fixed. You can now set a home redirect from SSO to the Edge UI by the following steps: 1. Edit the file `/opt/apigee/customer/application/sso.properties`. If the file does not exist, create it. 2. Add the line below to the file. Use the applicable protocol, http or https, and replace \<Edge-UI\>:\<PORT\> with the actual Edge UI endpoint and port. ``` conf_login_homeredirect=https://<Edge-UI>:<PORT>/edge ``` 3. Restart the SSO server. ``` apigee-service apigee-sso restart ``` |
| 148433643 | **Installing the Edge UI was causing a segmentation fault.** The error message was `runtime error: invalid memory address or nil pointer dereference` |
| 168258482 | **Executable permissions were missing for "group" and "world" on some directories.** As a result, running the command `apigee-all status` was returning an error. |
| 169377969 | **Unable to get UI trace for transactions with large values assigned to flow variable.** |
| 160904129 | **A Dev Portal 403 Access denied problem was fixed for CSS/JS URLs in all modules added to the `/sites` directory.** |

## Known issues


For a list of known issues with Edge Private Cloud, see
[Known issues with Edge Private Cloud](https://docs.apigee.com/release/known-issues#private-cloud).