Version 2024.09.0 Release
Date of version: September 9, 2024
This document contains New Features, Important Enhancements, Modifications and Bug Fixes for version 2024.09.0.
WARNING! For users updating from the 2024.05.3 Patch version, the ability to select multiple API Proxies in the API Proxy Group has been enabled. With this setting, the feature that previously allowed policies in the API Proxy Group to be applied to API Proxies has been removed.
WARNING! For users updating from the 2024.05.4 Patch version, with the implemented security update, it has been made mandatory to check the value of client IP addresses in browsers on the Apinizer Management Console. Therefore, the requirement for organizations connecting to the interface using the "Kubernetes Ingress Controller" to send the client IP information via the X-Forwarded-For header has been removed.
New Features
APNZ-4381 Specs can be downloaded in API Portal.
APNZ-4553 New policies added in Management APIs. See.
Important Enhancements and Modifications
APNZ-4523 With the disable routing button, a service loaded with a definition file can be run without going to the backend. See.
APNZ-4564 Routing disabled was printed in the routing address field of the proxies to be used as mirror. See.
IMPORTANT! When creating an API Proxy, the selected Mirror API has been deprecated and removed in this version. Configuration can now be done in the API Proxy Routing section.
APNZ-4534 The actions that can be performed in the API Proxy and API Proxy Group Development sections have been customized for each line. See.
APNZ-4199 The active/passive button in the Connection Configurations has also been added to the listing screen. See.
APNZ-4269 The information that the result is returned as top1/limit1, which is not visible in get queries, has been added to the DB-2-API try it screen as a warning. See.
APNZ-4378 Apiops can be completely shut down. See.
APNZ-4442 In case global policies are also used in the Proxy Group, the list of those used in the Proxy Group has been added.
APNZ-4452 In the API Portal endpoint test, selecting an application now automatically provides the Auth information. See.
APNZ-4456 When initializing the cache, loading of previous quota data from the database can now be done either lazily or eagerly. See.
APNZ-4524 Production and Test fields have been added to Gateway Environments. See.
APNZ-4528 The “enable” button in Connections has been standardized in tables.
Bug Fixes
Issue No | Description |
---|---|
APNZ-4562 | The WSDL example file size limit set in the general settings is not reflected in the Rest2Soap configuration. |
APNZ-4559 | In the API Portal Test Console, the body content is coming with old data and is not being updated. |
APNZ-4558 | When general settings are saved, the LogRetentionSetting configuration is being deleted. |
APNZ-4549 | A method cannot be opened in Rest2Soap. |
APNZ-4546 | When an endpoint is edited and the method name is changed, the body content in the design is lost. |
APNZ-4545 | When the error handling type is not set to default and the backend connection fails, the status code is not set. |
APNZ-4552 | API Portal Issues:
|
APNZ-4553 | ApinizerKubernetesClientService cannot read k8s metrics. |
APNZ-4540 | When using the latest version (2024.05.4) with a zero database, the necessary database tables are not being created. |
APNZ-4537 | When exporting the project in the test environment, the appearance of error messages in global policies in the production environment is empty due to the different IDs of error messages. |
APNZ-4525 | Having meaningful characters in the name of the exported data in the file system is causing the export file to become corrupted. |
APNZ-4544 | Issues arising from increased concurrency in XML operations should be resolved. |
APNZ-4507 | The authentication policy exported from the proxy group gives a null error when imported into the proxy. |
APNZ-4529 | When adding a key in the Secret Manager, selecting 'private' or 'public' options does not enable the buttons. |
APNZ-4521 | In the Credentials screen, the Account filter section does not show Account's. |
APNZ-4435 | When deploying or undeploying in the API Proxy Group, the endpoints' URLs are not updated without refreshing the page |
APNZ-4518 | Portal quick test issues:
|
APNZ-4516 | In Integration, jobs in the 'disabled' state are being triggered and remain in the 'in progress' state. |
APNZ-4536 | In the Alert History screen, the date and sorting are not working correctly. |
APNZ-4512 | Manager health check should be performed using the HTTPS protocol. |
APNZ-4511 | The membership model selection field in the portal should be fixed. |
APNZ-4510 | In Rest2Soap operations, namespaces are not being added to values sent as null. |
APNZ-4506 | When importing an authentication policy exported from one proxy group to a different proxy group, although a successful response is returned, the policy is not visible. It is unclear whether the policy has been added, and even after refreshing the page, the policy still does not appear. |
APNZ-4358 | Path parameters are not visible in the API Proxy design tab. |
APNZ-4351 | After performing the logout operation, when logging in again, the last record deletion operation remains open in front of the project selection popup. |
APNZ-4520 | Routing NTLM Authentication configuration is not working. |
APNZ-4502 | The cache is opening slowly and unnecessarily pinging a public IP address. |
APNZ-4569 | The issue of environments occasionally failing to load in the API Proxy analytics tab should be resolved. |
APNZ-4508 | An issue occurs in the JWT policy when 'LDAP API Authentication' is selected and the LDAP API Authentication definition is deleted. |
APNZ-4533 | When exporting a project, some connections are missing. |
You can review the relevant document for detailed information about the New Features, Important Changes, and Improvements introduced with Version 2024.05.3 Patch and Version 2024.05.4 Patch: