16.01.20 - Apigee Edge for Public Cloud release notes

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

On Tuesday, February 2, 2016, we released a new cloud version of Apigee Edge for Public Cloud.

New features and enhancements

Following are the new features and enhancements in this release.

Redesigned API proxy wizard

The API proxy wizard has been redesigned. When you click "+ API Proxy" on the API Proxies page in the management UI, the new wizard guides you through the API proxy creation process. All the same settings as the previous API proxy wizard are available. (MGMT-1376)

Create API proxies with OpenAPI (Swagger) documents

As part of the new API proxy wizard redesign, you can now create an API proxy from a OpenAPI (Swagger) document. On the first page of the API proxy wizard, click Use OpenAPI when selecting Reverse Proxy, Node.js App, or No Target. In the field that appears, enter the URL to your OpenAPI document. For more information, see Build a simple API proxy. (MGMT-1376)

WSDL 1.2 support for SOAP proxies

Apigee Edge supports WSDL 1.2 in creating API proxies to call SOAP services. (MGMT-2835)

SSLInfo variables in TargetEndpoint configurations

In an API proxy TargetEndpoint, you can dynamically set SSL/TLS details to support flexible runtime requirements. In the following example of how SSLInfo would be set in a TargetEndpoint configuration, the values can be supplied at runtime by a Java Callout, a JavaScript policy, or an Assign Message policy. Use whichever message variables contain the values you want to set.

<TargetEndpoint>
...
  <SSLInfo>
    <Enabled>{myvars.ssl.enabled}</Enabled>
    <ClientAuthEnabled>{myvars.ssl.client.auth.enabled}</ClientAuthEnabled>
    <KeyStore>{myvars.ssl.keystore}</KeyStore>
    <KeyAlias>{myvars.ssl.keyAlias}</KeyAlias>
    <TrustStore>{myvars.ssl.trustStore}</TrustStore>
  </SSLInfo>
...
</TargetEndpoint>

This feature is covered in the following docs:

• API proxy configuration reference
• https://community.apigee.com/articles/21424/dynamic-sslinfo-for-targetendpoint-using-variable.html

(APIRT-1475)

RSA_SHA256 algorithm support for SAML assertion policies

The SAML assertion policies now support the RSA_SHA256 algorithm in addition to RSA_SHA1. (APIRT-1779)

Validation on certificate uploads

To help prevent the uploading of expired or invalid certificates to keystores and truststores, the management API validates certificates on upload. Certificates are validated to ensure that the size of the file is not larger than 50KB and that the format is either PEM or DER. Certificate expiry is also validated. To override the default expiry validation (to not validate for certificate expiration on upload), use the following query parameter: ?ignoreExpiryValidation=true

For more information, see Upload a JAR file to a Keystore and Upload a Certificate to a Truststore. (SECENG-516) and (APIRT-2213)

Auto-polling on Node.js Logs page

When viewing Node.js logs from the proxy editor, the Node.js Logs page is automatically refreshed periodically to list new logs that are available. Click "Stop Auto Refresh" to turn off auto-refresh. (MGMT-1692)

API product page performance, no developer apps listed

When viewing an API product in the management UI, the developer apps associated with that product are listed. To improve UI performance, the list of developer apps is not shown when editing the API product. (MGMT-2869)

Subscription to daily analytics emails

Organization administrators must now explicitly subscribe to daily analytics report emails. Subscribe/unsubscribe by setting a user preference in the management UI, or with the management API. For more information, see Subscribe to daily analytics emails. (AXAPP-1949)

sum( ) function on response time metrics

In analytics custom reports and API calls, the "sum" aggregate function is now available for Target Response Time, Total Response Time, and end_point_response_time. For example, in the /stats API (/management/apis/get/organizations/%7Borg_name%7D/environments/%7Benv_name%7D/stats/%7Bdimension_name%7D-0), you can now use the following "select" query parameter: ?select=sum(total_response_time). (AXAPP-2006)

Latency Analysis report: API proxy names sorted

In the Latency Analysis report UI (Apigee Edge enterprise plans only), the API proxies are listed alphabetically in the Proxy drop-down list. (MGMT-2858)

Developer Apps on dashboard shown by display name

On the management UI dashboard, the Developer Apps bar chart lists developer apps by display name rather than internal name. (MGMT-2853)

New date/time widget on custom reports

The date/time picker widget on a custom reports page in the management UI has been enhanced. (MGMT-2881)

Monetization: Edit API package names

You can update the name of an API package at any point during the monetization lifecycle, even when the API package contains a published rate plan. (DEVRT-2177)

Monetization: Decimals allowed in custom attributes

When using a "Rate Card with Custom Attribute" plan, the custom attribute in the message header that is used as a multiplier for the transaction can now be a decimal value of up to four decimal places. For more information on this type of plan, see Specify rate card custom attribute details. ( DEVRT-2191)

General improvements

This release also contains multiple usability, performance, security, and stability enhancements.

Bugs fixed

The following bugs are fixed in this release.