Date of version: June 7, 2024

This document contains New Features, Important Enhancements, Modifications, Removed Features and Bug Fixes for version 2024.05.0.

Removed Features

APNZ-4253 WARNING! The simple method has been removed from the LDAP settings in General Settings. See.

New Features

APNZ-4190 New fields have been added to script and variable context values. See.

APNZ-4197 The Project and Admin Overview pages have been made more interactive.  See1. See2.

APNZ-4202 The ability to access secret values belonging to credentials via script policies has been added. See.

APNZ-4206 Minute-based filtering has been added for API traffic.

APNZ-4220 Logs can now be logged in UDP/TCP using the Graylog GELF format. See.

APNZ-4258 The Manager and portal can now be accessed via HTTPS.

APNZ-4275 An Error Policy line has been added to ensure that the designated policies operate in the event of an error. See.

APNZ-4287 A user_token_blackList object has been for the deletion of old logs. See.

APNZ-4288 The ability for users to log in from multiple tabs/locations simultaneously has been linked to general settings. See.

APNZ-4296 A screen has been added to the system where certificates existing in the truststore can be viewed. See.

APNZ-4300 In the API Portal, dynamic definition of FAQs has been enabled. See.

APNZ-4304 The addition of the Application feature has been enabled on the Portal. See.

APNZ-4305 Documentation&Test tab has been added to the Portal.

APNZ-4334 The Credential screen has been configured to filter according to applications and accounts in the Portal.

APNZ-4337 Tools menu has been added to the Portal.

APNZ-4339 The 'Test User' role has been added. See.

APNZ-4359 Notifications have been included in the purge jobs list in the system. See.

APNZ-4363 Asynchronous execution of script policies has been enabled. See.

Important Enhancements and Modifications

APNZ-3799 When an error is encountered in an API call policy while working unidirectionally, this error can now be reflected in the result of the corresponding API Proxy.

APNZ-3802 In the advanced query field of the API Proxy Traffic screen, search options such as empty/is not empty/exists/not exists/contains/not contains/in list/not in list have been enabled. See.

APNZ-4042 APIs Visibility By Organization screen has been added to Portal Management. See.

APNZ-4217 Lists can now be provided to conditions, enabling the checking of values such as in list and not in list. See.

APNZ-4218 The ability to enter specific days has been added to the time policy. See.

APNZ-4254 When searching for a user with LDAP type in the user screen, if the user is not found, a warning message is displayed.

APNZ-4255 In the LDAP information of the identity provider, when advanced is selected, the object defaults are now maintained, cannot be deleted, and can only be edited.

APNZ-4256 The LDAP Connection within the LDAP provider has been enabled.

APNZ-4270 The titles in the administration panel have been corrected. See. 

APNZ-4282 New values have been added to the values accessible via the script. See.

APNZ-4285 Prevented simultaneous login of two users with the same credentials. See.

APNZ-4295 The option to select the method of hostname verification in secure connections has been introduced.

APNZ-4303 In the Test Console, when there is an issue with the XSLT file, detailed information about the problem is now displayed on the screen.

APNZ-4307 The JWT generated when a user logs into the API Manager has been made smaller in size.

APNZ-4325 When deploying, details are provided regarding which proxy or proxy group the conflict with a relative path occurs.

APNZ-4326 The ability to edit Elasticsearch template settings from the interface has been enabled. See.

APNZ-4331 The configuration of account registration has been made customizable in the API Developer Portal. See.

APNZ-4346 The rollover feature has been added to Elasticsearch operations. See.

APNZ-4347 Performance improvements have been made in the Uptime Monitor and Anomaly screens.

APNZ-4352 The ability to sign the request body as JSON has been added to the Test Console. See.

APNZ-4353 The Key Store, Public Key, Private Key and Certificate fields opened on the JWK screen are now in order and can be searched.

APNZ-4354 Search by organization and alphabetical sorting of names have been implemented on the Credential screen.

APNZ-4355 The certificate is now editable. See.

APNZ-4364 Performance improvements have been implemented in XML transformation policies and protocol transformation.

APNZ-4376 Connection Request Timeout value can be adjusted in Routing. See.

APNZ-4380 Added the ability to sign the request body as WS Security to the Test Console. See.

Bug Fixes

Issue No	Description
APNZ-4309	IMPORTANT! The issue of project information being mixed up when the API manager is opened in different tabs has been resolved.
APNZ-4369	IMPORTANT! There is an error in converting the numerical fields in the response message to text in the REST-SOAP-REST conversion. Large numbers were being displayed in scientific notation in JSON. After this fix, numbers are now being used as they are in the response message. Previously faulty conversion processes will be corrected with this update. However, this may lead to the emergence of previously unnoticed errors. Therefore, we recommend checking your REST-2-SOAP operations.
APNZ-3833	Even when the log level is set to 'off' in application logs, logs continue to be retained.
APNZ-3857	There are issues with Context Values variables.
APNZ-4022	Errors are encountered when routing-based settings such as retry count are used in the Uptime Monitor.
APNZ-4039	When the authorization of an authorized user is revoked, the user is not listed in the analytic graphs.
APNZ-4061	The Report Generator is not functioning.
APNZ-4093	The default value for "Elasticsearch has logs on disk" in alerts has been removed and needs to be re-added.
APNZ-4101	Existing Cron expressions are not being updated.
APNZ-4123	ACL Reports issues, Project list is not appearing Search By Credentials is not working with the desired filtering
APNZ-4138	Even though logging is enabled for error cases, no log entry can be found for requests blocked by White IP when logging is disabled on the proxy.
APNZ-4162	After parsing OpenAPI, it cannot be saved.
APNZ-4174	The integration is being triggered but not making the request.
APNZ-4183	Querying for Elasticsearch disk utilization alarm is not possible.
APNZ-4208	There is a 5-6 second pause on the screens when the project is changed.
APNZ-4210	The error "label" is encountered in the Context Value.
APNZ-4215	LDAP Secure is not functioning.
APNZ-4229	The certificate in the project is not listed in the API Call.
APNZ-4236	Even when anomalies are turned off, 'anomaly detected' continues to be added to the result list.
APNZ-4244	The application logs only retain logs for the last 1 day at most.
APZ-4245	If an environment is linked to a project, when that project is deleted, that environment cannot be accessed on that gateway page.
APNZ-4259	Despite HTTP being disabled in the environment settings, an svc is created in Kubernetes.
APNZ-4260	Purge Jobs process is not working in Application Logs.
APNZ-4262	JWT does not become invalid when an API Manager user logs out.
APNZ-4263	In Rest2Soap transformations, the default data size limit of the Jackson library has been increased from 20MB to an integer limit of 2.1GB.
APNZ-4274	When we expose the service only via HTTPS, the XSD address in the WSDL remains HTTP.
APNZ-4276	Business rule does not work with JWT requests.
APNZ-4294	Adding data to the body with Business Rule works incorrectly.
APNZ-4297	Even if an API is not public, its page can be accessed directly via IP in the Portal. My Account page is not loading in the Portal.
APNZ-4298	HTTP protocol error is encountered when there are multiple cache pods.
APNZ-4308	Default project is not displayed when a user logs into API Manager.
APNZ-4318	An error is encountered when any value is entered for setting the threshold value for disk space fullness alarm.
APNZ-4323	Deletion operation is not working in Redaction. Value cannot be entered in the relevant field during the modification process.
APNZ-4324	An error occurs when certificates without the CN attribute are loaded.
APNZ-4332	In REST to SOAP conversion, the namespace prefix is not added to xsi:nil condition in XML.
APNZ-4335	In the republished environment, the cache service is not being created.
APNZ-4349	If a user logs in via Active Directory and has full privileges in the project, if they try to enter something instead of a name in the connection configuration > database option, and they don't have admin rights, the session is automatically closed.
APNZ-4357	When multiple policies are added to the Error Policy, the order changes. ACL Reports have issues.
APNZ-4358	Path param does not appear in the API Proxy design tab.
APNZ-4360	The policies added to the Error Policy line are not visible in the references of the Global policies.
APNZ-4362	Errors in global policies are not being displayed or updated.