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

On Friday, March 16, 2018, we released a new version of Apigee Edge for Private Cloud.

> [!NOTE]
> **Note:** **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).
>
> [Release notes home page](https://docs.apigee.com/release/notes/apigee-release-notes)

## Update procedure

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

1. On all Edge nodes:

   1. Clean Yum repos:  

      ```
      > sudo yum clean all
      ```
   2. Update the Edge 4.17.09 `bootstrap_4.17.09.sh` file in `/tmp/bootstrap_4.17.09.sh`:  

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

      ```
      > sudo bash /tmp/bootstrap_4.17.09.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. Source the `apigee-service.sh` file:  

      ```
      > source /etc/profile.d/apigee-service.sh
      ```
2. Update all Edge Management Server nodes:  

   ```
   >/opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
   ```
   where ***configFile*** specifies the config file you used to install Edge.
3. Update all Edge UI nodes:  

   ```
   >/opt/apigee/apigee-setup/bin/update.sh -c ui -f configFile
   ```
4. Update all Router Message Processor nodes:  

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

## Bugs fixed

The following bugs are fixed in this release.

> [!NOTE]
> **Note:** The build number in the table specifies the earliest version of the component that contains the fix. Use that build number to determine if you already have the fix installed, or if you need to perform an update. The apigee-service utility displays the build number of the currently installed component:
>
> ```
> /opt/apigee/apigee-service/bin/apigee-service comp version
> ```
>
> where ***comp*** is the name of the component without the build number
> extension. For example:
>
> ```
> /opt/apigee/apigee-service/bin/apigee-service apigee-setup version
> ```
>
> or get the build number of all components:
>
> ```
> /opt/apigee/apigee-service/bin/apigee-all version
> ```

| Issue ID | Description | Build number |
|---|---|---|
| 68329105 | **Portal setup action fails to create a user when connecting to `apigee_sso` when `apigee_sso` uses a self signed cert.** | `apigee-drupal-devportal-4.17.09-0.0.244.noarch.rpm` |
| 68858244 | **Edge UI with TLS terminated on an ELB, constructs an OAuth logout redirect URL using the HTTP protocol instead of HTTPS.** | `edge-ui-4.17.09-0.0.20024.noarch.rpm` |
| 69001358 | **Edge SSO can now connect to the Management Server over HTTPS when the Management Server uses a self-signed cert.** | `apigee-sso-4.17.09-0.0.10088.noarch.rpm` |
| 69377379 | **Message Processor now closing SSL sockets correctly** The Message Processor now closes SSL sockets correctly to reduce the number of CLOSE_WAIT connections. | `edge-gateway-4.17.09-0.0.1524.noarch.rpm` |
| 69711616 | **Updated Jackson Databind to version 2.7.9.1 in the third-party JARs.** | `edge-gateway-4.17.09-0.0.1524.noarch.rpm` |
| 70719754 | **Edge Router and Message Processor can throw Out Of Memory errors after upgrade to 4.17.09** | `edge-gateway-4.17.09-0.0.1524.noarch.rpm` |