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

On October 25, 2023, we released a new version of Apigee Edge for Private Cloud.

**Note:** This version will be supported until October 25, 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/4520003-private-cloud-relnotes#applying-multiple-patch-versions).

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

- edge-gateway-4.52.00-0.0.60200.noarch.rpm
- edge-management-server-4.52.00-0.0.60200.noarch.rpm
- edge-message-processor-4.52.00-0.0.60200.noarch.rpm
- edge-postgres-server-4.52.00-0.0.60200.noarch.rpm
- edge-qpid-server-4.52.00-0.0.60200.noarch.rpm
- edge-router-4.52.00-0.0.60200.noarch.rpm
- apigee-sso-4.52.00-0.0.21316.noarch.rpm
- edge-analytics-4.52.00-0.0.40100.noarch.rpm
- edge-management-ui-4.52.00-0.0.20029.noarch.rpm
- edge-ui-4.52.00-0.0.20233.noarch.rpm
- apigee-service-4.52.00-0.0.1500.noarch.rpm
- apigee-mirror-4.52.00-0.0.1032.noarch.rpm
- apigee-tomcat-9.0.82-0.0.939.noarch.rpm
- apigee-configutil-4.52.00-0.0.624.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 <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
   ```

## Security issues fixed

The following is a list of known security issues that have been fixed in this release. To avoid these issues, install the latest version of Edge for Private Cloud.

| Issue ID | Description |
|---|---|
| 279065506 | In the redirection URL for OAuth2, the entropy of the state parameter has been improved to make it unpredictable, in order to avoid the Cross Site Request Forgery (CSRF) vulnerability.", |
| 279065586 | Added content security policies in header to provide an additional layer of security for sites from client side attacks. |

## Changes to supported software

Support has been added for the following software versions:

- Red Hat Enterprise Linux (Intel 64-bit): Version 8.8
- Oracle Linux (Intel 64-bit): Versions 7.9, 8.7, and 8.8
- Rocky Linux 8
- Tomcat 9.0.82

See [Edge for Private Cloud supported software](https://docs.apigee.com/release/supported-software#apigeeedgeforprivatecloudsupportedversions) for a complete list of supported software.

## Deprecations and retirements

There are no new deprecations or retirements in this release.

## New features

This release introduces the following new features:

### Set the maximum number of characters for organization and environment names

With this release, you can limit the maximum number of characters for the
organization and environment names when creating a new organization or environment. The
default value for the maximum number of characters is 255. To set a lower maximum,
set the following properties in their respective properties file:

- In the organization property file, set `org.name.max.length`.
- In the organization property file, set `env.name.max.length`.

If either of these properties is set to a value less than 0 or greater than 255, the system
will use a maximum value of 1 or 255, respectively.

### Set the expiration of access tokens

With this release, you can set the expiration of access tokens, by setting the property
`conf_keymanagement_oauth_access_token_expiry_time_in_millis` to the desired
expiration time in milliseconds. This feature is disabled by default. To enable it, set
`conf_keymanagement_oauth_access_token_is_apply_limit` to `true`
in the Message Processor.

This feature gives Apigee administrators better control over the expiration of
access tokens created in Apigee.

## Bug fixes

This section lists the Private Cloud bugs that were fixed in this release.

| Issue ID | Description |
|---|---|
| 290242749 | **When the `ServiceCallout.response` variable was used in DataMasking, policies were not visible in trace.** This has been fixed. |
| 260397807 | **An issue in Email templates prevented multi-byte characters from being sent in email.** This has been fixed. |
| 234544436 | **There was an issue where the left menu would disappear when changing organizations in the new Edge UI.** This has been fixed. |
| 293268203 | **Analytics dependencies were not upgrading automatically on management server nodes.** This has been fixed. |
| 261616264 | **Added bootstrap check to ensure postgresql is not removed/deleted during the upgrade process.** |
| 279065586 | **In the redirection URL for OAuth2, the entropy of the state parameter has been improved to make it unpredictable, in order to avoid the Cross Site Request Forgery (CSRF) vulnerability.** |
| 283310836 | **The error message when parsing large XMLs has been improved.** |
| 245936798 | **An issue with organization and environment names was causing Postgresql queries to fail.** This has been fixed by improved handling of postgres index name clashes for long organization and environment names. |
| 293733533 | **The Spring third party library in Edge Gateway components has been updated from version 5.3.20 to version 5.3.27.** |
| 294363158 | **A regression was causing some extra dimensions to show up in the dropdown menus of the analytics and monitoring pages of the Edge UI.** This has been fixed. |
| 297889765 | **Artifacts generated by apigee-mirror now have the correct ownership.** |
| 294989027 | **Improved performance of certain Stats APIs.** |

## 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.

## 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).