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

On Tuesday, May 7th, we will begin releasing a new version of Apigee Edge for Public Cloud and integrated portals.

> [!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 sections summarize the new features in this release.

- [Beta release of self-service SAML configuration for Apigee Edge and integrated portals](https://docs.apigee.com/release/notes/190507-apigee-edge-public-cloud-release-notes-ui#saml)
- [Developer programs for integrated portals](https://docs.apigee.com/release/notes/190507-apigee-edge-public-cloud-release-notes-ui#developer-programs)
- [Beta release of the developer team and audience management features for integrated portals](https://docs.apigee.com/release/notes/190507-apigee-edge-public-cloud-release-notes-ui#teams-audience-management)

### Beta release of self-service SAML configuration for Apigee Edge and integrated portals

The beta release of self-service Security Assertion Markup Language (SAML) configuration is now available for Apigee Edge and integrated portals. SAML is a standard protocol for single sign-on (SSO) environments.
SSO authentication using SAML enables users to sign in to Apigee Edge or your integrated portals without having to create new accounts.
Users sign in using their existing credentials.

For more information:

- Self-service SAML for Apigee Edge:
  - [SAML Overview](https://docs.apigee.com/api-platform/system-administration/saml-overview)
  - [Enable SAML (Beta)](https://docs.apigee.com/api-platform/system-administration/enabling-saml-authentication-edge)
- Self-service SAML for integrated portals:
  - [Supported authentication types](https://docs.apigee.com/api-platform/publish/portal/intro-developer-program#supported_authentication_types)
  - [Configure the SAML portal identity provider (Beta)](https://docs.apigee.com/api-platform/publish/portal/portal-identity-provider#saml)


### Developer programs for integrated portals

A developer program defines the **identity provider** used for authentication and other aspects of
the user registration and sign-in experience for integrated portals.

For more information, see [Developer program overview](https://docs.apigee.com/api-platform/publish/portal/intro-developer-program).

### Beta release of the developer team and audience management features for integrated portals

The beta release of the developer team and audience management features for integrated portals is now available.

> [!NOTE]
> No SLAs are provided for the beta release of the developer team and audience management features and after you enroll your organization you cannot revert back. Apigee recommends that you limit your use of these beta features in production environments.

| Beta Feature | Description | More information |
|---|---|---|
| Developer teams | Allow portal users to share responsibility for an app with other portal users. | - [Share responsibility for an app using developer teams (beta)](https://docs.apigee.com/api-platform/publish/portal/portal-interact#teams) (portal users) - [Manage developer teams](https://docs.apigee.com/api-platform/publish/portal/developer-teams) (API providers) |
| Audience | Segment individuals in order to control access to content. | [Manage the audiences for your portal](https://docs.apigee.com/api-platform/publish/portal/portal-audience#manage-audience) |

To enroll in the beta release of the developer team and audience management features:

- When [creating a portal](https://docs.apigee.com/api-platform/publish/portal/manage-portals#create-portal), click **Enroll in beta for team and audience management features**.
- When [configuring a developer program](https://docs.apigee.com/api-platform/publish/portal/configure-developer-program), in the beta enrollment banner click **Enroll**.

## 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 |
|---|---|---|
| 131752262 | Integrated Portal | **Once I publish changes to my Home page I see "published 49 years ago" at the bottom** This issue has been fixed to reflect the correct publishing date. |
| 131699837 | Integrated portal | **mat-toolbar not rendering in live portal page content** Fixed issue where use of the mat-toolbar component in page content would prevent the page from rendering. |
| 131425256 | Integrated portal | **Portal not loading in Internet Explorer** Fixed issue where portals would not load in Intenet Explorer. |
| 130291857 | Integrated Portal | **Icon to upgrade Portal has white background** |
| 129766216 | Integrated portal | **Cannot upload new spec from file or URL when publishing** Fixed issue where users could not upload new specs from a file or URL when publishing an API to a portal. |
| 119200785 | Integrated portal | **Support absolute URLs in menu items** Fixed issue where menu items that linked to an asset file would not work properly. |

## Known Issues

This release has the following known issues.

| Component Name | Description |
|---|---|
| Developer programs | In the beta release, if you delete a developer program users will not be able to sign in to the connected portal. You connect to a developer program when you create a portal only; you cannot change the developer program after the portal is created. You will need to re-create your portal in order to connect to a developer program. In a future release, you will be able to edit the developer program to which a portal is connected. |
| Developer teams (beta) | - Portal users can view the developer teams to which they are members on the [Teams page](https://docs.apigee.com/api-platform/publish/portal/portal-interact#explore-teams). For the beta release, no notifications are sent when a portal user is added to a developer team. - Team owners cannot edit their own role or leave a team. - Before deleting a team, you must delete all apps owned by the team. |
| Developer account | When you delete a developer account, the developer record on Apigee Edge is not deleted. Similarly, when you delete a developer program, the developer accounts are deleted, but not their corresponding developer records on Apigee Edge. |
| Portal admin | - Apps with multiple credentials are not supported by the portal at this time. - Simultaneous portal updates (such as page, theme, CSS, or script edits) by multiple users is not supported at this time. - If you delete an API reference page from your portal, there is no way to recreate it; you'll need to delete and re-add the API product. |
| SmartDocs API reference documentation | - The API reference documentation does not handle form parameters properly at this time. - When using Try It, the `Accept` header is set to `application/json` regardless of the value set for `consumes` in the OpenAPI Specification. |
| Portal email notifications | - If a user clicks a time-sensitive link in a notification after the 10-minute expiration, an error is thrown. - If a user clicks the reset password link twice in an email notification, an error is thrown. |
| Specifications | The behavior of remote references in specifications is not guaranteed at this time. |