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

On Monday, March 20, 2017, 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:

1. On all Edge nodes, clean Yum repos:  

   \> sudo yum clean all

2. On all Edge UI nodes, update edge-ui:  

   \>/opt/apigee/apigee-setup/bin/update.sh -c ui -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 |
|---|---|---|
| EDGEUI-28 | **User session not destroyed when user logs out of Edge UI** When a user logs out of the Edge UI, the session cookie for the user is deleted. However, while the user is logged in, malware or other malicious software running on the user's system could obtain the cookie and use it to access the Edge UI. You can configure the Edge UI to store information about current sessions in server memory. When the user logs out, their session information is deleted, preventing another user from using the cookie to access the Edge UI. See [Configure the Edge UI to store session information in memory](https://docs.apigee.com/private-cloud/v4.18.01/configure-edge-ui-store-session-information-memory) for more. | edge-ui-4.17.01-0.0.3814 |
| EDGEUI-656 | **Can now set rules for auto generating passwords in the Edge UI** The Edge UI auto generates user passwords for new users. Users are typically then sent an email that allows them to change the auto generated password. You can now set the rules used to create these passwords. See [Configure rules used to auto generate Edge UI passwords](https://docs.apigee.com/private-cloud/v4.18.01/configure-rules-used-ti-auto-generate-edge-ui-passwords) for more. | edge-ui-4.17.01-0.0.3814 |
| EDGEUI-662 | **Can now set the password hint text in the Edge UI** You can now control the text that appears in the reset password dialog box in the Edge UI. This is useful if you have special requirements on user passwords. See [Setting the password hint text in the Edge UI](https://docs.apigee.com/private-cloud/v4.18.01/setting-password-hint-text-edge-ui) for more. | edge-ui-4.17.01-0.0.3814 |
| EDGEUI-664 | **Edge UI session is now correctly extended when user performs an action** | edge-ui-4.17.01-0.0.3814 |
| EDGEUI-854 | **Specifying session.maxAge in minutes now works** You can now configure the session timeout of the Edge UI in minutes by setting the conf_application_session.maxAge property in the /\<inst_root\>/apigee/customer/application/ui.properties file. | edge-ui-4.16.09-0.0.3814 |