Date of version: November 14, 2024
This document contains New Features, Important Enhancements, Modifications and Bug Fixes for version 2024.09.2.
ATTENTION With the version upgrade of the JDK used by Apinizer, the usage of the JVM parameter “-XX:MaxRAMPercentage” has changed. Since this value, which used to allow the use of Integer type data (-XX:MaxRAMPercentage=75), now expects values as Double (-XX:MaxRAMPercentage=75.0), the old values must be updated to decimal in the yaml file. If the update is expected to be done by Apinizer manager, the pods will need to be restarted after Apinizer manager is opened. Otherwise, this field should be corrected as decimal number by manually modifying the deployments. Bkz.
New Features
APNZ-4684 Added new parameters for CORS and XFF settings if OAuth2 or JWT token retrieval is managed with credential. Bkz.
APNZ-4605 Certificate operations (creation, update, query, deletion) can be performed with the Management API. Bkz.
Important Enhancements and Modifications
APNZ-4666 The JDK version used by Apinizer has been upgraded to the latest version JDK 1.8.
APNZ-4666 Apinizer images can be run as rootless in Kubernetes or OpenShift.
APNZ-4692 The type of the API added to the API Portal was made visible on the portal page.
APNZ-4679 API Product can be registered with more than one App in API Portal.
Bug Fixes
| Issue No | Description |
|---|
| APNZ-4675 | Audit logs cannot be written to the connectors. |
| APNZ-4681 | The accept-encoding value in the request header breaks the response processing during routing. |
| APNZ-4677 | The names of the roles in the API portal have been edited to be standard. |
| APNZ-4645 | The request body added from the Design tab is not reflected in the test console in the portal. |
| APNZ-3078 | When an API Product is deleted in the API Portal, the subscription should be deleted. |
| APNZ-4680 | In the OPTIONS response, CORS headers were not visible in the logs. |