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

On Wednesday, August 14, we will begin releasing a new version of Apigee Edge integrated portal.

> [!NOTE]
> **Resources** :
>
> - **Questions or issues?** Contact [Apigee Edge Support](https://docs.apigee.com/api-platform/troubleshoot/support)
> - Subscribe to release notifications: See [Get Apigee Edge release notifications](https://docs.apigee.com/release/get-release-notifications).

## New features


The following section summarizes the new feature in this release.

### Configure a content security policy


Configure a content security policy (CSP) for all pages in your portal to protect against cross-site scripting (XSS) and other code-injection attacks. The CSP defines trusted sources for content such as scripts, styles, and images. After configuring a policy, content loaded from untrusted sources will be blocked by your browser.
For more information, see [Configure a content security policy](https://docs.apigee.com/api-platform/publish/portal/csp).

## Bugs fixed

The following bugs are fixed in this release. This list is primarily for users checking to see
if their support tickets have been fixed. It's not designed to provide detailed information for
all users.

| Issue ID | Component Name | Description |
|---|---|---|
| 138844469 | Integrated Portal | **500 Internal Server Error when sign in on Safari** An issue has been fixed that was causing a redirect to a 500 internal server error page when signing in using the Safari browser (even when user signed in successfully). |
| 138303909 | Integrated Portal | **API image path problem** Uploading a new image it the API settings dialog would cause images paths for other APIs to change to `/files/files`. This issue has been fixed. |
| 138286313 | Integrated Portal | **Customer cannot assign domain restriction on developer program** When configuring the account restrictions for a built-in identity provider, an error was displayed when saving the configuration. This issue has been fixed. |