Release Notes - 2024

Release 2024.09.0

Publication Date: September 9, 2024

This document contains New Features, Changes, Improvements, and Bug Fixes for version 2024.09.0.

WARNING For users updating from the 2024.05.3 patch version, multiple API Proxy selection is now allowed in the API Proxy Group. With this setting, the feature of applying policies in the API Proxy Group to API Proxies, which was previously available, has been removed.

WARNING For users updating from the 2024.05.4 patch version, with the security update, client IP address value checking has been made mandatory in the Apinizer Management Console. Therefore, organizations connecting to the interface using “Kubernetes Ingress Controller” are no longer required to send client IP information with the X-Forwarded-For header.

• New Connection Configuration: RabbitMQ

NEW FEATURE

• Specifications are now available for download on the API Portal.
• New policies have been added to the Management APIs. See.

HIGHLIGHTED NEW FEATURE

•  With the Disable Routing button, a service loaded with a definition file can now be run without going to the backend. See.
•  The values written in the routing address have been detailed to make it clearer where proxy routing addresses go when they do not go to the backend.See.
• WARNING The Mirror API selected when creating the API Proxy has been deprecated and removed in this version. It has been configured in the API Proxy Routing section.
•  The actions that can be performed in the API Proxy and API Proxy Group Development tab have been customized for each line. See. 
•  The active/passive button in Connection Configurations has also been added to the listing screen. See.
•  A warning has been added to the DB-2-API screen indicating that the results are returned as top1/limit1, which is not visible in get queries. See.
•  Apiops can now be completely shut down. See.
•  The list of those used in the Proxy Group has been added to global policies.
•  In the endpoint test on the API Portal, the Auth information is now automatically retrieved when the application is selected. See.
•  When the cache is initialized, previous quota data can be loaded from the database either lazily or eagerly. See.
•  Production and Test areas have been added to Network Gateway Environments. See.
•  The enable button in connection configurations has been standardized in tables.

BUG FIXES

For detailed information about the new features, important changes, and improvements included in Version 2024.05.3 Patch and Version 2024.05.4 Patch, please refer to the relevant document:

2024.05.x

Release 2024.05.0

Publication Date: June 7, 2024

NEW FEATURE

•  New fields have been added to script and variable context values. See.
•  The Project and Admin Overview pages have been made more interactive. See1. See2.
•  Added the ability to access secret values belonging to the script policy and credentials. See.
•  Second-based filtering has been added to the API traffic screen.
•  Logging in Graylog GELF format via UDP/TCP has been enabled. See.
•  Manager and Portal can now be opened via HTTPS.
•  An Error Policy line has been added to ensure that the specified policies are applied in the event of an error. See.
•  The user_token_blackList object has been added to the deletion of old logs. See.
•  A setting has been added to the general settings that allows users to log in from multiple tabs/locations at the same time. See.
•  A truststore tab has been added to the Certificates screen. See.
•  The ability to dynamically define Frequently Asked Questions in the API Portal has been enabled.See.
•  The application has been added to the portal. See.
•  A Documentation & Testing tab has been added to the Portal.
•  The Credential screen is configured to be filtered according to the applications and accounts in the Portal.
•  The Tools menu has been added to the Portal.
•  Test User role added. See.
•  Notifications have been added to the purge jobs list in the system. See.
•  Script policy can now run asynchronously. See.

IMPORTANT CHANGES AND IMPROVEMENTS

•  When the API Call policy is working unidirectionally, if an error is received from an API call, it is ensured that this error can be reflected in the result of the relevant API Proxy.
•  The API Proxy Traffic screen now allows searches using the options empty/is not empty/exists/does not exist/contains/does not contain/in list/not in list in the advanced query field.See.
•  The API Visibility screen for Organizations has been added to Portal Management. See.
•  A list was provided to Condition, enabling the checking of values such as whether or not they are included in the list. See.
•  The ability to enter specific days into the time policy has been added. See.
•  When searching for a user of the LDAP type on the user screen, a warning is displayed if the user cannot be found.
  
•  If “Advanced” is selected in the LDAP information in the identity provider, the object will be set as default, cannot be deleted, and can only be edited.
  
•  Ensured that LDAP connections within the LDAP provider are received correctly.
•  The headings in the admin panel have been corrected. See.
•  New values have been added to the values accessible via script. See.
•  It is now possible to prevent two people from logging in at the same time with the same user account. See.
•  The method for hostname verification of secure connections can now be selected in the system settings.
  
•  When there is a problem with the xslt file in the test console, the details of the problem are now displayed on the screen.
  
•  When a user logs into API Manager, the JWT generated is now smaller in size.
  
•  When deploying, details were provided about which proxy or proxy group the relative path conflict occurred with.
•  Elasticsearch template settings can now be edited on screen. See.
•  The API Developer Portal now allows for configurable account registration. See.
•  Rollover feature added to Elasticsearch operations. See.
•  Performance improvements have been made to the Uptime Monitor and Anomaly screens.
•  Added feature to sign the request body as JSON in the test console. See.
•  The Key Store, Public Key, Private Key, and Certificate fields that open on the JWK screen are now displayed in order and can be searched.
•  The ability to search by organization and sort names has been added to the Credential screen.
•  The certificate can now be edited. See.
•  Performance improvements have been made in XML transformation policy and protocol transformation.
•  The Connection Request Timeout value can now be adjusted in Routing. See.
•  The feature of signing the request body as WS Security has been added to the test console. See.

BUG FIXES

Issue No	Description
APNZ-4309	WARNING When API Manager is opened in different tabs, project information gets mixed up.
APNZ-4369	WARNING There is an error in converting numeric fields in the response message to text during the REST-SOAP-REST conversion. Large numbers were displayed using scientific notation in JSON. After this correction, numbers began to be used as they are in the response message. Previously malfunctioning conversion processes will be corrected with this update. However, this may cause previously undetected errors to surface. Therefore, we recommend that you check your REST-2-SOAP processes.
APNZ-3833	Even when the log level is set to “off” in the application logs, logs continue to be kept.
APNZ-3857	There are problems with the variables in Context Values.
APNZ-4022	Errors are occurring in the operation of routing-based settings such as the number of retries in the uptime monitor.
APNZ-4039	Errors are encountered in the operation of routing-based settings such as the number of retries in the uptime monitor. Authorized users are not listed in the analytics graphs when their permissions are revoked.
APNZ-4061	The report generator is not functioning.
APNZ-4093	The default value “Elasticsearch log exists on disk” has been removed from alerts.
APNZ-4101	Current Cron expressions are not being updated.
APNZ-4123	ACL Reports issues: The project list is not coming up. Search By Credentials does not work with the desired filtering.
APNZ-4138	Even though the log option is enabled in case of an error, no log record can be found for the request stuck on the White IP when logging is disabled on the proxy.
APNZ-4162	Unable to register after OpenAPI parsing.
APNZ-4174	Integration is triggered but cannot assign requests.
APNZ-4183	Unable to query Elasticsearch disk usage alarm.
APNZ-4208	When the project is changed, there is a 5-6 second delay on the screens.
APNZ-4210	A label error is occurring in Context Value.
APNZ-4215	Ldap Secure is not working.
APNZ-4229	The certificate is not listed in the API Call for the project.
APNZ-4236	Even if the anomaly is closed, ‘anomaly detected’ continues to be added to the results list.
APNZ-4244	The application logs store the last 1 day's logs at most.
APNZ-4245	If an environment is linked to a project, you cannot access that environment on the gateway page when the project is deleted.
APNZ-4259	Even though HTTP is disabled in the environment settings, svc is being created in Kubernetes.
APNZ-4260	The Purge Jobs process is not working in Application Logs.
APNZ-4262	When the API Manager user logs out, the JWT does not become invalid.
APNZ-4263	In Rest2Soap conversions, the Jackson library's (default) data size limit has been increased from 20 MB to 2.1 GB, which is the integer limit.
APNZ-4274	When we open the service only via HTTPS, the XSD address in the WSDL remains HTTP.
APNZ-4276	Business rule not working in JWT requests.
APNZ-4294	Adding data to the body with Business Rule is not working properly.
APNZ-4297	Even if the API is not public on the portal, the page can be accessed directly via IP. My account page is not showing up on the portal.
APNZ-4298	When there is more than one cache pod, an HTTP protocol error is received.
APNZ-4308	When the user logs into API Manager, their default project does not appear.
APNZ-4318	An error occurs when any value is entered while setting the threshold value for the disk fullness alarm.
APNZ-4323	The delete function in Redaction is not working, and values cannot be entered into the relevant field during the modification process.
APNZ-4324	An error occurs when uploading certificates without a CN statement.
APNZ-4332	In REST to SOAP conversion, the namespace prefix is not added to XML in special cases where xsi:nil is present.
APNZ-4335	A cache service is not created in the republished environment.
APNZ-4349	If a user who logs in from Active Directory and has full permissions in the project tries to enter something other than a name in the connection configuration > database option and does not have administrator permissions, the session is automatically closed.
APNZ-4357	When multiple policies are added to Error Policy, they are rearranged.
APNZ-4358	The path param is not visible in the API Proxy design section.
APNZ-4360	Policies added to the Error Policy line do not appear in the references of Global policies.
APNZ-4362	Error policies in global policies are not displayed or updated.

Release 2024.01.0

Date of Publication: January 2, 2024

NEW FEATURE

• API Traffic Log Settings

Which fields are logged or not logged in message areas belonging to API Proxy and API Proxy Groups was managed through their own pages. To improve user experience, this setting was made possible on an environment basis through the API Proxy list on an application and project basis. Additionally, it is now possible to enable or disable logging for connectors assigned to API Proxies or API Proxy Groups. See.

• New Connection Configuration: Syslog

Syslog connection definitions can now be made to store log records created via Apinizer in the Syslog system. See.

• New Action/Connector: Syslog

Data was sent to the relevant system using a connector created with syslog connection definitions. See.

• New Connection Configuration: Webhook

Webhook connection definitions can now be made to transfer log records created via Apinizer to the target system using Webhook. See.

• New Action/Connector: Webhook

Data transfer to the relevant system was enabled using a connector created with webhook connection definitions. See.

• New Connection Configuration: RabbitMQ

It is now possible to configure RabbitMQ connection settings to send log records created via Apinizer to the queue system using RabbitMQ. See.

• New Action/Connector: RabbitMQ

Data was sent to the relevant queue system using a connector created with RabbitMQ connection definitions. See.

• New Connection Configuration: Kafka

Kafka connection definitions can now be made to transfer log records created via Apinizer to the relevant Kafka target. See.

• New Action/Connector: Kafka

Data was sent to the relevant target using a connector created with Kafka connection definitions. See.

• New Connection Configuration: Elasticsearch

Elasticsearch connection definitions can now be made to store log records created via Apinizer in the Elasticsearch system. See.

• New Action/Connector: Elasticsearch

Data was sent to the relevant system using a connector created with Elasticsearch connection definitions. See.

• New Connection Configuration: Apache ActiveMQ

ActiveMQ connection definitions can now be made to send log records created via Apinizer to the message system using ActiveMQ. See.

• New Action/Connector: Apache ActiveMQ

 Data was sent to the relevant messaging system using a connector created with ActiveMQ connection definitions. See.

• New Connection Definition: Logback

Logback connection definitions can now be made to store log records created via Apinizer in the Logback system. See.

• New Connector: Logback

Data was sent to the relevant target system using a connector created with Logback connection definitions.See.

• Defining Log Connectors on a Per-Environment Basis WARNING

By default, logs are stored using Elasticsearch, or this default setting can be disabled to transfer logs to another system (Syslog, Kafka).

To make log management more flexible, this setting can be configured on an environment-by-environment basis, disabled when necessary, and used for simultaneous logging on multiple log connectors (Database, Elasticsearch, Kafka, RabbitMQ, ActiveMQ, Syslog, Webhook). See.

When API proxy traffic could not be recorded, it was stored in the Apinizer database. With the transition to the connector infrastructure, this feature was removed, and the ability to select a failover connector was added. This ensures that traffic is transferred to the failover connector(s) in the event of a problem with the connector. See.

• Creating an API Proxy with a Connector

API Proxy can now be created using the newly defined connectors (Elasticsearch, Kafka, RabbitMQ, ActiveMQ, Syslog). This allows API access to the integration point in the connector. See.

• Defining Connectors for Application and Token Logs WARNING

VBy default, application and token logs were recorded in the Apinizer database. To make log management more flexible, connector definitions were created, enabling application and token logs to be transferred to other systems in addition to the Apinizer database via these connectors. See. 

• Privacy Settings Definition

Privacy settings used to be set globally. With the new update, you can now configure Privacy Settings specifically for each connector in the environment. See.

• IP-Based Report

Requests received by API Proxies based on projects or applications are grouped according to IP information, enabling the display of usage summary metrics. See.

• Cache Configuration Based on Method and Endpoint

It is now possible to configure cache settings based on method/endpoint. Cache settings can now be configured not only for HTTP GET methods but also for other methods.  See1. See2.

• Exporting Certificates

It is now possible to export certificates loaded into the system. See.

• Adding/Deleting/Updating Users to the User Pool in Apinizer Identity Management Using REST API

User addition/deletion/update operations have been added to the Apinizer user pool via REST API. See.

• API Proxy Export/Import API

An API has been added that enables API proxies to be exported/imported to management APIs. See.

• New Report: API Proxy Traffic (By Time)

The API Proxy Traffic (By Time) report has been added to visualize API proxy traffic grouped by time. See.

• XML to JSON and JSON to XML Conversions

XML to JSON and JSON to XML conversions have been added to the Business Rule policy alongside XSLT and JSON conversions. See.

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

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

XML Conversion and JSON Conversion conversion tests have been added to the test pages. See1. See2.

When defining variables, a new “Entire Body” option has been added to allow the entire body value to be taken for message types when creating variables of the Body type. See.

• Deleting Revisions from Deployment History

It is now possible to manually delete revisions on the API Proxy deployment history. See.

• Transferring Unsent API Proxy Traffic Logs

If Apinizer configuration database is selected as failover connector, a screen has been developed to transfer failover data accumulated in Apinizer configuration database to the connectors it should go to. See.

• Sending Audit Logs with Connector

Audit logs can now be sent to different destinations using the Connector, which can be defined on the System General Settings screen. See.

• API Portal Visibility Settings

New settings have been added to the API Products page to allow detailed visibility settings for API products. See.

• Setting the Navbar Color

A feature has been added to allow users of the Apinizer Management Console to easily distinguish between environments by setting the navbar color through system settings. See.

• Changing Context Values in Script Policy

The script policy now allows context values to be changed. See.

IMPORTANT CHANGES AND IMPROVEMENTS

• The data type of request/response headers and parameter values stored in the Elasticsearch index template, which used to be text, has been converted to nested. See.
• This resolved the issue encountered in advanced searches and standardized the data type sent to all connectors. See.
• Access to the Elasticsearch monitor page has been moved to the Elasticsearch connection configurations screen. 
• The Elasticsearch configuration fields on the General Settings page have been moved to the Elasticsearch connection configurations screen.
• All connections under the Connection Configurations menu can now be exported or imported.
• vA new type called Custom Variable has been added to the Variables screen. This type allows you to create custom variables for the message line. See.
• Access to Custom Variable values has been enabled in the script policy.
• Access to Message Context variables has been enabled in the script policy.
• Environment information is now stored in the Application Log.
• API Proxy, Custom Query enables specific tracing based solely on the desired data.
• Connection configuration links were tested using environment information.
• WARNING OAuth2 and Trace information logging in Elasticsearch has been removed. OAuth2 and Trace information is now stored in the Apinizer database.
• When loading the API Proxy, an option (permanent revision) feature was added to prevent the Deployment History from being deleted.
• A new condition of type “query/filter rate percent” has been added to the Anomaly Detector, which calculates the ratio of the searched query to the total data in the relevant time period.
• Improvements were made to understand the messages returned from the Backend API during the connection to the Backend API belonging to the API Proxy, and error messages were simplified. New values that can be used in the error message template were added. See.
• If the application logs are below the INFO level and/or the Trace mode is enabled in any API Proxy, a warning message will appear in the API Management Console.
• The metrics detailing how long the message request spent in the Backend API and response queue have been specified. The ability to query these fields has also been added to the relevant API traffic and reporting screens.
• A rule has been introduced that the API Proxy relative path value cannot be deployed with only the “/” character.
• A user in the API analytics role is prevented from using the test console in the API Traffic tab.
• Comprehensive security improvements have been made to the APIs used by the API Management Console screen.
• All schedules have been standardized.
• Client IP has been added to the Blocked IP and Allowed IP policies with a variable. See1. See2.
• An Excel Export feature has been added to the Credential page. See.
• A feature has been added to the profile page that allows users to select a project by default. This means that users are now required to select a project each time they open the screen. See.
• It is now possible to view group information via API Traffic Details for requests received through the API Proxy Group.
• If Task Flows are not managed with Kubernetes Apinizer, a warning message is now displayed on the screen, and the WARN message on the screen has been revised.
• Frequently used values have been added by default to the variables menu under the management menu.
• During environment creation, cache and worker server addresses were trimmed in both gitops and normal methods.
• The JSON Schema library has been changed. See.
• Ensured that the Request Address field always appears as a single piece in the API Traffic screens.
• Swagger display has been removed from the specifications in API Proxy, but access via endpoint has been maintained.
• An XML/JSON formatting feature has been added to the Base64 Decode/Encode tool. Its name has been changed to Data Processing. See.
• When SOAP is parsed in SOAP to REST, the existing settings in the template are retained.
• The API Products interface has been improved. See.
• The use of “{}” as a path parameter between “/” in the path parameter has been extended so that it can also be used as “/value{param}/”.
• The API Portal now allows identity and analytics information to be retrieved from the configuration. See.
• Analytical reports have been standardized. See.
• Due to the MongoDB restriction, a 1MB limit has been added to the body size in the step-by-step tracking log records.
• API Proxy, refresh and delete buttons have been added to the step-by-step trace tab. See.

BUG FIX