4.53.00.06 - Edge for Private Cloud release notes

You're viewing Apigee Edge documentation.
Go to the Apigee X documentation. info

On December 11, 2025, we released a new version of Apigee Edge for Private Cloud.

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.

Updating this release will update the components listed below:

edge-gateway-4.53.00-0.0.60366.noarch.rpm
edge-management-server-4.53.00-0.0.60366.noarch.rpm
edge-message-processor-4.53.00-0.0.60366.noarch.rpm
edge-postgres-server-4.53.00-0.0.60366.noarch.rpm
edge-qpid-server-4.53.00-0.0.60366.noarch.rpm
edge-router-4.53.00-0.0.60366.noarch.rpm
apigee-openldap-2.4-0.0.2528.noarch.rpm
apigee-mirror-4.53.00-0.0.1044.noarch.rpm
apigee-tomcat-9.0.111-0.0.962.noarch.rpm
apigee-sso-4.53.00-0.0.21610.noarch.rpm
edge-uapim-4.53.00-0.0.60366.noarch.rpm
edge-uapim-connector-4.53.00-0.0.60366.noarch.rpm

You can check the RPM versions currently 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:

On all Edge nodes:
1. Clean the Yum repositories:
```
sudo yum clean all
```
2. Download the latest Edge 4.53.00 bootstrap_4.53.00.sh file to /tmp/bootstrap_4.53.00.sh:
```
curl https://software.apigee.com/bootstrap_4.53.00.sh -o /tmp/bootstrap_4.53.00.sh
```
3. Install the Edge 4.53.00 apigee-service utility and dependencies:
```
sudo bash /tmp/bootstrap_4.53.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. Use the source command to execute the apigee-service.sh script:
```
source /etc/profile.d/apigee-service.sh
```
5. Update the apigee-setup utility:
```
apigee-service apigee-setup update
```
On all Edge nodes, execute the update.sh script for the edge process (including monetization):
```
/opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
```

On all LDAP nodes, execute the update.sh script:

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

If you are using SSO, execute the following command:

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

If you are using apigee-mirror, execute the following command:

/opt/apigee/apigee-service/bin/apigee-service apigee-mirror update

New features

This section lists new features in this release.

Issue ID	Description
426383877	Added support for the ECDSA format key and certificate for both northbound (client to Apigee) and southbound (Apigee to target) communication.

Bug fixes

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

Issue ID	Description
445563031	Fixed datastore errors caused due to a specific type of interaction between Cassandra and application components (Management server, Message Processor or Router).
412696630	Fixed a bug in message processors and routers where private keys were occasionally failing to load during bootstrap.
448566858	Removed unnecessary logs related to keystores from message processors.
442733857	Improved performance of encrypted KeyValueMaps, especially for KVMs containing a large number of entries.

Security issues fixed

Issue ID	Description
463848991	Addressed CVE-2025-61795 for Tomcat

Edge for Private Cloud API Hub Integration

This release continues the support for Apigee API Hub Connector for Private Cloud integration, enabling organizations to sync both API metadata and runtime analytics to Google Cloud API Hub. The integration includes a new Apigee API Hub connector binary and enhancements to the message processor, which exports runtime data to a network file system(NFS). The API Hub for Private Cloud connector consumes this data and publishes it to API Hub. There are no bug fixes or changes to existing integration behaviors.

For more information, see Edge for Private Cloud API Hub Integration.

Personally identifiable information (PII) masking

This feature ensures data privacy and compliance by allowing you to mask sensitive data within API proxy and shared flow bundles before they are synchronized to API Hub.

Default masks: The connector automatically applies a built-in list of XPath expressions (default masks) to mask known PII sources in policy configurations (e.g., hardcoded basic authentication passwords, private keys in JWT/JWS policies).
Custom masks: You can configure additional custom masks by setting the conf_uapim_connector.uapim.mask.xpaths property in the /opt/apigee/customer/application/uapim-connector.properties file, allowing you to target customer-specific sensitive fields.

Organization reconciliation (Backfill)

The connector now provides a defined process for reconciling (or backfilling) an existing Apigee organization's entire API metadata set to API Hub.

Process: Reconciliation is achieved by temporarily opting out an organization from the connector's configuration (clearing the runtimeDataPubsub and metadataPubsub property values) and then immediately opting it back in (restoring the values).
Function: This action forces the connector to perform a complete fetch and full resync of all metadata for the specified organization, resolving potential data inconsistencies.

Changes to supported software

Added Support for Amazon Linux 2023(7,8) and RHEL-9.6.
Added Support for Apache Tomcat 9.0.111.

See Edge for Private Cloud supported software for a complete list of supported softwares.

Deprecations and retirements

There are no new deprecations or retirements in this release.

Known issues

See Known issues with Edge for 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 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.