4.19.06.07 - Edge for Private Cloud release notes

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

On June 5, 2020, we released a new version of Apigee Edge for Private Cloud.

Update procedure

To update your installation, perform the following procedure on the Edge nodes:

On all Edge nodes:
1. Clean the Yum repos:
```
sudo yum clean all
```
2. Download the latest Edge 4.19.06 bootstrap_4.19.06.sh file to /tmp/bootstrap_4.19.06.sh:
```
curl https://software.apigee.com/bootstrap_4.19.06.sh -o /tmp/bootstrap_4.19.06.sh
```
3. Install the Edge 4.19.06 apigee-service utility and dependencies:
```
sudo bash /tmp/bootstrap_4.19.06.sh apigeeuser=uName apigeepassword=pWord
```
  Where uName: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
```
Execute the update.sh script for OpenLDAP on all nodes. On each node, execute the following command:
```
/opt/apigee/apigee-setup/bin/update.sh -c ldap -f configFile
```
Where configFile specifies the configuration file that you used to install Apigee Edge for Private Cloud.
Execute the update.sh script for Edge on all nodes. On each node, execute the following command:
```
/opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
```
Where configFile specifies the configuration file that you used to install Apigee Edge for Private Cloud.
Execute the update.sh script for the UI on all nodes. On each node, execute the following command:
```
/opt/apigee/apigee-setup/bin/update.sh -c ui -f configFile
```
Where configFile specifies the configuration file that you used to install Apigee Edge for Private Cloud.
Execute the update.sh script for SSO on all nodes. On each node, execute the following command:
```
/opt/apigee/apigee-setup/bin/update.sh -c sso -f configFile
```
Where configFile specifies the configuration file that you used to install Apigee Edge for Private Cloud.
Execute the update.sh script for the Developer Portal on all nodes. On each node, execute the following command:
```
/opt/apigee/apigee-setup/bin/update.sh -c dp -f configFile
```
Where configFile specifies the configuration file that you used to install Apigee Edge for Private Cloud.
If you use Apigee mTLS and updated your configuration based on new features or bug fixes in this patch, you must uninstall and then reinstall the apigee-mtls service on all nodes for these changes to take effect. For more information, see Change an existing apigee-mtls configuration.

Supported software

Apigee Edge for Private Cloud has confirmed support for OpenJDK version 1.8.0.252.

Tomcat has been updated to version 7.0.103.

Deprecations and retirements

No changes.

New Features

The following table describes new features in this release:

Description

Description
mTLS secures Management Server to Router connection Apigee mTLS now supports the connection between the Management Server and the Router on port 8081.
Certificate validity duration is now configurable When you use a custom certificate, you can set the number of days in which the certificate is valid. You do this by setting the value of `APIGEE_MTLS_NUM_DAYS_CERT_VALID_FOR` in your configuration file. The default value is 365. For more information, see Step 1: Update your configuration file. If you make a change after installing Apigee mTLS, be sure to follow the instructions in Change an existing apigee-mtls configuration.

mTLS secures Management Server to Router connection

Apigee mTLS now supports the connection between the Management Server and the Router on port 8081.

Certificate validity duration is now configurable

When you use a custom certificate, you can set the number of days in which the certificate is valid. You do this by setting the value of APIGEE_MTLS_NUM_DAYS_CERT_VALID_FOR in your configuration file. The default value is 365. For more information, see Step 1: Update your configuration file. If you make a change after installing Apigee mTLS, be sure to follow the instructions in Change an existing apigee-mtls configuration.

Bugs fixed

The following table lists the bugs fixed in this release:

Issue ID	Description
154428338	Message Processor fails to load environments when keystores are configured with similar names or aliases. We have fixed a regex lookup conflict when loading keystores that have similar naming convention. This was causing the Message Processor to fail to load environments associated to the keystore, or fail to start when multiple conflicting keystores were returned during the lookup.
130653816	Intermittent 404 errors in runtime traffic. A race condition was causing Message Processors to not load all proxies at bootup, resulting in intermittent 404 ApplicationNotFound errors in runtime traffic. This has been fixed.
157275131	Drupal upgrade The Developer Portal upgrade process was broken in version 4.19.06.
155840972	Tomcat upgrade Tomcat was upgraded to version 7.0.103.
155595660	Timezone format The values used for the `sss` and `SSS` tokens in the timezone format set by the `conf_system_apigee.syslogger.dateFormat` property were not correct.
155340541	OpenJDK support Apigee has confirmed support for OpenJDK version 1.8.0.252.
155105930 76087166	KVMs in multi-data center environments The Management Server was randomly connecting to any of the datacenters if an organization spanned multiple datacenters (for example, dc-1, dc-2). This affected connections to the Cassandra nodes in the local data center for key management and Key Value Map (KVM) operations.
152382545	mTLS port range usage The documentation now correctly states that the ZooKeeper port range for Apigee mTLS begins at 10001.
150717738	Clusters with no leader Clusters without a leader prevented the mTLS service from being stopped or restarted. The timeout length has been reduced as well.
148486685	Indirect bind OpenLDAP replication and SSO interoperability With indirect binding, the OpenLDAP service was not searching the user object when replication was enabled (there was more than one OpenLDAP instance).
148179907	apigee-analytics-collector re-added The apigee-analytics-collector utility was re-added. This utility lets you report the API volume count.
146511254	ExtractVariables policy not throwing errors When an XML variable was not resolved via an XPath expression, the ExtractVariables policy continued to execute in the proxy. This occurred even when the `IgnoreUnresolvedVariables` element or the `continueOnError` attribute were set to false.
130013746	Deactivating companies The button to de-activate companies from Monetization was unavailable.
120799182	OpenLDAP upgrade The process for upgrading OpenLDAP in a multi-datacenter environment resulted in a corrupted state.
145236083	Sysadmin username:password length A Sysadmin username:password longer than 57 characters caused an Edge SSO installation script to fail.
135616498	SSO setup script failure An issue was fixed where using file-scheme URLs caused SSO setup script failure.
111420263	Fix ConcurrentModificationException in message logging policy Eliminate several race conditions that occur when using message logging policy.

4.19.06.08

4.19.06.06