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

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.

> [!NOTE]
> **Note about the Apache Log4j vulnerability:**
>
> <br />
>
> Edge for Private Cloud's default configuration contains Log4j 2 but
> is not vulnerable to Log4j 2
> ([CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228)).
>
> Likewise, Edge for Private Cloud is not affected by the
> related vulnerability in Apache Log4j-1.x, which is shipped with ZooKeeper. That
> vulnerability requires a
> specific configuration of Log4j-1.x that Edge for Private Cloud
> does not ship as a default configuration. Therefore the vulnerability is not
> exploitable in Edge for Private Cloud.

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

## 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 <var translate="no">uName</var> and <var translate="no">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. 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](https://docs.apigee.com/private-cloud/v4.51.00/mtls-upgrade.md.txt). For more information, see [Introduction to Apigee
   mTLS](https://docs.apigee.com/private-cloud/v4.51.00/mtls-intro).

## Security issues fixed

No security issues were fixed in this release.

## Changes to
[supported software](https://docs.apigee.com/release/supported-software.md.txt#apigeeedgeforprivatecloudsupportedversions)

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 |
|---|---|
| 219088976 | **The Trace tool was not displaying spaces correctly after decoding** This has been fixed. |
| 223717655 | **Fixed analytics dependency of the management server rpm when installing Edge for Private Cloud** |
| 194469693 | **SAML configuration error on login page was not visible** This has been fixed. |
| 190609332 | **Error messages for Apigee SSO installation have been improved.** |
| 214146121 | **An authentication issue with Apigee SSO has been fixed** |
| 220188030 | **Reset password was not working for LDAP configurations** This has been fixed. |
| 220993729 | **Portal SSO shows the Apigee domain when hovering over footer links in third-party web pages** This has been fixed. |
| 178695867 | **Directories of edge-analytics were world writeable.** This has been fixed. |
| 197945951 | **Improved resilience and logging of DNS management code in message processors** |
| 203891604 | **Several configuration variables for apigee-mtls differed from what was publicly documented** This has been fixed. |
| 218898599 | **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](https://docs.apigee.com/release/known-issues.md.txt#private-cloud)
for a complete list of known issues.