Version 2025.07.5 LATEST VERSION

Publication Date :  September 5, 2025

NEW FEATURES  

• The Reverse Proxy should provide access to the client's definition file. (Previously, the Reverse Proxy on Apinizer definition file was accessed).

BUG FIXES

• APNZ-5207: The case sensitivity issue encountered when accessing API proxies within an API Proxy Group through the API Proxy Group should be resolved.
• APNZ-5208: A class not found error is received when parsing the WSDL.

Version 2025.07.4 

Publication Date :  September 1, 2025

NEW FEATURES  

• The Microsoft MSSql database JDBC library used in the Apinizer API Creator module has been updated to version 13.2.0.jre8.

BUG FIXES

• APNZ-5201: The packages of the ApinizerBasicHeader and EnumHttpRequestMethod classes, which can be used in the script policy, have been edited, so precautions should be taken to prevent impact on the user organizations.
• APNZ-5202: When Redirect is enabled, an error is received regarding the logging of the Server Streaming response status code.

Version 2025.07.3 

Publication Date :  August 26, 2025

BUG FIXES

• APNZ-4947: The authorize button should not be clicked without making a selection in the pop-up that appears under the authorize button in the API Portal.
• APNZ-5183: Chatbot integration is not working in the API Portal.
• APNZ-5169: Requests sent with authorization in the API Portal are not displayed in the API traffic tab.
• APNZ-5184: Only 12 Products can be displayed on the API Manager's API Portal administration page, the rest are filtered.

Version 2025.07.2 

Publication Date :  August 7, 2025

NEW FEATURES  PREVIEW

• We added the MCP server feature to our Apinizer API Portal product, thus creating a bridge where defined APIs can be automatically accessed by artificial intelligence.

Version 2025.07.1 

Publication Date :  August 5, 2025

BUG FIXES

• APNZ-4488: An extra / character is added before the relative path in the Excel export on the API proxy page.
• APNZ-4706: In the Excel export on the API proxy page, when multiple environments are defined, only the address of the first environment is reflected.
• APNZ-5156: When duplicating a SOAP type service, the sample body does not appear in the Test Console.
• APNZ-5157: Numeric values are converted to scientific notation format during Rest2Soap request transformation.
• APNZ-5158: In RestToSoap, the namespace prefix is missing or removed on elements marked with xsi:nil.

Release 2025.07.0 

Publication Date : July 24, 2025

Version 2025.04.5  

Publication Date : June 20, 2025

IMPORTANT IMPROVEMENTS AND CHANGES

• The message body abbreviation unit in the connector log settings under Environment has been updated to bytes instead of KB for more precise control. 

BUG FIXES

• When the server stream feature is activated, there is a problem in processing form-data content and displaying logs properly.

Version 2025.04.4

Publication Date : May 26, 2025

NEW FEATURES  PREVIEW

• Developments should be made to enable JMS connection, consume and produce operations running on Weblogic server with Script policy.

Version 2025.04.3

Publication Date : Mayıs 17, 2025

NEW FEATURES  PREVIEW

• With the Server Side Streaming feature, it was ensured that the response of APIs such as OpenAI, Claude, Gemini, which return HTTP responses as Stream, can be transmitted to the client piece by piece, not in bulk. See (APNZ-5040) 

Version 2025.04.2

Publication Date : May 9, 2025

IMPORTANT IMPROVEMENTS AND CHANGES

• APNZ-5017 : New configuration parameters that can be used for cache performance improvements have been added. See

WARNING Within the scope of the newly added parameters, HAZELCAST_OPERATION_RESPONSEQUEUE_IDLESTRATEGY parameter is set to “backoff” by default. With this setting, 5-10% performance increase is achieved, but this setting will continuously use 90-100% of the CPU limit of the Cache Pod. If you do not want this situation, change this parameter to “block”. See

• APNZ-5026 : As part of cache performance improvements, the Cache TTL settings for the components Circuit Breaker, Client Ban, API Proxy Response, API Proxy Group Response, and API Proxy Endpoint Response have been optimized.
• APNZ-5027 : A setting determining whether an error should be thrown when Identity is not found has been added to the Client Ban policy configuration. See
• APNZ-5022 : All conditions in the Condition definitions have been reviewed and improved.
• APNZ-5031 : The health check mechanisms prepared for cache servers have been extended to verify not only API availability but also the health status of the Cache Cluster.
• APNZ-5035 : In multipart/form-data requests, partial logging of API traffic is now supported by excluding the file content.
• APNZ-5020 : Support for generating tokens using API Key and Secret Key via Policy Group has been added.

BUG FIXES

• APNZ-5014 : The value of "tuneCacheConnectionPoolMaxConnectionTotal" is ignored; this affects the number of connections in the cache connection pool.
• APNZ-5024 : When the specified path in XPath and JsonPath queries is not found, an empty string ("") is returned instead of null.
• APNZ-4914 : The system continuously throws errors when accessing the API Proxy Group page; the user interface does not render as expected.
• APNZ-4232 : The Overview page in the Analytics section and the Overview page in the left menu display different content; there are inconsistencies in page navigation.
• APNZ-5021 : New additions to the API Based Throttling and API Based Quota fields cause missing data issues because they are not properly reflected in the Management API.
• APNZ-4984 : JWT and OAuth 2.0 authentication mechanisms should not be supported for WebSocket and gRPC connections.
• APNZ-5032 : On the login page, requests are sent to the backend even when the username and password fields are submitted empty.
• APNZ-5033 : In multipart form requests, the Content-Type header default character encoding has been corrected to UTF-8.
• APNZ-5009 : In API Traffic, the X-Forwarded-For (XFF) field returns empty even when the API Proxy's XFF parameter is enabled.

Version 2025.04.1

Publication Date : April 25, 2025

NEW FEATURES  PREVIEW

• The feature of simultaneous configuration upload to kubernetes clusters located in different locations has been introduced. See

Release 2025.04.0

Publication Date : April 16, 2025

Version 2025.01.4

Publication Date : March 17,2025

NEW FEATURES  PREVIEW

• Prometheus Metric Management

Prometheus metric server on/off support has been added via Environment.

• Routing Control

In Routing, if Content-Length is 0, it is now possible to control whether the header is sent back or not.

IMPORTANT IMPROVEMENTS AND CHANGES

• Connection management between Worker-Cache has been strengthened. Apart from API Proxy Connection Pool, all HTTP connections made in Apinizer are managed with a separate Pool.

BUG FIXES

• APNZ-4911 : Unable to save when no password is given for environment in Advanced in Credential.
• APNZ-4920 : When the Credential page is first created and saved, the process cannot continue without refreshing the page.
• APNZ-4924 : There are errors in allowed and disallowed IP control due to geolocation control.
• APNZ-4925 : Errors received while disable geolocation;
  
  • When trying to add data that doesn't exist, I get an error in the workers, even though it shows as successful.
  • When Disable is done, the remaining 70MB selection on the screen appears to be deployed.
• APNZ-4956 : Security header values sent while establishing a websocket connection cannot be forwarded.

Version 2025.01.2

Publication Date : February 20, 2025

IMPORTANT IMPROVEMENTS AND CHANGES

• Added autoreconnect, autoReconnectMaxRetries and autoReconnectRetryDelay options to Websocket connection management.
• In Websocket API Proxy type, in case of autoreconnect=false, when the backend connection is closed, the client connection is automatically closed.
• In Jose Implementation policy, it has been enabled to add type to JWT header value.

BUG FIXES

• APNZ-4896 : In Jose Implementation policy, ‘Sign By Issuer’ is not selected but its value is selected.
• APNZ-4897 : In Websocket API Proxy type, there is a problem when the headers used by the client when connecting to the Apinizer are used to connect to the backend.

Version 2025.01.1

Publication Date : February 17, 2025

NEW FEATURES  PREVIEW

• Trino Connector Support

Added support for Apinizer Trino Connector.

IMPORTANT IMPROVEMENTS AND CHANGES

• When ‘Global Setting’ is active in Connection Settings, access to the relevant ‘Global Setting’ has been enabled.
• When searching by method on the API Traffic screen, the communication protocol of the method has been added as a label.
• It has been enabled to leave the ‘Path (of Backend API)’ value blank in Endpoint settings.
• In order for the requestBackendUrlToTargetAPI value to be empty in the script policy, the value #EMPTY# has been entered. When this value is used, the request is routed directly to the routing address without adding any path or query.
• It has been enabled to add a logo to the API Portal.

BUG FIXES

• APNZ-4862 : While downloading OpenAPI file in API Portal, it gives an error due to WAF rule.
• APNZ-4863 : There is a namespace mismatch that occurs when Apinizer Manager is deployed to a namespace other than the Apinizer namespace.
• APNZ-4878 : If Content-Type of form-data is not specified as octet-stream, text-type files are sent as text instead of file.
• APNZ-4879 : When names are changed in Worker deployment, the probe or service object cannot be accessed even though the pod is running.
• APNZ-4869 : The start time of WebSocket messages is kept as session start time.
• APNZ-4871 : 'PICK First' algorithm is used in Routing Algorithms in HTTP type API proxies.
• APNZ-4873 : 'Error Response Template' is not automatically activated according to the SOAP or REST type of the API.
• APNZ-4874 : Text area view shifts behind the HTML element.
• APNZ-4876 : During the import process, there is a null error received on non-spec API proxies.
• APNZ-4882 : API Proxy cannot be found in websocket access when Apinizer root context is empty.
• APNZ-4883 : Unable to load keystore and truststore with pfx extension in Environment screens.

Release 2025.01.0

Publication Date : January 31, 2025

Version 2024.09.2

Publication Date : November 14, 2024

WARNING : 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 to decimal number by manually modifying the deployments.Bkz.

NEW FEATURES  PREVIEW

• If OAuth2 or JWT token acquisition is managed with credential, new methods have been added for CORS and XFF settings. See
• Certificate operations (creation, update, query, deletion) can be performed with Management API. See

IMPORTANT IMPROVEMENTS AND CHANGES

• The JDK version used by Apinizer has been upgraded to JDK 1.8 latest version.
• Apinizer images can be run as rootless in Kubernetes or OpenShift.
• The type of API added to the API Portal has been made visible on the portal page.
• It has been enabled to register with more than one App to API Product in API Portal.

BUG FIXES

• APNZ-4675 : Audit logs cannot be written to connectors.
• APNZ-4681 : Accept-encoding value in request header breaks response processing during routing.
• APNZ-4677 : The names of the roles in the API portal should be standardized.
• APNZ-4645 : 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 API Portal, there is a problem with subscription deletion.
• APNZ-4680 : CORS headers were not visible in the logs in OPTIONS response.

Version 2024.09.1

Publication Date : November 4, 2024

NEW FEATURES  PREVIEW

• Automatic metric data cleanup has been added to the Environment (Namespace) Metrics > Application Log Cleanup Tasks. See details.
• The API Products page in the API Portal is now displayed as read-only. See details.

IMPORTANT IMPROVEMENTS AND CHANGES

• If the incoming message's Content-Type is marked as gzip but the content is not actually gzipped, it is now processed as plain. See. "Disable Content Compression"
• A custom time range option has been added for Throttling and Quota features. See
• It is now possible to set the number of Cache and Worker pods to 0. See
• The Home and How It Works pages of the API Portal have been made dynamic. See
• The Appearance Settings page of the API Portal has been improved to provide a more user-friendly and understandable configuration experience. See
• The API Products page in the API Portal has been enhanced for better clarity in API product configurations. See
• Language settings for API Portal view fields are now available in both Turkish and English. See
• JSON and YAML schema views have been added to the example section within an API Product in the API Portal. See
• Tables can now be added to the API Product description and displayed in the API Portal. See
• New Business and Developer roles have been added to the API Portal. See
• The ActiveMQ connection configuration options have been extended. See
• When using a reverse proxy in the Management API, the requirement to send specUrl has been removed. See

BUG FIXES

• APNZ-4601 : Two API proxies imported with different relative paths are confusing their endpoints in the test console.
• APNZ-4588 :  Environment “http” port is closed, when only “https” port is open it cannot be deployed to all pods.
• APNZ-4557 : When switching to the Design tab, the proxy automatically logs out
• APNZ-4460 : When JOSE policy in Global is exported and imported, it is not added as a global policy.
• APNZ-4591 : Since the multipart/related content type is not supported by Undertow, such data should be processed as plain text and not as form data.
• APNZ-4584 : Issues in Management APIs;
  • “deploy-undeploy” authorization on the user should be mandatory only if “deploy” is selected.
  • Exception messages should be presented in more detail.
  • The error received when the project name is not sent correctly should be fixed.
• APNZ-4580 : ProxyContext'teki responseTypeByteArray context değeri değiştirilmişse, işlem sırasında bu güncellenmiş context değeri kullanılacaktır.
• WARNING : Request plain olarak gelse bile artık backend'e gzip formatında gönderilebilir.
  WARNING : Response plain olarak gelse bile artık client'a gzip formatında iletilebilir.
• APNZ-4615 : During the license calculation, there is an error in the part where the number of pods is taken.
• APNZ-4595 : The clock-based TTL setting for cache qouta was missing, this setting has been updated to a maximum of 2 hours.
• APNZ-4581 :  Schema validation is performed by calling XSDs with a GET message.
• APNZ-4593 : There are some general problems in the Design and Portal Section.

• APNZ-4647: The Quick Test section was still visible on the Trace screen even though it was disabled.

• APNZ-4658: In the Authentication policy using the Database Provider, the following error occurred: "An error occurred during database authentication. Detailed Error Message: Configuration is empty or null!"

• APNZ-4655: A null pointer error occurred in the Database Authentication Provider, making it impossible to perform testing.

• APNZ-4630: After deleting old LDAP users and creating new ones with Project Manager roles, the new users were still unable to view the projects.

• APNZ-4641: A null pointer error occurred while creating a reverse proxy via the Management API.

• APNZ-4665: The indicator above global policies was not visible in the Error view.

• APNZ-4662: In the Database Authentication Provider, authorization errors and issues related to persistent connections were encountered.

• APNZ-4624: The body data for PATCH method requests was not being sent to the backend from the Test Console.

• APNZ-4627: Users with analytics roles were unable to access the API Endpoint Creation Report and its related pages.

Release 2024.09.0

Publication Date : September 9, 2024

Version 2024.05.4

Publication Date : 4 August, 2024

With the security patch implemented in this version, checking the value of client IP addresses in browsers in the Apinizer Management Console has become mandatory. Therefore, organizations connecting to the interface using the "Kubernetes Ingress Controller" must configure settings to send client IP information with the X-Forwarded-For header. See

NEW FEATURES  PREVIEW

• Display of the active ports on the Environment screen has been enabled.

• XML and JSON pretty-printing features have been added to the Test Console. See

• A super admin user with permission to access all projects can now be created. See.

• A "Rarely Used/Unused Clients" Report Screen has been added to the Reports section. See.

• A "Rarely Used/Unused Endpoints" Report Screen has been added to the Reports section. See.

• During LDAP API authentication, it is now possible to retrieve user profile information. See.

IMPORTANT IMPROVEMENTS AND CHANGES

• Java and operating system versions used in Apinizer container images have been updated.

• Auto-fill in the API Proxy Development tab has been disabled in Chrome.

• In the API Proxies > Development tab, method search is now case-insensitive.

• Hop-by-hop headers in routing are now processed in a case-insensitive manner.

• A new configurable option has been added to Quota and Throttle policies, as well as Authentication Throttle and Quota screens, allowing the system to continue operating even if the cache does not respond. See. See.

• It is now possible to test API Proxy Group endpoints, and the Test Console now only displays Proxy and Proxy Group options. See.

• During the reparse operation, manually added methods are now preserved. See.

• The Portal UI now supports customization of logo and colors. Additionally, the API Product list is now categorized and includes filtering options. See.

• A new tab has been added in the Portal Test Console to retrieve JWT tokens directly from the application (with optional Base64 encoding for basic authentication). The authentication type is also now displayed in the Portal service view.

• New connection routing options have been added to the API Proxy Routing Settings. See.

• It is now possible to dynamically configure CORS settings for the Token Service on the API Gateway. See.

• In API Portal endpoint testing, when the authentication type is selected as "application", the credentials are automatically applied.

• For proxies using Proxy Groups, a new setting has been introduced: "Can only be used via proxy groups."

BUG FIXES

• APNZ-4485: When an account or its associated credentials are disabled in the Portal, all unrelated credentials linked to that account remain disabled as well.

• APNZ-4483: The Portal menu in the navbar does not appear after login and fails to load unless the page is refreshed.

• APNZ-4479: In the Project Member page, dropdown menus are rendered underneath the table.

• APNZ-4474: If a user only has the Proxy Group (PG) role, clicking on the Proxy Group > Endpoints tab redirects to the login page due to an error.

• APNZ-4432: An HTTP error occurs in the cache, and startup fails when two cache instances are present.

• APNZ-4471: Proxy Group Authorization Issues and Adjustments:

  • Users with the API Tester role cannot view analytics data.

  • Users with permission to view API Proxy Groups can see links in the variables page but cannot access the content.

• APNZ-4463: There is an issue with the 3-hour time range on the Trace screen.

• APNZ-4453: Some API Proxies do not appear when adding an API Product in API Manager.

• APNZ-4441: An error occurs when credentials are first created and invoked for the first time using Basic Auth.

• APNZ-4412: Projects cannot be deleted due to a rollback error caused by an API Product within the project.

• APNZ-4433: Errors encountered by newly registered users trying to log into the Portal:

  • Even if auto-approve is enabled, the user is added as disabled.

  • If a disabled user tries to log in, an error is shown but no proper log is written to the pod.

  • Even with auto-approve enabled, the user remains in pending approval status.

  • Newly registered users should not be required to be added to or activated in an organization.

• APNZ-4473: In the GitOps Environment screen, when multiple environments have been previously created, a transaction error occurs while saving the connector.

• APNZ-4491: In the PolicyConfigurationTemplate > Routing section, fields with missing values should be pre-filled with default values.

• APNZ-4457: Certificates in Apinizer should also be valid for WSS (WebSocket Secure) and STS Token.

• APNZ-4499: File downloads initiated via the API Portal are blocked by the browser.

• APNZ-4497: Exported authentication policy configurations are found to be empty or invalid, resulting in a 'configuration is null or empty!' error.

• APNZ-4496: During MongoDB connection testing, the connection is incorrectly accepted as successful even if the password or address is incorrect.

• APNZ-4434: In Rest2Soap, when a service running in the production environment is exported and moved to test, a missing XML namespace prefix causes incomplete XML content in the test environment.

• APNZ-4501: In the WS-Security From Target policy, Keystore IDs are displayed instead of their names.

Version 2024.05.3

Publication Date : July 4, 2024

NEW FEATURES  PREVIEW

• With the removal of applying policies from API Proxy Groups to individual API Proxies, a new feature called "Policy Group" is planned to address this requirement.

• It is now possible to dynamically define Hop-by-Hop Headers and User-Agent values in Routing. See.

• An expire time field has been added to the JSON Web Key (JWK) screen, and this value is now treated as the expiration time of the certificate. See.

• An expiration alert has been added to the Alarms section for JWK (JSON Web Key).

• WSDL-based schema validation has been introduced for XML schema validation. See.

• Security vulnerabilities found in the new version of API Manager have been resolved.

• Multiple API Proxies can now be selected within an API Proxy Group. See.

IMPORTANT IMPROVEMENTS AND CHANGES

• Creation time and expiration time fields have been added to the JWK (JSON Web Key) list.

• The Trace tab now indicates whether the API Call and Script policies are executed asynchronously or synchronously.

• The JWT ID (jti) value can now be added to the Policy JOSE implementation. See .

• In JSON schema validation, if the error message is already in JSON format, the Error Response Template will no longer overwrite or corrupt the structure by displaying it directly.

• XPath usage performance has been improved.

• A gear icon is now displayed next to endpoints that have policies in Apinizer; hovering over the gear displays the label "Policy Exist". See

• Default charset encoding can now be configured for incoming requests to Apinizer Gateway. See.

• Values under Secret Manager can now be updated. See.

• In Global Policies, the XSLT value is now hidden from the XML Transformation Policy list.

• The remaining validity period of certificates is now displayed and can be filtered on the Apinizer Certificate screen. See 

• The Global Policies menu is now sorted in alphabetical order.

• An API type field has been added to the Product definition in the API Portal.

• In the XML validation policy, when multiple schemas are added, it is now possible to define a system ID to support cases where the schemas reference each other (e.g., using include/import).

BUG FIXES

• APNZ-4395: When a policy is global, saving it does not update its references in the API Proxy methods and does not display a warning indicating that this needs to be corrected.

• APNZ-4384: In some screens, after deleting a list item and logging out, when logging back in, the delete confirmation dialog remains open.

• APNZ-4409: When a global policy is updated, the list of related API Proxies is not shown in the error message, and their status does not switch to "redeploy required".

• APNZ-4405: The Elasticsearch disk usage alarm is functioning incorrectly.

• APNZ-4414: In the policy type field, JSON Schema Validation is incorrectly displayed as XML Schema Validation.

• APNZ-4419: Under conditions, if a user selects a value but does not enter the corresponding variable, the system blocks saving due to a validation error.

• APNZ-4420: When opening the Test Console for the first time via Tools, two CodeMirror instances appear.

• APNZ-4445: In the XML validation policy, when "Validate using WSDL definition file" is selected and multiple schemas exist, not all schema files are loaded.

• APNZ-4447: During SOAP-to-REST protocol transformation, elements without a namespace prefix should not be assigned a prefix due to name similarity.

• APNZ-4448: When using XPath to extract data from an XML file, if the file is malformed, it should return an empty value instead of the entire content.

Release 2024.05.0

Publication Date : June 4, 2024

Version 2024.01.6

NEW FEATURES  PREVIEW

Publication Date : May 31, 2024

• The ability to perform team-based authorization via LDAP has been added to the Manager console. See

Version 2024.01.3

Publication Date : March 31, 2024

IMPORTANT IMPROVEMENTS AND CHANGES

• In the JOSE Implementation policy, when "Message Body" is selected as the "Target to be Signed/Encrypted", it is now possible to leave the claim name field empty, in which case the message body is used directly as the payload.

• During the initialization of Credentials, secret information is now generated and cached.

BUG FIXES

• APNZ-1403: When a variable is selected as the second value in a Condition, the value cannot be resolved correctly.

Version 2024.01.2

Publication Date : March 22, 2024

NEW FEATURES  PREVIEW

• Test Console Audit Log Screen
  A new screen was added to display the tests performed from the Test Console along with the username. See.
• Displaying Total Method Count in Proxies on the Overview Screen
  Information about the total number of methods in API Proxies has been added to the Overview screen. See.
• New Report: API Endpoint Creation Report
  A new API Endpoint Creation Report has been added to visualize API Endpoints grouped by time. See.
• New Charts on the Overview Screen
  Charts showing the distribution and count of API Proxies, connections, and HTTP method types have been added to the Overview screen. See.
• Retrieving Claim Value from JWT Using Business Rule
  Two new fields have been added to the business rule to extract claim values from within a JWT: Extract JWT Header Claim and Extract JWT Body Claim. See.
• Environment-Based Policy Execution
  The environment name and ID information have been added to the Context Value used in Variables and Script Policies. See.
• ZoneID Value in Context Value
  It is now possible to enter the ZoneID value for date-containing values in Context Value. See.
• New Fields in Context Value for Script Policies and Variables
  New fields have been added to the Context Value used in Script Policies and Variables. See.
• Accessing Secret Values of Credentials via Script Policy
  Script Policies can now access secret values of the associated credential. See.

IMPORTANT IMPROVEMENTS AND CHANGES

• Added the ability to bulk enable/disable policies within API Proxy methods. See.

• Added the ability to enable or disable Quick Test in System Settings. See.

• Backend API version is now automatically populated when parsed from Swagger and OpenAPI.

• Added an option to the Jose Implementation policy to add JSON either as a string or as a JSON object. See.

• The description entered for the environment is now displayed in the list screen.

• The popup view for Context Value details has been improved.

• Added the ability to retrieve the status code from the response into a context variable.

• Added the ability to select the client identity via a variable in the Jose Validation policy. See.

• In the JSON Schema Validation policy, the JSON path can be left empty, and when multiple JSON schemas are provided, each schema is validated separately for the target path. See.

• The XPath field can now be left empty in XML Schema Validation. See.

• When adding an action, for selected data types such as Extract Body and Header, the target variable label has been updated to "Target Variable Where Extracted Data Will Be Added."

BUG FIXES

• APNZ-4096: There are errors on the screens accessible and operable by users who only have the Analyzer role in the Development menu.

• APNZ-4149: Users who fail to log in to the interface are not being recorded in the audit logs.

• APNZ-4156: Services created via the API Creator are missing authentication information on the Portal.

• APNZ-4177: Pod list is not displayed under Kubernetes resources.

• APNZ-4194: When an API Proxy created with DB2API is added as a new API Proxy from another project, the request bodies are coming in empty.

• APNZ-4195: An error occurs when testing LDAP.

Version 2024.01.1

Publication Date : March 14, 2024

NEW FEATURES  PREVIEW

• New Screen: Application Log Cleanup Tasks
Automatic cleanup of logged data in Apinizer at specified time intervals has been enabled. See.

• Alarm Creation for Logs
Alarms can now be generated when logs stored in Apinizer reach a certain size. See.

• Trace Search Filter
A search filter based on trace mode has been added to the advanced search options in API Proxies. See.

• Globalize Feature
A feature has been added to allow project-level items (connection settings, monitor settings, report settings, credentials, certificates) to be moved to the admin side. This enables centralized management by administrators and shared usage across all projects.

• NTLM Settings
An NTLM feature has been added to the Routing tab of API Proxies to enable authorization in cases where backend APIs require NTLM. See.

• Log Levels by Class/Package
A new Log Levels tab has been added to the Application Logs page, allowing log levels to be set based on class or package. See.

• URL Encode and Decode Operations in Business Rule Policy
URL encode and URL decode functions have been added to the Business Rule policy. See.

• URL Encode and Decode Operations in Data Operations Page
URL encode and URL decode functions have been added to the Data Operations page in the test tool. See.

IMPORTANT IMPROVEMENTS AND CHANGES

• Politikalara "is exist" ve "is not exist" koşulu eklendi.
• Apinizer'ın sol menüsüne o an hangi projede olunduğu bilgisi eklendi.
• Test Araçları'ndaki Test Konsol'a erişebilen roller düzenlendi.
• API Portal'de kimlik bilgileri (credential) ve analitiklerin (analytics) konfigüre edilmesi sağlandı. Bkz.
• Breadcrumbs'a link eklendi.
• Apinizer Kubernetes sunucularında Manager, Integration ve Portal'e node affinity eklendi. Bkz.
• Audit ve Yedekleme (Backup) sayfasında gelmeyen tablolar ve yedek (backup) alırken exclude edilecek eksik varlık isimleri eklendi.
• Konnektörlerin hangi API Proxy'ler için çalıştığı bilgisi uygulama loglarına eklendi.  
• Failover ile verilerin Apinizer veritabanına kaydedilme işleminde performans iyileştirilmesi yapıldı.
• Menü değişiklikleri yapıldı.
• Routing Connection'da yeni hata tipi eklendi. Bkz.
• WSDL ile üretilen örnek SOAP XML mesajının büyüklüğünün sınırlandırılması için Genel Ayarlar'a Örnek SOAP XML Mesajı Üretim Sınırları ayarları eklendi. Bkz.
• SOAP servisler için geçerli yönlendirme sekmesine SOAP Action ve Namespace bilgisini düzelt seçeneği eklendi. Böylece eskiden otomatik olarak yapılan bu işlemin isteğe bağlı yapılabilmesi sağlandı. Bkz.
• API Proxy Uygulama Loglarının sadece belirtilen API Proxy için seviyesinin değiştirilebilmesi sağlandı. Bkz.
• "Is Exist" and "Is Not Exist" Conditions Added to Policies
• Current Project Indicator Added to Apinizer Sidebar
• Roles with Access to the Test Console in Test Tools Have Been Updated
• Configuration of Credentials and Analytics Enabled on the API Portal See.
• Links Added to Breadcrumbs
• Node Affinity Added for Manager, Integration, and Portal on Apinizer Kubernetes Nodes See.
• Missing Tables in Audit and Backup Pages and Excluded Asset Names in Backup Process Have Been Added
• Information About Which API Proxies the Connectors Are Working For Has Been Added to the Application Logs
• Performance Improvement Made in Data Saving to Apinizer Database via Failover
• Menu Changes Have Been Made
• New Error Type Added to Routing Connection See.
• General Settings Now Include Limits for the Size of Example SOAP XML Messages Generated from WSDL See.
• "Fix SOAP Action and Namespace" Option Added to the Routing Tab for SOAP Services, Allowing Manual Correction Instead of Automatic Behavior See.
• Log Level Configuration for Application Logs Can Now Be Set Specifically per API Proxy See.

BUG FIXES

• APNZ-4063: The requirement for a schedule in the Backup screen should be removed.
• APNZ-4065: Methods with the same endpoint are grouped together in the analytics charts.
• APNZ-4069: There are issues related to pagination.
• APNZ-4070: Time display in the charts under the Analytics tab should reflect local time.
• APNZ-4071: Webhook should be removed from the actions list.
• APNZ-4089: When global STS Authentication and Backend API Authentication policies are defined for a proxy, the password gets re-encrypted.
• APNZ-4090: When the log level of a proxy is set to debug, excessive logs are written, and logs lack API Proxy and Client ID information, making them unsearchable.
• APNZ-4100: When application logs are set to debug, Mongo insert logs are also recorded.
• APNZ-4102: In token retrieval using scope, the scope value returns empty.
• APNZ-4111: If an error occurs while creating the connection definition for log recording, the failover mechanism does not trigger.
• APNZ-4113: If an error occurs during connector creation, the failover mechanism does not trigger.
• APNZ-4115: API Proxy information is missing in application logs for some loggers.
• APNZ-4121: Some headers added during routing connections are not logged.
• APNZ-4125: In the IP Traffic & Time Metrics reports, total values appear as zero.
• APNZ-4127: In caching, if the same key is routed to a different endpoint within the same proxy or proxy group, the previous result is returned.
• APNZ-4133: In Identity Providers, records prior to updates are not displayed and new records do not reflect on the screen.
• APNZ-4142: In Data Operations, selecting XML as the format returns the result in a single line.

Release 2024.01.0

Publication Date : January 2, 2024

Older Versions and Changes

• 2023 Release Notes and Changes
• 2022 Release Notes and Changes
• 2021 Release Notes and Changes