You're viewing **Apigee Edge** documentation.
[Go to the
**Apigee X** documentation](http://cloud.google.com/apigee/docs). info
On February, 16, 2022, we released a new version of Apigee Edge for Private Cloud.
**Note:** This version will be supported until February 16, 2023.
> [!NOTE]
> **Note about the Apache Log4j vulnerability:**
>
>
>
> 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)
> - *[Edge for Private Cloud support timeline](https://docs.apigee.com/release/apigee-edge-release-process#apigee-edge-for-private-cloud-support-timeline)*
> - *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:
- apigee-machinekey-1.1.4-0.0.20024.noarch.rpm
- apigee-drupal-7.87-0.0.310.noarch.rpm
- apigee-drupal-devportal-4.51.00-0.0.412.noarch.rpm
- apigee-drupal-contrib-4.51.00-0.0.407.noarch.rpm
- apigee-mirror-4.51.00-0.0.1023.noarch.rpm
- edge-management-ui-4.51.00-0.0.20026.noarch.rpm
- edge-ui-4.51.00-0.0.20206.noarch.rpm
- edge-management-ui-static-4.51.00-0.0.20035.noarch.rpm
- apigee-service-4.51.00-0.0.1432.noarch.rpm
- apigee-setup-4.51.00-0.0.1132.noarch.rpm
- edge-gateway-4.51.00-0.0.60162.noarch.rpm
- edge-management-server-4.51.00-0.0.60162.noarch.rpm
- edge-message-processor-4.51.00-0.0.60162.noarch.rpm
- edge-postgres-server-4.51.00-0.0.60162.noarch.rpm
- edge-qpid-server-4.51.00-0.0.60162.noarch.rpm
- edge-router-4.51.00-0.0.60162.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. 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. Update the `apigee-machinekey` utility:
```
/opt/apigee/apigee-service/bin/apigee-service apigee-machinekey update
```
3. On all Edge nodes, execute the `update.sh` script for the edge process:
```
/opt/apigee/apigee-setup/bin/update.sh -c edge -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. 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
```
7. 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). 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#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 |
|---|---|
| 211873022 | **Setting mail.smtp.ssl.protocols to an empty string caused SMTP emails to fail** This has been fixed. |
| 216482436 | **In the GenerateJWT policy, when specifying jwk as an additional header claim, the policy did not correctly handle the payload** This has been fixed. |
| 204745973 | **Analytics data was missing in PostgresSQL after an update to version 4.51.00** This has been fixed. |
| 213320910 | **When a forward proxy was used between a Message Processor and target server, analytics captured inconsistent target details** Target details in analytics were sometimes for the actual target and sometimes for the proxy. This behavior has been fixed, so target details captured in analytics are always those of the actual target. |
| 214365856 | **Drupal-related warning messages were based on Drupal 8 instead of Drupal 9** This has been fixed. |
| 213923272 | **Some user actions, such as getting the version of `apigee-mirror`, required the user to have sudo access** This has been fixed. Users can now perform those actions without having sudo access. |
| 158572674 | **Access control policy reported errors when x-forwarded-for headers contained ip:port format** This has been fixed. |
| 174970453 | **Permissions containing both a wildcard (\*) and special character (such as a comma) were not working as expected** This has been fixed. |
| 215555851, 210780867, 217323200 | **Apache Log4j 2.17.1 is now shipped in the thirdparty library of Apigee** The `apigee-machinekey` component no longer uses the Log4j library for logging. `wsdl2apigee` libraries in the UI no longer use Log4j 1.2.X. |
| 199833224 | **An issue with the Korean language input for the Edge Proxy Editor has been fixed** |
| 206614896 | **The Edge UI failed to open due to an empty cookie set in the header** This has been fixed by deleting the empty cookie. |
| 203621889 | **Bash scripts were returning undesired warning messages** This has been fixed by replacing `[` with `[[` in the scripts. |
| 206786005 | **Fixed an error when `apigee-all wait_for_ready` is run on a node where `apigee-provision` is installed** |
| 204164967 | **Business logic regarding email update is fixed, and a Javascript vulnerability issue was fixed by upgrading knockout.js to version 3.5.1** |
| 67164663 | **Unwanted rotation and logs were being printed with TIME_SIZE rotation policy** This has been fixed. |
| 173566787 | **The behavior of MP has changed: it will now reuse existing target IPs once if DNS resolution fails during DNS cache refresh** |
## Known issues
See [Known issues with Edge for Private Cloud](https://docs.apigee.com/release/known-issues#private-cloud)
for a complete list of known issues.