22.03.14 - Apigee Edge for Public Cloud release notes

Latency was improved for app creation when multiple API products are included in the payload.

Improved deployment time for a proxy bundle with a large OAS resource file.

Use the correct allowed duration for the freemium rate plan in Apigee Monetization.

An issue was fixed to ensure that the freemium duration is respected by Apigee Monetization. With this fix, app developers can use the rate plan for free during the configured duration. Before this fix, the duration was being calculated incorrectly on the backend. See Configure a freemium plan.

The SwaggerParser library upgrade throws stricter validation errors during proxy deployment for the OASValidation policy.

An issue was fixed where turning on Apigee debug caused the runtime to skip some asynchronously executed policies.

An issue was fixed where in the GenerateJWT policy, when specifying jwk as an additional header claim, the policy did not correctly handle the payload.

When a forward proxy was used between the Message Processor and Target server, inconsistent target details were captured in analytics. Target details in analytics were sometimes of the actual target and sometimes of the proxy. This issue was fixed so target details captured in analytics are always those of the actual target.

An issue was fixed in the DecodeJWT policy where when declaring AdditionalClaims as map and adding a claim inside <AdditionalClaims>....</AdditionalClaims>, the policy decoded them as double instead of integer types.

Improved resilience and logging of DNS management code in message processors.

An issue was fixed where the VerifyJWT policy did not allow the use:sig attribute in the JWKS public key. Now, the use:sig attribute is allowed.

An issue was fixed where requests to the Python callout in a shared flow failed due to java.lang.NoClassDefFoundError.

OAS validation errors now throw HTTP 400 status; previously, 500 status was thrown.

Miscellaneous Security updates and fixes.

An issue was fixed where a failure to connect to a Syslog server could cause the MP to restart.

An issue was fixed where a JavaScript policy would fail to execute if it attempted to modify the variable apigee_javascript.

An issue was fixed where the DeleteOAuthV2Info policy was failing to remove the access token.

An issue was fixed where a message processor would sometimes boot up successfully even though it was not able to load all underlying repositories.

An issue was fixed where permissions containing both a wildcard (*) and a special character, such as a comma (,) did not work as expected.

A proxy revision was returning an HTTP 400 status error when used as a target with LocalTargetConnection.

The Message Processor will now reuse existing target IPs once if DNS resolution fails during DNS cache refresh.

The flow variable servicecallout.requesturi reflects appropriately if the URI is constructed using multiple variables.

An issue was fixed where the AccessControl policy reported errors when x-forwarded-for headers contained ip:port format.

An issue was fixed where JWS policy threw a steps.jws.GenerationFailed error when the last JSON parameter was empty.