Date of version: January 2, 2024

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

Removed Features

APNZ-3790 WARNING! Automatic deletion of log records based on retention period was removed from Monitor pages, Application Logs, API Integration, and Reports pages due to the requirement for data owners to control log records. Purge scripts were prepared to allow deletion of these records from the database. See.

APNZ-3884 WARNING! Pages used to automatically back up Elasticsearch indexes with Apinizer were removed due to the usage requirements of snapshot policies. Scripts that contains manual operations were prepared to perform these tasks. See.

APNZ-3865 WARNING! All features related to the old revision logic have been removed due to difficulty of use. Now completely switched to the "Deployment History" application, which was introduced in Version 2023.06.1. Parameters that were used in the Apinizer Management APIs have also been removed. See.

New Features

APNZ-3771 New Connection Definition: Syslog Connection

Syslog connection definitions were introduced in Apinizer to store log records in the Syslog system. See.

APNZ-3855 New Connector/Action Type: Syslog Connector

Data can now be sent to the relevant system using connectors created with Syslog connection definitions. See.

APNZ-3772 New Connection Definition: Webhook Connection

Webhook connection definitions were introduced in Apinizer to move log records to the target system using Webhooks. See.

APNZ-3856 New Connector/Action Type: Webhook Connector

Data can now be transferred to the relevant system using connectors created with Webhook connection definitions. See.

APNZ-3773 New Connection Definition: RabbitMQ Connection

RabbitMQ connection definitions were introduced in Apinizer to send log records to the queue system using RabbitMQ. See.

APNZ-3854 New Connector/Action Type: RabbitMQ Connector

Data can now be sent to the relevant queue system using connectors created with RabbitMQ connection definitions. See.

APNZ-3774 New Connection Definition: Kafka Connection

Kafka connection definitions were introduced in Apinizer to transfer log records to the target related to Kafka. See.

APNZ-3853 New Connector/Action Type: Kafka Connector

Data can now be sent to the relevant target using connectors created with Kafka connection definitions. See.

APNZ-3779New Connection Definition: Elasticsearch Connection

Elasticsearch connection definitions were introduced in Apinizer to store log records in the Elasticsearch system. See.

APNZ-3852 New Connector/Action Type: Elasticsearch Connector

Data can now be sent to the relevant system using connectors created with Elasticsearch connection definitions. See.

APNZ-3880 New Connection Definition: Apache ActiveMQ Connection

Apache ActiveMQ connection definitions were introduced in Apinizer to send log records to the message system using Apache ActiveMQ. See.

APNZ-3880 New Connector/Action Type: Apache ActiveMQ Connector

Data can now be sent to the relevant message system using connectors created with Apache ActiveMQ connection definitions. See.

APNZ-3775 Environment-Based Log Connector Management WARNING!

By default, logs were stored in Elasticsearch, or this default setting was disabled to transfer logs to another system (Syslog, Kafka).

To make log management more flexible, this setting can now be done at the environment level, can be disabled when necessary, and simultaneous logging can be done on various log connectors (Database, Elasticsearch, Kafka, RabbitMQ, ActiveMQ, Syslog, Webhook). See.

In case API Proxy Traffic could not be sent to Elasticsearch, it was stored in the Apinizer database. With the introduction of the connector infrastructure, this feature was removed, allowing the selection of a failover connector for traffic in case of connector issues. See.

APNZ-3867 Creating API Proxy with Connector

API Proxies can now be created using the newly defined connectors (Elasticsearch, Kafka, RabbitMQ, ActiveMQ, Syslog, Mail), enabling access to the integration point in the connector via API. See.

APNZ-3879 Connector Definition for Application and Token Logs WARNING!

By default, Application and Token logs were saved in the Apinizer database. To make log management more flexible, connector definitions were made, allowing these logs to be transferred to other systems in addition to the Apinizer database via these connectors. See.

APNZ-3484 Privacy Settings Definition

Previously, privacy settings could be set globally. With the update, Privacy Settings can be configured specifically for the connector in the environment. See.

APNZ-3764 IP-Based Report

Requests to API Proxies at the project or application level can now be grouped based on IP information, allowing viewing of usage summaries for specific metrics. See.

APNZ-2390 Cache Setting on Method and Endpoint

Cache settings can be made on a method/endpoint. Cache settings can be made not only for those with GET Http Method but also in other methods. See1. See2.

APNZ-2940 Exporting a Certificate

The ability to export installed certificates in the system has been provided. See.

APNZ-909 APNZ-3892 New Management APIs for Adding/Deleting/Updating Credentials in Apinizer Identity Pool

A new Management API introduced which users can create/update/delete/grant/revoke credentials in Apinizer Identity Pool. See.

APNZ-3968 New Management APIs for Exporting/Importing API Proxies 

Export/Import API Proxy has been added to Management APIs. See.

APNZ-3615 New Report: API Proxy Traffic By Interval

API Proxy Traffic By Interval report is added to visualize API Proxy Traffic by grouping it by time. See.

APNZ-3572 XML to JSON and JSON to XML Transformations

XML to JSON and JSON to XML transformations have been added to the transform process in the Business Rule policy, in addition to XSLT and JSON operations. See.

In addition to the XSLT option, the XML to JSON option has been added to the XML Transformation Policy. See.

In addition to the Jolt option, the JSON to XML option has been added to the JSON Transformation Policy. See.

XML to JSON and JSON to XML transformations have been added to the XML Transformer and JSON Transformer pages. See1. See2.

A new "All Body" option has been added to allow the entire body value to be taken for message types when creating a variable of Body type in variable definition. See.

APNZ-3911 Deleting a Revision from Deployment History

Manual deletion of revisions of API Proxy deployment history is allowed. See.

APNZ-3935 Migrate Unsent API Traffic Logs

If the Apinizer configuration database is selected as the failover connector, the screen that carries the failover data accumulated in the Apinizer configuration database to the main connectors has been created. See.

 APNZ-3951 Sending Audit Logs with a Connector

The ability to send Audit Logs with a Connector, defined through the System General Settings screen, has been implemented. See.

APNZ-3991 New Connection Definition: Logback

Logback connection definitions were introduced in Apinizer to send log records to the file system using Logback. See.

APNZ-3991 New Connector: Logback

Data can now be sent to the relevant file system using connectors created with Logback connection definitions. See.

APNZ-4027 API Portal Visibility Settings

New settings have been added to the API Products page to enable detailed visibility of API products. See.

APNZ-4038 Setting the Navbar Color

The feature of determining the navbar color has been introduced to make it easier for users of the Apinizer Management Console to distinguish between environments. See.

APNZ-4013 Changing Context Values in Script Policies

It is enabled to change context values in the Script policy. See.

Important Enhancements and Modifications

APNZ-3768 The data type "text" for request/response headers and parameter values previously stored in Elasticsearch index templates was changed to "nested." See.

This change resolved issues in advanced searches and standardized the data type sent to all connectors. See.

APNZ-3780 Access to Elasticsearch monitor page was moved to Elasticsearch connection configuration page.

APNZ-3781 Elasticsearch configuration fields set from General Settings page were moved to Elasticsearch connection configuration page.

APNZ-3782 All connections under the Connection Management menu can now be exported or imported.

APNZ-3885 A new type called Custom Variable was added to the Variables page. This type allows creating custom variables for the message request/response pipeline. See.

APNZ-3871 Access to Custom Variable values was provided in script policies.

APNZ-3884 Access to Message Context variables was provided in script policies.

APNZ-3756 Environment information is now stored in Application Log.

APNZ-3763 API Proxy can now be specifically traced using Custom Query based on desired data only.

APNZ-3804 Connection configurations can now be tested based on environment information.

APNZ-3810 Keeping OAuth2 and Trace information in Elasticsearch was removed. OAuth2 and Trace information is now stored in the Apinizer database.

APNZ-3859 When API Proxy is loaded, an option (permanent revision) was introduced to prevent the deletion of Deployment History.

APNZ-3874 A new condition "query/filter rate percent" was added to the Anomaly Detector, which calculates the ratio of the searched query to the total data in the relevant time period.

APNZ-3895 Improvement was made to understand errors received during connection to Backend API of API Proxy and messages returned from Backend API; error messages were simplified. New values that can be used in error message templates were added. See.

APNZ-3902 If the Application Logs are at a level below the INFO level and/or Trace mode is turned on in any API Proxy, a warning message will appear in the API Management Console.

APNZ-3761 Metric information on how long the message spent on the request, Backend API and response pipeline was detailed. And it is now possible to query these fields on the relevant API traffic and reporting screens.

APNZ-3788 A rule has been introduced that the API Proxy relative path value cannot be deployed with only the "/" character.

APNZ-3890 The ability for a user in the API analytics role to use the test console in the API Traffic Tab has been removed.

APNZ-3992 Comprehensive security improvements have been made to the APIs used by the API Management Console screen. 

APNZ-3145 All schedules have been standardized.

APNZ-3628 Client IP has been added with a variable to the Blocked IP and Allowed IP policies. See1. See2.

APNZ-3893 Excel Export feature has been added to the Credential page. See.

APNZ-3231 Added the ability to select a project as default on the My Profile page. Thus, it is no longer necessary to select a project every time the screen is turned on. See.

APNZ-3348 It is now possible to view API proxy Group information for requests coming through API Proxy Group in the API Traffic details.

APNZ-3961 A warning message has been added to Task Flows if Kubernetes is not managed with Apinizer.

APNZ-3814 Common values have been added by default to the variables menu under the management menu.

APNZ-3965 During environment creation, trimming of cache and worker server addresses has been enabled for both GitOps and normal methods.

APNZ-3980 The JSON Schema library has been changed. See.

APNZ-4005 Ensured that the Request Address field appears as a single piece at all times in API Traffic screens.

APNZ-4014 Swagger Show Spec section has been removed from API Proxy, but access via the endpoint continues.

APNZ-4017 Added XML/JSON formatting feature next to the Base64 Decode/Encode tool. Renamed to Data Operations. See.

APNZ-4019 Existing settings on templates are now retained when SOAP is reparsed in SOAP to REST.

APNZ-4031 The API Products interface has been improved. See.

APNZ-4032 The use of "{}" as path param between "/" in the path param has been expanded and it can also be used as "/value{param}/"

APNZ-4036 Identity and analytical information retrieval is improved with configuration access for API Portal. See.

APNZ-4043 Standardization of analytical reports. See.

APNZ-4044 A 1MB limit on the body size was added to step-by-step tracking log records due to MongoDB constraints.

APNZ-4045 Refresh and delete buttons were added to the API Proxy Trace tab. See.

Bug Fixes