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

On Sept. 29, 2020, we released a new version of Apigee Edge for Private Cloud.

> [!NOTE]
> For more information, see the following resources:
>
> - *[Edge for Private Cloud 4.50.00
>   documentation](https://docs.apigee.com/private-cloud/v4.50.00)*
> - *Questions or issues?* Contact [Apigee Edge Support](https://docs.apigee.com/api-platform/troubleshoot/support)
> - *Release notifications* : See [Get Apigee Edge release notifications](https://docs.apigee.com/release/get-release-notifications)

## Update procedure

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

- edge-gateway-4.50.00-0.0.20093.noarch.rpm
- edge-management-server-4.50.00-0.0.20093.noarch.rpm
- edge-message-processor-4.50.00-0.0.20093.noarch.rpm
- edge-postgres-server-4.50.00-0.0.20093.noarch.rpm
- edge-qpid-server-4.50.00-0.0.20093.noarch.rpm
- edge-router-4.50.00-0.0.20093.noarch.rpm
- edge-analytics-4.50.00-0.0.40031.noarch.rpm
- apigee-mtls-4.50.00-0.0.20187.noarch.rpm
- apigee-mtls-consul-4.50.00-0.0.20127.noarch.rpm
- apigee-cassandra-2.1.16-0.0.2509.noarch.rpm
- apigee-sso-4.50.00-0.0.20079.noarch.rpm
- edge-ui-4.50.00-0.0.20165.noarch.rpm

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.50.00 `bootstrap_4.50.00.sh` file to `/tmp/bootstrap_4.50.00.sh`:

      ```
      curl https://software.apigee.com/bootstrap_4.50.00.sh -o /tmp/bootstrap_4.50.00.sh
      ```
   3. Install the Edge 4.50.00 `apigee-service` utility and dependencies:

      ```
      sudo bash /tmp/bootstrap_4.50.00.sh apigeeuser=uName apigeepassword=pWord
      ```

      Where <var translate="no">uName: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. 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 all Cassandra nodes:

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

   where <var translate="no">configFile</var> specifies the configuration file that you used to install
   Apigee Edge for Private Cloud. For example, `/opt/silent.conf`.
3. On all Edge nodes, execute the `update.sh` script for the `edge` process. To do this, execute the following command on each node:

   ```
   /opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
   ```
4. 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
   ```
5. 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
   ```
6. If you are using Apigee mTLS, follow the procedure described in [Upgrade Apigee mTLS](https://docs.apigee.com/private-cloud/v4.50.00/mtls-upgrade).

   For more information, see [Introduction to Apigee mTLS](https://docs.apigee.com/private-cloud/v4.50.00/mtls-intro).

## Supported software

No changes.

## Deprecations and retirements

No new deprecations or retirements.

## New Features

This section lists new features in this release.

### Encrypting JMX passwords

You can now encrypt JMX passwords. See
[Enabling JMX password encryption](https://docs.apigee.com/private-cloud/v4.50.00/how-monitor#enable-jmx-password-encryption) and
[Enabling JMX authentication for Cassandra](https://docs.apigee.com/private-cloud/v4.50.00/how-monitor#cassauthenable) for details. (150633039)

## Bugs fixed

The following table lists the bugs fixed in this release:

| Issue ID | Description |
|---|---|
| 135972575 | **Edge for Private Cloud was showing different behavior during deployment with `override=true&delay=300`**. This has been fixed. |
| 163578296 | **The [axstatus API](https://docs.apigee.com/private-cloud/v4.50.00/how-monitor#postgresserver-usingedgeapplicationaxstatuscheck) was incorrectly reporting failure status for a fresh installation.** This has been fixed. |
| 160955355 | **The UI Trace session did not match the trace session log: policies executed between two service callouts were missing.** This was happening because some policies were being saved and dispatched in the wrong order. This has been fixed. |
| 147736003 | **An outdated library on enterprise.apigee.com was causing security issues.** The library has been updated. |
| 161858295 | **Some silent variables were misspelled.** Silent install variable `SSO_JWT_SIGNING_KEY_FILEPATH` is no longer misspelled. |
| 160951701 | **mTLS installation was failing due to an outdated Consul binary version.** The Consul binary has been upgraded from v1.6.2 to the latest stable version, v1.8.0. <br /> |
| 160916451 | **mTLS installation was failing due to a missing entry for the Consul `bindaddr` field.** apigee-mtls now properly handles servers with multiple network interfaces and addresses. |

## Known issues

The following table lists known issues in this release:

| Issue ID | Description |
|---|---|
| 149245401 | **Ldap policy connection pooling issue** LDAP connection pool properties specified using [LDAP resource](https://docs.apigee.com/api-platform/reference/policies/ldap-policy) are not taking effect. As a result, connections are being opened and closed each time for single use, creating a large number of connections per hour to the LDAP server. **Workaround:** In order to change the LDAP connection pool properties, do the following steps to set a global change across all LDAP policies. 1. Create a configuration properties file if it does not already exist: ``` /opt/apigee/customer/application/message-processor.properties ``` 2. Add the following to the file (replace values of Java Naming and Directory Interface (JNDI) properties based on your LDAP resource configuration requirement). ``` bin_setenv_ext_jvm_opts="-Dcom.sun.jndi.ldap.connect.pool.maxsize=20 -Dcom.sun.jndi.ldap.connect.pool.prefsize=2 -Dcom.sun.jndi.ldap.connect.pool.initsize=2 -Dcom.sun.jndi.ldap.connect.pool.timeout=120000 -Dcom.sun.jndi.ldap.connect.pool.protocol=ssl" ``` 3. Make sure the file `/opt/apigee/customer/application/message-processor.properties` is owned by apigee:apigee. 4. Restart each message processor. To verify that your connection pool JNDI properties are taking effect, you can perform a tcpdump to observe the behavior of the LDAP connection pool over time. > [!NOTE] > **Note:** Connection pool properties specified by the above procedure are global, and so are applicable to all connection-pool-enabled LDAP connections that Apigee's Message Processor establishes. |