You're viewing **Apigee Edge** documentation.
[Go to the
**Apigee X** documentation](http://cloud.google.com/apigee/docs). info
On April 19, 2023, we released a new version of Apigee Edge for Private Cloud.
**Note:** This version will be supported until August 31, 2024.
> [!NOTE]
> For more information, see the following resources:
>
> - *[Edge for Private Cloud 4.52.00
> documentation](https://docs.apigee.com/private-cloud/v4.52.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
This section describes how to install this release if you are updating from the previous
release of Edge for Private Cloud. If you need to update from an earlier release, see
[Applying multiple patch versions](https://docs.apigee.com/release/notes/4520001-private-cloud-relnotes#applying-multiple-patch-versions).
Updating this release will update the components in the following list of RPMs:
- edge-management-server-4.52.00-0.0.60190.noarch.rpm
- edge-postgres-server-4.52.00-0.0.60190.noarch.rpm
- edge-qpid-server-4.52.00-0.0.60190.noarch.rpm
- edge-router-4.52.00-0.0.60190.noarch.rpm
- apigee-cassandra-2.1.22-0.0.2539.noarch.rpm
- apigee-cassandra-client-2.1.22-0.0.2519.noarch.rpm
- apigee-provision-4.52.00-0.0.623.noarch.rpm
- apigee-sso-4.52.00-0.0.21245.noarch.rpm
- edge-analytics-4.52.00-0.0.40091.noarch.rpm
- apigee-postgresql-14.5-0.0.2739.noarch.rpm
- edge-mint-gateway-4.52.00-0.0.40323.noarch.rpm
- edge-mint-management-server-4.52.00-0.0.40323.noarch.rpm
- edge-mint-message-processor-4.52.00-0.0.40323.noarch.rpm
- apigee-sosreport-5.0-0.0.2509.noarch.rpm
> [!NOTE]
> **Note:** `sosreport`, a system level diagnostic and data collection tool, is now installed by default. Apigee support agents can use `sosreport` to help troubleshoot issues that you may encounter. The tool does not collect any data unless it is run.
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.52.00 `bootstrap_4.52.00.sh` file to `/tmp/bootstrap_4.52.00.sh`:
```
curl https://software.apigee.com/bootstrap_4.52.00.sh -o /tmp/bootstrap_4.52.00.sh
```
3. Install the Edge 4.52.00 `apigee-service` utility and dependencies:
```
sudo bash /tmp/bootstrap_4.52.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-provision` utility on the Management Server:
```
/opt/apigee/apigee-service/bin/apigee-service apigee-provision update
```
3. Update Postgres nodes (master and standby):
```
/opt/apigee/apigee-setup/bin/update.sh -c ps -f configFile
```
4. On all Edge nodes, execute the `update.sh` script for the edge process:
```
/opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
```
5. Execute the update.sh script for SSO on all nodes:
```
/opt/apigee/apigee-setup/bin/update.sh -c sso -f configFile
```
## 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 |
|---|---|
| 271093461 | **OASValidation policy was consuming too much heap memory allocation** This has been fixed. |
| 248499777 | **Added more checks to prevent smuggling a GET request inside another POST request.** |
| 245387101 | **Modified audit data of developer app related APIs.** The consumer secret is now consistently logged in a masked manner. You can set configuration `conf_keymanagement_app.auditlog.mask.secret` to `false` in Management server to prevent the secret from being masked,in case you want to log plaintext secret in audit. |
| 267778362 | **Apigee-provision was creating empty lines while adding cron entries.** This has been fixed. |
| 267788856 | **Enhanced rebuildindex so non ID based index APIs function appropriately when there are more than 10k apps per entity.** |
| 273931118 | **Fixed a regression in MGMT API which was causing incorrect content types to be returned when accept header in requests had a wildcard.** This was also causing failures while downloading trace file in the UI. |
| 274587823 | **For security reasons, external entities are now not allowed to be loaded by default in XSLTransform Policy.** You can override this by setting the flag `conf_feature-flags_xsl.allow.external.entities=true` in Message Processor. |
| 245387101 | **Modified audit data of developer app related APIs.** The consumer secret is now consistently logged in a masked manner. You can the configuration `conf_keymanagement_app.auditlog.mask.secret` to `false` in Management server to prevent the secret from being masked,in case you want to log plaintext secret in audit. |
| 276991965 | **Fixed a bug introduced in OPDK v4.52.00 which was causing certain API and Accept header combinations to fail.** |
| 260024953 | **Apigee was not populating some target variables, such as URL and Host, when a target server was used and a target error was encountered.** This has been resolved. |
| 274399775 | **Cassandra and cassandra-client were not upgrading to latest versions when upgrading from Edge for Private Cloud v4.51 to v4.52.** This has been fixed |
| 269545512 | **Updated Postgres driver version in Gateway to 42.5.4.** |
| 270203185 | **Updated Postgres driver version in Monetization to 42.5.4.** |
| 197529839 | **Improved handling of new lines in condition statements of proxies.** |
| 214664198 | **Added a column in Analytics Fact Tables which captures the top three policies that took the longest to run.** |
| 258898812 | **Removed unexpected parameter `credentialsLoaded` from API response of fetching apps.** |
| 270967547 | **There was a problem upgrading from Edge for Private Cloud 4.50 to 4.52.** This has been fixed. |
## Known issues
Apigee-postgresql is having issues with upgrading from version 4.50 or 4.51 to version 4.52.
The issues mainly
occur when the number of child fact tables is greater than 500. See
[Postgresql upgrade when updating
to version 4.52](https://docs.apigee.com/release/known-issues#private-cloud-known-issues) in Known issues
with Edge for Private Cloud for a workaround.
See [Known issues with Edge for Private Cloud](https://docs.apigee.com/release/known-issues#private-cloud)
for a complete list of known issues.
## Applying multiple patch versions
This section describes how to apply multiple patch versions, in case you are updating from
a version of Edge for Private Cloud that is earlier than the previous patch release version.
Each patch release contains updates to specific components of Edge for Private Cloud, such as
`edge-management-server`.
To apply multiple patch versions, you need to update each Edge component that was included in
a patch release later than your currently installed version. You can find these components by
looking at the Edge for Private Cloud release notes for all versions later than your current
version, and checking the list of RPMs for those releases. See
[Apigee Release Notes](https://docs.apigee.com/release/notes/apigee-release-notes) for links to all
Edge for Private Cloud release notes.
**Note:** You only need to update each component once, by installing the RPM for the latest
version of the component included in the patch releases. Follow the instructions in the
release notes for that version to update the component.
**Note:** Upgrading a component automatically installs the latest patch version of a
component. If you want to upgrade to a patch version that is not the latest, you need to
maintain your own
tarball copy of Apigee's repo using Apigee mirror, and use this mirror for Apigee installations.
For more information, refer to [Using a local Edge repository to maintain your Edge version](https://docs.apigee.com/private-cloud/v4.51.00/installation-overview#local-repo).