17.04.24 - Apigee Edge for Public Cloud release notes (API Management)

You're viewing Apigee Edge documentation.
Go to the Apigee X documentation.

On Wednesday, May 3, 2017, we began releasing a new version of Apigee Edge for Public Cloud.

New features and updates

Following are the new features and updates in this release.

New virtual host attribute

A new attribute called baseUrl has been added to virtual host description in Apigee Edge. This attribute supports overriding the runtime URL that the Edge UI renders for any selected proxy. Users with any one or more of the below configurations can benefit by using the new baseUrl attribute:

  • SSL termination occurs at a load balancer

  • Port mapping occurs between a load balancer and Apigee routers

  • A load balancer configured with path rewriting

Here's an example showing the virtual host object with the new baseUrl attribute. In this example, the value https://api.mycompany.com would appear in the Edge UI:

{ "hostAliases" : [ "<ORG>-<ENV>.apigee.net"],
   "interfaces" : [ ],
   "name" : "default", 
   "port" : "9001",
   "baseUrl" : "https://api.mycompany.com" 

If the baseUrl parameter is not set, then the default URL rendered by the Edge UI will appear as: http://<ORG>-<ENV>.apigee.net:9001/, whereas actual host alias setup is https://api.mycompany.com. Notice in this example the user choose to terminate SSL at the load balancer level and also chose low port 443 to high port 9001 mapping. (MGMT-644)

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 Description
MGMT-3977 A security fix was made related to user permissions.