20.03.27 - Apigee Edge for Public Cloud release notes

On Friday, March 27, we released a new version of Apigee Edge for Public Cloud.

New features and enhancements

This section describes the new features and enhancements in this release.

New HMAC security policy

The HMAC policy is now available within the security category. The HMAC policy uses a secret key and a hash function (such as, SHA256) to produce a keyed message authentication code (MAC). It can be used to check a message for integrity.

The sender computes the HMAC and transmits it along with the policy to the receiver. The receiver uses the shared secret key to compute the HMAC and verify whether the values match. Matching values indicate two things: the message has not changed since it was signed and sent, and the signer has the same shared key.

The default HMAC policy is shown below:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<HMAC name="HMAC-1">
    <DisplayName>HMAC-1</DisplayName>
    <Algorithm>SHA-256</Algorithm>
    <Message ref="variable_containing_message">abc</Message>
    <SecretKey ref="private.secretkey"/>
    <Output>hmac_value</Output>
</HMAC>

To attach the policy using the UI, see Attaching and configuring policies in the UI.

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
139840439 Edge UI

Incorrect tooltip for request and response sizes

When viewing analytics, the tooltip indicated that the request and response sizes were measured in Kilobytes. Request and response sizes are reported in bytes; the tooltip has been updated.

137346253 Edge UI

New Conditional Flow dialog not displaying operations for OpenAPI Specification v3.0

If you generated an API proxy from an OpenAPI Specification version 3.0, the following error was displayed when attempting to add a new conditional flow using the specification:
Every Swagger operation already has a corresonding conditional flow

This issue has been fixed; OpenAPI Specfication version 3.0 is now supported when adding conditional flows to your API proxy.