You're viewing Apigee Edge documentation.
View Apigee X documentation.
On July 29, 2021, we released version 4.51.00 of the Edge for Private Cloud Feature Release.
The following table summarizes the changes in this release:
This release includes the following new features:○ A new pop-up window warns you of end of life (EOL) dates
○ Option to log out users when their passwords are changed
○ Set TLS version for SMTP
○ Added an enhanced
○ Added sosreport, a new system level diagnostic and and data collection tool.
For more information about each of these new features, see New features.
The following issues affecting backward compatibility were introduced in this version
of Apigee Edge for Private Cloud:
Since the previous Edge for Private Cloud Feature Release, the following releases have occurred and are included in this release:
With the release of 4.51.00:
For more detailed information about the deprecations including removal timelines, see Apigee deprecations and retirements.
This release includes the following known issues:
For more information about each of these known issues, including workarounds, see Known issues.
For instructions on upgrading to Edge for Private Cloud 4.51.00, see Update Apigee Edge 4.19.06 or 4.50.00 to 4.51.00.
This section lists new features in this release. Additionally, this release includes all features in the Edge UI, Edge Management, and Portal releases listed in Included Releases.
In addition to the following enhancements, this release also contains multiple usability, performance, security, and stability enhancements.
A new pop-up window warns you of end of life (EOL) dates for Edge for Private Cloud
Edge for Private Cloud customers will start seeing warning messages displayed six month prior to the installed version's EOL date. The EOL message will be shown once per browser session: if you close the tab or browser, the session will be lost. If you then re-open Apigee in a browser, the message will be displayed again.
New option to log out users when their passwords are changed
A new flag was added to
apigee.feature.clearSessionOnPasswordUpdate, which lets
you configure whether users are logged out after you change their password.
The default is that users are not logged off.
New flag to set TLS version for SMTP
A new flag has been added to
mail.smtp.ssl.protocols, which specifies the SSL protocol
that are enabled for SMTP connections. This feature lets you configure SSL protocols based on
your security requirements.
New diagnostic tool, sosreport
Added Sosreport, a new system level diagnostic and data collection tool.
Added support for new software versions
Apigee has added support for the following software versions:
- Postgres version 10.17
- Nginx version 1.20.1
- TLS 1.3 Northbound support
Configure forward proxy.
The following flags have been added, which let you configure a forward proxy:
By default the values of the flags are empty.
Enhanced pg-data-purge script to purge parent fact tables from analytics
To run the script, enter the following command:
/opt/apigee/apigee-service/bin/apigee-service apigee-postgresql pg-data-purge org_name env_name number_of_days_to_retain [Delete-from-parent-fact - N/Y] [Confirm-delete-from-parent-fact - N/Y]
The script has the following options:
Delete-from-parent-factDefault : No. Will also delete data older than retention days from parent fact table.
Confirm-delete-from-parent-fact. Default: No. If No, the script will prompt for confirmation before deleting data from parent fact. Set to Yes if the purge script is automated.
Option to change the user label in the login page
A new flag,
apigee.feature.customLoginUserLabel allows you to configure the user label
in the login page based on their preference. The default is Email address.
This release includes the following changes to supported software:
|Support Added||No Longer Supported|
This release supports the following software versions:
The following software versions are no longer supported with this release:
For a complete list of supported platforms, see Supported software and supported versions.
This section lists the Private Cloud bugs that were fixed in this release. Additionally, this release includes all bug fixes in the Edge UI, Edge Management, and Portal releases shown in Included Releases.
Mint Management Server needs to be updated when Postgres failover is performedAn enhanced script was created to change Postgres connection details for Mint Management Server. See Handling a PostgresSQL database failover.
Without an internet connection, Apigee SSO tried to download an external font library during login.The Google Sans font for headers, which doesn't have an open source license, has been replaced with the Noto Sans font.
The HMAC policy did not appear in the policy chooser.The policy is now displayed in the policy chooser.
Monetization installation was failing on the second management server.Some potential issues due to a race condition during installation of Mint Management Server have been fixed.
Unable to change the user label in the login pageA new flag has been added to
In the Developers UI, a forbidden character in the developer's email address prevented editing the developer's details.This has been fixed.
Management Server wasn't coming up if Cassandra nodes in other data centers were down.The enable Cassandra authentication script has been enhanced to prevent this problem.
AWS Linux 1 is being deprecatedSupport has been added for AWS Linux 2.
GET requests to dailysummaryreports were being allowed without CSRF protectionThis has been fixed
Consul connect client was not using all the available Consul servers for automatic failoverThis has been fixed
Customers weren't able to add new Cassandra nodes due to incorrect
ServiceCallout policy was incorrectly splitting the header values when the
Management server was not always connecting to the local region's Postgress server.The Management server's Postgres selection algorithm has been optimized so that it connects to a Postgres node in local region
Log messages when Message Processor reaches its connection limit have been improved. This simplifies troubleshooting.
Customer dc-4 expansion failed due to custom region name.A new property,
Added an optional feature to make developer emails case insensitive.This feature is turned off by default, so developer emails continue to be case sensitive (the current behavior).
Analytics API with filter to exclude API proxies was returning an error.An issue with parsing filters during execution of custom reports has been fixed.
Management update was failing when Cassandra JMX Authentication or SSL was enabledAdded feature to provide Cassandra JMX authentication and SSL configurations when running setup or update on Management server.
When creating a shared flow in the Edge UI, the UI was returning a 403 error for insufficient permissions.Fixed an undefined value that was being passed to the API.
Made improvements in JMX configurations of Cassandra so configurations follow other Apigee configuration standards and changes are not overridden during Cassandra upgrade.
An IP command was not prefixed with the absolute path.The absolute path is now included in the command.
Misformatted numbers within a component's .properties file were causing the component to fail to startThis has been fixed.
PostgreSQL PassTheHash protocol design vulnerability, by PostgreSQL to Postgres v10.17This has been fixed.
Made enhancements to improve performance of analytics queries on Management Server
Added a Router level configuration to disable Virtual Host listen options on standard ports 80 & 443.
Get org would return a 403-unauthorized error instead of 404-not found if org is not present.
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 Private Cloud.
Vulnerability: [Denial of Service (DoS)] found in for project: unified-experience/navbar (SNYK-JAVA-COMTYPESAFEAKKA-32493). This has been fixed.
Cross-Site Scripting (XSS) vulnerability in jQuery. A vulnerability in jQuery which reported cross-site scripting (XSS) was fixed.
Vulnerability in Tomcat servlet. Existing Tomcat servlet 8.0.53 had a security vulnerability. Upgrading Tomcat servlet to 8.5.34 fixed this vulnerability.
The following table lists known issues in this release:
As a workaround, install
See Known issues with Edge for Private Cloud for a complete list of known issues.
To get started with Edge for Private Cloud 4.51.00, use the following links: