Release Notes - 2022

Version 2022.12.1

Publication Date: December 7, 2022

NEW FEATURE

The Code Snippet tab was added to the Test Console, enabling the generation of the code required to send the request via cURL.. See.

IMPORTANT IMPROVEMENTS AND CHANGES

In the API Traffic screen's search panel, the Request Address and Routing Address fields in the Basic tab have been improved. See: To implement these improvements, the Index Mapping Type has changed, so it's recommended to reindex old indexes to enable searches on these fields in older data. For reindexing See.
The ignore setting for the error response template is now managed via the API Proxy Group. See.
Improved the user experience of the API Proxy Group screen. See.
The user experience of the IP Group selection dialog has been improved.
Nodes are now listed on the Kubernetes Resources screen. See.
Endpoints tab added to API Proxy Group screen to list, filter and view details of all methods/endpoints. See.

BUG FIXES

Issue No	Description
APNZ-3335	When null values are sent to bit and int type fields in methods prepared with Select SQL Statement via DB-2-API, false or 0 values are received in the response instead of null values.
APNZ-3324	When an edit operation (policy etc.) is made on the API Proxy, the previous value of the edited routing address is used.
APNZ-3323	When creating an Advanced type query on the API Proxy Traffic screen, all results are displayed, but the query does not work.
APNZ-3316	When a policy is added after editing the Endpoint or Protocol Transformation, it creates a duplicate copy.
APNZ-3315	When an API Proxy added to the Proxy Group is deleted from the API Proxy list, it is not deleted even if a 'Successful' result is returned.
APNZ-3310	In the Endpoints tab of the Proxy Group screen, the error "This page is not responding" is received.
APNZ-3309	When trying to add Backend API Auth to the Proxy Group, the screen breaks.
APNZ-3306	Although it works when the SQL written in the DB-2-API module is tested on the Manager screen, an error is received when it is deployed to the API proxy and its operation is tested through the API Proxy.
APNZ-3305	When creating an API Proxy with a PostgreSQL type DB-2-API, a connection problem is encountered.
APNZ-3290	Portal Administrator (API Portal Manager) and Analyzer privileges added while editing a user do not work properly.
APNZ-3279	Although there are records on the Token Requests and Report Generator screens, records beyond 100 cannot be displayed due to pagination number limitation.
APNZ-3278	The API Proxy filter cannot be selected multiple times on the API Traffic screen.
APNZ-3277	When a global policy is exported and then tried to import, the operation is not performed even though it is shown as successful.
APNZ-3012	The endpoints with Get method of the REST2SOAP type API Proxy remain as body objects in the OpenAPI documentation.

Version 2022.11.1

Publication Date: November 1, 2022

NEW FEATURE

When a log setting is configured directly on the API Proxy, it is now allowed to override the project-level log configuration. This behavior can also be reversed. See1. See2.
Methods that receive path parameters directly after the root path (without a method name) are now supported.

IMPORTANT IMPROVEMENTS AND CHANGES

It is now possible to edit the response returned when testing a method created via Db-2-API. This allows users to modify sample response data or remove sensitive information, ensuring that the API specification reflects the correct data. See.
After republishing an Environment, its pods are now automatically restarted.
Changes were made to the required fields for reparse and soapToRest expressions in Management APIs. See.
On the Kubernetes Resources page, all namespaces belonging to an environment and their associated pods can now be viewed, deleted, and their logs accessed.
When the Hide in Spec File option is enabled for an API Proxy method, if the Data Model used in that method is not used by any other methods, it is excluded from the specification file.
The ability to delete pods directly from the Kubernetes Resources screen has been added. See.
In the Queries and Report Generator screens, it is now possible to export query results in Excel format and to view parameter, header, and body data in a dialog box when testing a query. See1. See2.
The Deploy All option has been removed from the API Proxy detail page. This operation should be performed in a controlled manner at the environment level.
The user experience of the project selection dialog has been improved. See.
An Advanced section has been added to the filter area on the API Traffic screen, allowing the use of custom query filters. See.
In the API Traffic screen at the project level, clicking the API Proxy name now redirects to its detail page.

BUG FIXES

Issue No	Description
APNZ-3252	An error is received while undeploying the API Proxy.
APNZ-3245	If the response is successful and an error is received from a policy on the response line, the error code is not overridden with the policy's error code.
APNZ-3243	There is no Delete method in the documentation for the Open API type generated from Apinizer.
APNZ-3225	The process of exporting the global policy and importing it into a project other than the project named Default does not work properly.
APNZ-3218	If there is no path information while taking a backup, it does not give an error.
APNZ-3216	It must be ensured that the document returned as a Byte Array can be returned as an encoded string by default.
APNZ-3206	When running the WS Security STS Token policy in Trace mode, API calls are not visible.
APNZ-3203	When LDAP Provider is selected as the Identity/Role/Group Service in the policy and you come back to edit it, the value of this field appears as the default value.
APNZ-3202	When logging traffic records, the maximum size of the body information should be checked to ensure it does not exceed 10 MB after the Sensitive Data Management (Privacy Settings) settings are applied.
APNZ-3201	The Remote Address information on the Login Audits screen appears incorrect.
APNZ-3200	When navigating to the APIs page in the API Developer Portal, an error is received in the console.
APNZ-3197	When importing Credentials as CSV, the default fields in the Token Settings tab are not selected.
APNZ-3191	When adding a new Key Store, when the first definition is made, an error is received in the console and it is not added.
APNZ-3185	Backups are not appearing on the Backup History page.
APNZ-3180	Although the ProCrypt setting (ProCrypt Settings) is disabled on an application-by-application basis, it appears in the Settings tab of the API Proxy.
APNZ-3030	When changing the method name on API Creator (DB-2-API, Mock and Script API) where API Proxy is created, the policies in the API Proxy's method are lost.
APNZ-3011	When the Get method is created with Db-2-API, the requestbody object is created empty in the OpenAPI documentation.
APNZ-2674	In some of the existing examples on the JSON Path Test screen, the response comes back empty.

Version 2022.10.1

Publication Date: October 1, 2022

NEW FEATURE

Creating a Common Query Model

The Common Query Model is the metadata that describes the types of data contained within the message (usually in the body). Globally generated models are used when designing the API definition file.

For detailed information, see Design -> Common Query Model.

Kubernetes Resources Management

Making general settings related to Apinizer Platform's Environments, defining Pod Security Context, configuring servers (Management Console, API Integrator and API Portal), restarting and disabling/removing pods, monitoring all pods and accessing their logs, and monitoring the Kubernetes cluster can be managed through the interface.

For detailed information, see Server Management -> Kubernetes Resources.

ACL Report

The ACL Report is a report screen that provides information about which API proxies users within each organization can access, and which API proxies users within each organization can access. Access data such as Forwarding Address and Data Model can be filtered and displayed. Additionally, the generated report can be exported to Excel.

For detailed information, see the Report -> ACL Report page.

ACL Audit Records

ACL Audit Logs display records of transactions involving credentials that were approved or revoked for access to an API proxy or API proxy group. These records list information such as transaction date, transaction type, reason, user, API proxy/API proxy group, and method. Detailed filtering options are also available.

For detailed information, see the Auditing -> ACL Audit Logs page.

Management API

Apinizer Management APIs enable many operations like API Parse, ReParse, Deploy, etc., without the need for a screen application. This allows Apinizer to be integrated into a DevOps environment.

For detailed information, see the Management API page.

Spec Designer Interface Redesigned

The Spec Design Editor allows users to create new API Definition Documents by filling in a form within the interface, or import and use existing API Definition Documents. This interface has been revised to improve the user experience.

For detailed information, see Design -> Spec Design Editor page.

Performing Captcha Verification on the Login Screen

To prevent malicious attempts to log in to the Apinizer Administration Console, users are restricted to a certain number of incorrect login attempts. After the user exceeds the allowed number of incorrect login attempts in the first stage, captcha verification is activated, forcing them to attempt a predetermined number of login attempts. If the user exceeds the total number of incorrect login attempts, they are locked out and are no longer allowed to access the application.

For detailed information, see the System General Settings page.

In order for the locked user to be able to log in to the application again, this lock must be removed by the Admin from the Users page.

Removing the User from the System During Idle Timeout

In the Apinizer Management Console, the user is logged out if he/she does not perform any action on the application for a specified period of time.

For detailed information, see the System General Settings page.

WS-Security STS Token Policy

This policy addresses the need for the backend web service, which is of SOAP type via Apinizer, to obtain a Token from the Security Token Service.

For detailed information, see the WS-Security STS Token page.

Hiding API Proxy Endpoints

For REST type API Proxies, access to the entire API Definition File can be restricted by obfuscating on a per-API Proxy basis, or access to specific methods from the API Definition File can be restricted by obfuscating on a per-method basis.

See the Settings Tab for API proxy-based access restriction or the Development Tab for method-based obfuscation.

IMPORTANT IMPROVEMENTS AND CHANGES

While viewing the Swagger UI information of an API Proxy Group, all method tabs are now expanded by default. It is now possible to filter by API Proxy criteria, remove method grouping, and sort methods alphabetically. See.
On the API Proxy page, pressing the Enter key now allows adding a new entry to the Category list.
In the API Portal, the Shared Secret information of a key can now be modified or regenerated.
A time selection option has been added to the date filter field on the screen under the Reports and Analytics menu.
Input fields for code entry on application screens are now resizable.
An Object ID filter has been added to the Audit Records screen. See.
In the Routing settings of an API Proxy, Retry Count on Error (Error Handling Type) and Condition fields have been added under the Connection Settings section. See.
A feature has been added to the Routing settings tab of an API Proxy to allow customizing the error message in the response. See.
The export link for an API Proxy is now also accessible from the dropdown menu on the API Proxy listing screen.
To improve user experience on the API Proxy editing page, the Overview, Settings, Design, and Routing tabs have been updated. See (Overview). See (Settings). See (Design). See (Routing)
To improve user experience on the API Proxy Group editing page, the Overview and Settings tabs have been updated. See.
When defining a variable of type Body, default values are now automatically filled in based on the body type.
When adding a new user and the Login Type is set to LDAP, user information is now queried from LDAP using the configuration defined on the Apinizer LDAP Login page. See.

BUG FIXES

Issue No	Description
APNZ-3178	When I set the Gateway Engine Logs level to Debug from the Applications Logs page, the MongoDB appender's log is constantly printed to the database.
APNZ-3176	Tests performed in the Test Console throw an error when recorded.
APNZ-3174	Creating a second record with the same Content Type value for a response is not allowed in Mock API.
APNZ-3171	When editing the parameter of the method in Db-2-API, the Repetition Type is selected as Multiple, and when you try it, it turns into Single.
APNZ-3168	In Db-2-API, the timeout of Connection Pool Definition for SQL statements of type Batch or Procedure does not work.
APNZ-3168	There is no Connection Timeout field in the database connection configurations. Additionally, the time units in the connection definition were incorrect. (It was entered in seconds when it should have been milliseconds.)
APNZ-3165	When importing a WSDL with a SOAP 1.2 method, only the SOAP 1.1 endpoint is used.
APNZ-3147	The listing on the User page is not working.
APNZ-3139	When you want to add a new Action to the API Integrator task, if there is a Body field in the action, this input field does not appear after the action is saved.
APNZ-3137	The person with Project Owner authority cannot add new members to the project.
APNZ-3135	The Error Message Customization list is not available when editing Authentication policies.
APNZ-3124	Case insensitive method search in API Proxy's Design and Development tab does not work.
APNZ-3117	When you want to edit the configuration of the certificate definition, the certificate details are not shown.
APNZ-3115	When a new method is added to the Mock API, a second copy of the method is created.
APNZ-3112	In the API Call policy, the variable contents for Original Message Data do not change.
APNZ-3102	Token requests are not logged when they are faulty, even though they should be logged.
APNZ-3096	While adding a Variable, an error is received when assigning values to the Context Values section.
APNZ-3095	The namespace appears incorrect in WSA Settings.
APNZ-3082	Character limit error in description field in API Proxies prevents saving.
APNZ-3079	When the role added to the Credential is deleted, when a request is sent to the API Proxy that has one of the authentication policies added, this is not reflected in the request.
APNZ-3068	Even though there is no active patching process on Scheduled Jobs, its control continues.
APNZ-3061	Incoming Message: An error is received due to library incompatibility in the WS-Security (WS Security From Target) policy.
APNZ-3060	In the new API Call policy added to the response pipeline, the Message Template Operation Type field is not initialized.
APNZ-3058	WSA settings are not applied for API Proxy with SOAP2Rest protocol conversion applied.
APNZ-3057	Whenever globally added Plain-Text Authentication, Digest and Base64 policies are opened for editing, the selected fields are reset to default values each time.
APNZ-3042	When the API Proxy with SOAP2Rest protocol transformation applied is added to the API Proxy Group, the body variable of the Script policy added to the response line appears as XML.
APNZ-3041	The Export API Proxy link on the API Proxy page does not work for a user other than Admin and gives an error.
APNZ-3040	Test Console errors; In the Proxy Group List, the Relative Path value is not only displayed for active ones, and not all values in the Endpoints field are displayed in the field.
APNZ-3039	An error is received after deleting the method in Mock API.
APNZ-3038	An error icon is seen on the endpoint created in the Development tab of the Empty API.
APNZ-3032	Importing the WS-Security policy results in errors; the Save button is not clickable, the Delete button is not visible, and the order of the Encryption and Signature fields is broken.
APNZ-3029	After performing operations on the methods in the Development tab of the API Proxy page, the active method selection appears incorrect.
APNZ-3026	When adding existing IP Groups to the Allowed IP List policy, validation errors occur.
APNZ-3021	Context Variable values selected in the Variable are not saved.
APNZ-3010	When adding a new endpoint, the label remains the same even if the state of the Use Byte Array type for Compressed Response (based on the Accept-Encoding value) input changes.
APNZ-2939	Deficiencies were identified during the export and import process of the project.
APNZ-2539	The parameter added to the query of the DB-2-API added method cannot be used in more than one place in the query.

Version 2022.06.1

Publication Date: June 1, 2022

NEW FEATURE

Elasticsearch Snapshot Settings

Snapshots, or backups, of the indexes in a defined Elasticsearch cluster can be automatically created at specified intervals. Configuring this setting defines a Snapshot Lifecycle Management (SLM) policy for the cluster. This allows you to manage backup settings within the cluster without needing any additional plugins, and view historical data containing the results of backups. Snapshots can be manually initiated at any time. For detailed information and usage, please see the Elasticsearch Backup Policy page.

Customizing API Portal Settings/Pages

General settings (logo, title) and page content or specific areas (How It Works, FAQ, Login, Register) on the API Developer Portal can be customized upon request. This allows the Portal Administrator to personalize the content used by clients. This allows content management to be tailored to market dynamics and needs.

IMPORTANT IMPROVEMENTS AND CHANGES

Token Settings have been added to the Credential page, allowing authentication settings to be managed on a per-credential basis. See.
In the API Proxy, the method/endpoint edit dialog now includes the "Enable Download" field and the option "Use Base64 Encoded Text/Byte Array For Compressed Response (by Accept-Encoding value)" to manage the response content. See.
A search filter based on the Routing Address has been added to the API Proxy screen. See.
The log4j level setting can now be changed on a per-API Proxy basis. See.
Screen improvements have been made to enhance the usability of Authentication Policies. See1. See2. See3. See4.
In the Test Console, the display of the sample body taken from the API Definition file has been improved.
The appearance of all sections in the API Call Policy, including Request and Original Message, has been refined. The usage of Body sections has also been improved. See.
Cache settings have been added to the Request section of the API Call Policy, enabling the request result to be retrieved from the cache based on a selected variable. See.
When the API Proxy is in Trace mode, API Call Policy information is now logged.
New variable definitions have been added to the API Proxy, enabling limitation of characters in the error message or response message returned from the API via the XML/JSON Error Response Template. See.
The display of deployment information on the API Proxy and API Proxy Group screens has been enhanced. See.
The "Apply by" field has been added to the API-Based Quota and API-Based Throttling screens, enabling these policies to operate based on a specific variable. See1. See2.
In the Variables screen, the "Context Value" type and values have been added, along with the "Form" option for the Parameter type. See.
New key concepts have been added to the Gateway Environment settings to configure options for multipart HTTP requests for file uploads. See.
The display of members and roles on the Projects page has been updated. See.
The display of error messages in the XML Transformer and JSON Transformer screens has been improved.
The display of error messages in the LDAP Connection Definition and LDAP Identity Provider screens has been improved.
In the Development tab of the API Proxy, a quick search feature has been added to the endpoints/methods section. See.
A Correlation ID filter option has been added to the Application Logs screen for logs related to the Gateway Engine. See.
In the Token Requests screen, the Username or Key information is now displayed. Filter options have been expanded to include API Proxy, Username or Key, and Status Code Bigger Than. See.
New methods have been added to access Swagger and OpenAPI definition files via the deployment address. See.
Features to view the API definition document and its interface for the API Proxy Group have been added.
It is now possible to view the Response Message generated according to the settings on the screen where SOAP2Rest conversion configurations are made.
In the environment settings, PKCS12 type keystore files with a .pfx extension are now also allowed for HTTPS termination. See.
Editing of added configurations on the Key Stores screen has been enabled. See.
A Byte Array Content Types page has been added to the Predefined Variables menu to manage isByteArrayContent values. See.
Necessary options for API Proxy Group and API Call have been added to the Cache Monitoring screen. See.
Authentication information has been added to the API Specification data in Swagger and OpenAPI format.
When an API Proxy is reparsed, the name and description information is now fetched from the original API Proxy.
From the selected API Proxy Group page, it is now possible to view the endpoints of all APIs via the Swagger interface.
It is now possible to create an API Product using an API Proxy Group.
If the "Apply to API Proxies" feature is enabled for API Proxy Group settings, configurations such as CORS, Log Settings, XML/JSON Error Response Template, Forwarded IP Header Parameter, and Log Settings can now be managed from the API Proxy Group screen and applied to all API Proxies within.
If an API Proxy is added as an API Proxy Group, deployment information for the API Proxy Group is listed in addition to the related API Proxy deployment information.
When creating a Gateway Instance, the option to select which Kubernetes worker node the environment will run on has been added.
The ability to add multiple example responses to a single endpoint when editing a Mock API definition has been developed.
An API Security role has been added to manage the Identity Management section on a per-project basis.
New lists and dialogs for viewing API traffic logs and log details have been added. The filter criteria now include the method name.
In the WS-Security to Target policy, "Signature Digest Algorithm" and "Use Single Certificate" fields have been added to the Signature section, and "Key Identifier Type," "Custom Identifier Type," and "Custom Identifier Type Value Type" fields have been added to the Encryption section.
The "Log Key" field has been made editable to allow ILM Policy and Template information of deleted Elasticsearch Cluster definitions to be reused in other clusters. Additionally, clicking on the boxes showing ILM and Template statuses on the clusters list screen now allows the corresponding ILM or Template status to be updated.
API-Based Quota and Backend API Authentication policies created only locally can now be created globally through the Global Policies menu.
During backup, selected MongoDB collections can be excluded. This prevents records kept for logs from being included in the backup file, helping to control backup file size.
Two new operations have been added on the Environment Settings page regarding JWT generation: regenerating and uploading the token, and generating and uploading the token by loading the private key from a file.
A "SOAP Action" field has been added to the WSA settings, which can be updated per method for SOAP-type API Proxies.
General settings in Privacy Management are now applied to requests coming from outside the API Proxy as well. Thus, even if requests are sent to an incorrect address, their sensitive data remains protected.

BUG FIXES

Issue No	Description
APNZ-3004	Gateway Environments re-encrypt the saved password for HTTPS when republishing or publishing is done.
APNZ-2903	Path parameter containing spaces is incorrectly sent to the API.
APNZ-2976	Searching for parameters and header sections using keyword criteria on the Queries page does not work.
APNZ-2974	If "example" is empty in the API Definition file on the Test Console, a selection must be made according to the API type in "examples".
APNZ-2963	When a request is sent to a StoredProcedure type method created with DB2API via API Proxy, the formatting of large numbers in the response is corrupted and appears to be in scientific notation.
APNZ-2956	The sample request body created from the Design tab of the API Proxy does not appear in the test console.
APNZ-2955	An error occurs when trying to create a sample request and response body from the Design tab of the API Proxy.
APNZ-2952	Parameter information of web services added as WSDL type is not coming to the test console.
APNZ-2948	After saving the Rest2SOAP Protocol Transformation, the changes are not reflected in the Design tab.
APNZ-2947	It throws an error while parsing the WSDL of KPS services.
APNZ-2943	Any edits to Gateway Environments will break the pod selection to "all".
APNZ-2933	The order of processing of policies in the response line of the logs in the Trace tab of API Proxy is shown in reverse.
APNZ-2931	While testing the Database Identity Provider, the username and password field values are used incorrectly.
APNZ-2930	Sample message values in DB-2-API are not automatically received when the API Proxy is created and tested.
APNZ-2923	When the policy added in the API Proxy Group is removed, the status information remains as deployed.
APNZ-2899	When clicking on the method from the API Design screen, an error is received.
APNZ-2895	An error occurs when importing local policy into API Proxy.
APNZ-2983	When a method/endpoint is added or updated, the policy icon in the API Proxy flow structure disappears.
APNZ-2881	In API Proxy Group, Apinizer does not use error message templates.
APNZ-2880	When CORS is added, the status codes of responses from requests with HTTP method other than Options are corrupted.
APNZ-2876	Errors occur when API Spec information is displayed as Swagger 2.x format.
APNZ-2873	The pagination component on the API Proxy Traffic screen is missing.
APNZ-2870	If Content-Type "application/x-www-form-urlencoded;charset=UTF-8" is sent in the JWT Token purchase message, an error is returned.
APNZ-2868	Some services do not include models in the Open API format specification information produced for WSDL.
APNZ-2864	In the dialog where any credential is added to the API Proxy Access Control List (ACL) list via the Credentials menu, the filter selection such as project is not reflected in the list without pagination.
APNZ-2862	In cases where the API Proxy Group is installed in more than one environment, if one is redeployed, the others are put in a redeploy required state.
APNZ-2861	Time fields in JWT Token responses are not in ISO 8601 format.
APNZ-2855	When the instance of the Rest2Soap type API Proxy is changed via the Design tab, this is not reflected in the Swagger documentation and Test Console.
APNZ-2846	In Mock API, multiple responses can be generated to the same endpoint with the same status code.
APNZ-2841	While adding a condition on the Routing tab of the API Proxy page, even though the "does not contain" function is selected, it does not appear in the component when updating the condition.
APNZ-2836	When API Integration is run, it only returns one result.
APNZ-2829	When a SOAP web service is created as a REST API, the changes made during the protocol conversion are not reflected in the Design.
APNZ-2828	When changes are made to Rest-to-SOAP type API Proxies via Jackson Transformation, they are not automatically displayed in the Test Console.
APNZ-2826	When the API Proxy is re-parsed, the text in the dialog appears incorrectly.
APNZ-2824	When the endpoint is tested with the API document via the API Portal, it gives a CSP error.
APNZ-2819	When trying to create an API Proxy via Open API, it gives an error.
APNZ-2818	When trying to create an API Proxy by uploading a file, the file component in the dialog that opens gives an error.
APNZ-2805	When multiple API Proxies are created from DB-2-API, the Install All API Proxy button on the DB-2-API screen does not work.
APNZ-2797	The Log tab in the Test Console gives an error.
APNZ-2788	The example section of the Open API documentation is not coming properly.
APNZ-2787	Crash when adding Authentication policy in API Proxy Template screen.
APNZ-2783	The Collection tab on the Test Console does not match the collection list in the Collection List.
APNZ-2782	A second Key Store definition is not added to the WS-Security policy.
APNZ-2763	Condition error in routing; when conditional routing is added, the query cannot distinguish based on parameters.
APNZ-2760	API Proxy does not function properly when too many credentials are added to an API Proxy via ACL or when selections are made on different pages of the table. Additionally, added credentials can be reselected after deleting filters in the credential selection dialog.
APNZ-2756	When the endpoint addition and editing operations of the Empty API type API Proxy are made in the Design tab or the Develop tab, the changes here cause the data of the relevant path fields (Backend Path, Name, Description) to not work asynchronously.
APNZ-2723	After the API Proxy Group is registered or redeployed, the API Proxies go into redeploy mode.
APNZ-2749	When adding an endpoint to the mock API, the body of the default response in the Response Information was edited and saved. When this response was later displayed, it was observed that this information did not change with the given value.
APNZ-2744	While trying to create an API Proxy by uploading the API's spec file, when multiple file operations are performed in the input field, this input gets stuck and the assigned data does not change.
APNZ-2742	Even when "Use a variable" is selected and saved in the Modify Original Message field in the API Call Policy, the "Specify the Value" option remains selected.
APNZ-2741	The value for the Identity/Role/Group Service field cannot be selected in the Digest Authentication policy.
APNZ-2572	When selecting certificates with the same name from different environments in the Test Console, it is not clear which certificate belongs to which environment.

Version 2022.02.1

Publication Date: February 1, 2022

IMPORTANT IMPROVEMENTS AND CHANGES

The ability to create API Proxy Group access lists for Credentials has been provided.
The display of detail and stack trace information in the Application Logs screen has been improved.
The security vulnerability originating from Log4J has been permanently fixed.
Definitions created in Sensitive Data Management can now be applied to form-data type data.

BUG FIXES

Issue No	Description
APNZ-2706	The data for the Authentication and Incoming Message WS-Security policies for the Backend API appears to be incorrect.
APNZ-2702	When you want to add a new query or filter on the Query with Anomaly Detector and Report Generator screen, you can enter blank values even though the fields are required.
APNZ-2690	In the input field on the Authentication Policy and Backup Settings screens for the Backend API, passwords only appear masked.
APNZ-2689	The fields requiring passwords in the Authentication policy for the Backend API are encrypted more than once.
APNZ-2628	Autofill field in CORS component throws database error.
APNZ-2684	Republishing on the Gateway Environments screen does not work stably.
APNZ-2683	When you copy and paste it into the host alias field on the Gateway Environments screen, it is created with new lines and space characters.
APNZ-2682	When an edit is made to Elasticsearch Clusters, the boxes showing the status information for Index Templates turn red.
APNZ-2681	Since there is no TLS 1.2 support in databases prior to MSSQL 2014, Db2Apis created with these connection definitions give TLS errors.
APNZ-2678	A dysfunctional component appears in the CORS Headers screen.
APNZ-2670	The selected log information on the Token Requests screen is delayed.
APNZ-2664	When a request is made to the access address given to the Manager console with a non-existent relative path, it is not logged.
APNZ-2660	API Proxy Group pagination section is not visible.
APNZ-2656	The Roles field in the authorization policy is not working properly.
APNZ-2655	In the authorization policy, the Roles component is visually below another component.
APNZ-2622	HTTPS requests sent to the Elasticsearch cluster via the management console are not going through.
APNZ-2615	On the API Proxy screen, the API Based Throttling policy cannot be selected globally.
APNZ-2613	The API Definition Editor does not allow creating endpoints from special characters.
APNZ-2563	The project information assigned to the Gateway Environment does not appear complete.
APNZ-2717	Unloaded media do not appear on the API Proxy and Proxy Group screens.