22.03.14 - Apigee Edge for Public Cloud release notes

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

On the following dates, we began releasing component updates to Apigee Edge for Public Cloud:

  • Management Server: March 30, 2023
  • Message Processor: June 12, 2022
  • Router: May 10, 2022
  • Management Server: April 28, 2022

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
260223013 Management Server

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

195356975 Management Server

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

205056475 Management Server

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.

195356975 Message Processor

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

221313205 Message Processor

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

216482436 Message Processor

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.

213320910 Message Processor

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.

213089299 Message Processor

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.

197945951 Message Processor

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

195619555 Message Processor

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.

193450469 Message Processor

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

184389140 Message Processor

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

182386219 Message Processor

Miscellaneous Security updates and fixes.

181923677 Message Processor

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

180664016 Message Processor

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

180576871 Message Processor

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

177305642 Message Processor

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

174970453 Message Processor

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

174850082 Message Processor

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

173566787 Message Processor

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

159599332 Message Processor

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

158572674 Message Processor

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

143970302 Message Processor

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