180406 - Apigee Edge for Public Cloud release notes

If no key is associated with a TLS/SSL certificate, the key name is now showing as empty string

The following changes apply to the Get a Keystore or Truststore management API:

• Before the fix, a key name was shown even though no key was associated with a TLS/SSL certificate. Now, if no key is associated with a TLS/SSL certificate, an empty string with double quotes is returned. For example: "keys": [""]. Otherwise, key names are the same as alias names (existing behavior).

• A new response property, aliases, is an array that contains the aliasName, cert, and key for each alias in a keystore or truststore. For example:

  "aliases" : [
      {
          "aliasName" : "myAlias",
          "cert" : "myAlias-cert"
          "key" : "myAlias-key"
      }
  ]
  

  Where key is the aliasName-key.

  In a future release, the existing certs and keys properties will be removed from the response, as the new aliases property includes these.

New functions for helping configure message payloads and strings

Edge includes a predefined set of functions to help you define strings (such as message payloads) in policies such as Assign Message, Java Callout, and Raise Fault. These functions let you:

• Use JSONPath
• Hash values in multiple formats
• Manipulate strings
• Escape and encode characters
• Format times
• Generate IDs, longs, and strings

See Message templates.

Update to JWT policy claims generation behavior

Following are behavior changes for generating claims with the JWT policy, when a claim provides both a default, explicit value and a variable reference to supersede the default value.

• Don't generate a claim when:
  • The referenced variable (ref="variable") on the Claim element is unresolved.
  • The explicit value is empty.
  • The IgnoreUnresolvedVariables element is true.

  The previous behavior was to add a claim with a blank string.

• Generate a claim without an unresolved variable error when:
  • The explicit value on the Claim element is non-null and non-blank.
  • The referenced variable is unresolved.
  • The IgnoreUnresolvedVariables element is any value.

  The previous behavior was to throw an unresolved variable error even when an explicit value existed.

Provide pagination for the List Company Apps management API

In CPS-enabled organizations that use monetization, the List Company Apps management API now includes count and startKey query parameters to control response pagination, where the maximum number of company apps returned is 100.

Enabling Edge router and message processor communication secure as default option

Remove reachable from code and set the field to true always

Handle CPS data in the org wipeout service

Modify the management server code so it reads audit logs from BigQuery

Routers should block calls from the Crimea region and countries which have US sanctions

Separate HTTPClient cache from connection pools to reduce latencies with a large number of random target endpoints

Shared flows are broken in trial pod

ExpiresAt tag is not shown in the app-credentials response for CPS orgs when expiry is -1

sysadmin cannot query org userroles if the org is marked for deletion

NonDistributedBucket should use CompositeFetchRange

Window calculation is wrong for quota with defaultType interval enforcement

FATAL - common-mp-fault-rate tyr-test.apigee.net error

JWT policies cannot accept an audience claim that is a string containing commas

MPs in reu1mp002-3 are being frequently marked down and back up

Description field not updated in PUT call for existent virtualhosts

TLS Disabled virtualhosts updates on Description/Base URL failed for orgadmins

Update vhost with a mismatching keystore reference is successful

Spec URL not populated in the application bean correctly during bundle import

Management API to return HTTP 400 for an OAuth token revoke action when the token is expired

Fix router plugin python script that parses conf.d files

Identity zone should be handled in the org wipeout service

lastModifiedBy value in the proxy meta data to properly reflect with last updated user

Router fails to indicate unhealthy status when the default Nginx configurations are incorrect

Shared Flow showing up in the API proxy list