Release Notes - 2021
Version 2021.11.1
Publication Date : November 1, 2021
NEW FEATURES
- The first version of the Apinizer API Developer Portal has been released!
The API Portal is an important communication channel for APIs, acting as a bridge between API Providers and API Consumers. API Providers define the API Proxies they want to expose to the outside world from the Apinizer Manager Console. API Consumers manage how they can communicate with an API through the Apinizer API Developer Portal. The goal is to enable API Providers to easily share their API Proxies and make them available for consumption. Additionally, Apinizer provides features such as design customization on the API Developer Portal, access to and testing of API documentation via the API Catalog, definition of Terms & Conditions, API analytics, monitoring of API traffic, account management, identity management, and access control based on API and identity information.
- Portal API
The API Developer Portal Administrator can create APIs from the API Proxy via the administration section. This allows external sources to access the API Proxy through the assigned environment. The Portal Administrator also manages the API's accessibility from here.
- Portal Accounts
The API Developer Portal Administrator defines accounts that can log in to the API Developer Portal, whether they are organization administrators or not. An account that is an organization administrator has the authority to create other accounts belonging to its sub-organizations. The account can manage the APIs assigned to it or assign them to another account. Each account specifies its own credentials for sending requests to the API. Additionally, API access control based on credentials or API-based credential access restrictions can be implemented.
- Portal Settings
The API Developer Portal Administrator configures personalization, email management, terms & conditions, and integration processes that apply across the entire portal.
IMPORTANT IMPROVEMENTS AND CHANGES
- Worker application logs can now be monitored via the Application Logs tab on the API Proxy screen.
- Management of historical information related to credentials and APIs to be used on the portal UI side has been added to Audit Logs.
- A CorrelationID filter has been added to the API Traffic screen.
BUG FIXES
Issue No | Description |
|---|---|
| APNZ-2593 | Even though the identity information has been removed from the contract, the relationship is still visible. |
| APNZ-2599 | Not every object has a control record. |
| APNZ-2601 | The identity information in the expired contract can be requested and does not generate an “Expired Contract Date” error. |
| APNZ-2605 | WS-Security policy is throwing an error. |
| APNZ-2606 | Deletion and filtering operations do not work consistently on the application logs screen. |
| APNZ-2607 | Audit pages/tabs are not opening. |
| APNZ-2609 | The identity information is not working in the ACL tab of the project filter. The same API proxy can be added to the identity information more than once. |
| APNZ-2619 | When I log in, it acts as if the project is not selected even though it is. |
| APNZ-2624 | An error occurs when a parameter is used in multiple places in DB-2-API. |
| APNZ-2638 | Even though the option to add the user to the header is enabled in the JWT Authentication policy, there is no header added in the log. |
| APNZ-2640 | Authentication token retrieval error is not recorded in token logs. |
Version 2021.06.1
Publication Date : June 1, 2021
NEW FEATURES
- API Proxy Template
With the API Proxy Template that can be defined for each project, all API Proxies in that project are created in accordance with the specified template. This way, definitions that are common to all or most API Proxies, such as Cache, CORS, Authentication, Error Response Template, Forwarded IP Header Parameter, API Based Quota, and API Based Throttling, can be made once, reducing the workload for API Developers. The features provided by the API Proxy Template can be customized for the API Proxy if desired. For detailed information and usage, refer to the API Proxy Template page.
- Mock API Creator
With Mock API Creator, Mock APIs that return predefined responses for requests can be created easily and quickly. These responses can be customized according to conditions. RESTful Mock APIs created in this way can be used for purposes such as prototyping or testing. For detailed information and usage, see the Mock API page.
IMPORTANT IMPROVEMENTS AND CHANGES
API Creator → In the DB-2-API module, a feature for defining parameters in list form has been added to support the writing of IN queries.
- Added cursor return value for Oracle database.
BUG FIXES
| Issue No | Açıklama |
|---|---|
| APNZ-2483 | Elasticsearch authentication error. |
| APNZ-2480 | The parameters are not visible in the sample messages created for the Soap2Rest API Proxy. |
| APNZ-2479 | The conditions previously entered in the Mock API Reparse process are lost. |
| APNZ-2477 | Error in backend digest authentication policy. |
| APNZ-2476 | There is an issue with missing definitions for API Proxies in Privacy Manager. |
| APNZ-2475 | If the element name is empty in the privacy manager screen, the Save button should be disabled. |
| APNZ-2472 | Error messages are not appearing on the Soap2Rest screen. |
| APNZ-2469 | The Response is incorrect in the Swagger and Open API Spec created for DB-2-API. |
| APNZ-2457 | The newly added method to DB-2-API does not appear in the API Spec. |
| APNZ-2454 | The API Developer role in the project cannot delete API Proxies. The API Manager role cannot view global policies. |
| APNZ-2453 | If values such as {{}} appear in the mail body in Mail Connector, a null error occurs. |
| APNZ-2441 | OUT parameters belonging to the stored procedure in DB-2-API appear as IN parameters in the API Spec created for this DB-2-AI. |
Version 2021.05.1
Publication Date : May 1, 2021
NEW FEATURES
- Script Connector
Script Connector, Action, and Task Flow definitions enable various operations to be performed using JavaScript and/or Groovy language.
- Project Full Export
All assets defined in a Project can be exported for the purpose of creating a new project with the same settings by backing up or importing them.
- API Proxy Groups
API Proxy Groups allow multiple API Proxies to be managed and deployed as a group for configuring policies and controlling access. By disabling the individual URLs of the API Proxies in the API Proxy Group, access can be provided through the API Proxy Group's URL. For detailed information and usage, see the API Proxy Groups page.
- Identity Management
It enables the identities of clients (API consumers) that can access API proxies to be managed from a single point and Access Control Lists to be created easily. For detailed information and usage, see the Identity Management page.
- DB-2-API Cursor support
Cursor support has been added for methods/endpoints that use Stored Procedures in the DB-2-API module. For detailed information and usage, see the DB-2-API page.
- Agreement/Protocol
It enables the management of issues such as who can access API Proxies, when they can be accessed, which contract/protocol they are subject to, when the contract/protocol expires, and the automatic closure of access to API Proxies accordingly. For detailed information and usage, please refer to the Contracts/Protocols page.
IMPORTANT IMPROVEMENTS AND CHANGES
- Identity information in CSV format obtained and/or prepared from any system can now be easily uploaded to the Apinizer identity pool.
- A quick search feature has been added to the Test Console when selecting API Proxy via the Name and Gateway Address fields.
- A Connection Pool structure has been established for Elasticsearch and Routing to improve the performance of worker servers.
- Delete phase settings for apinizer-log-ilm-policy -elas lifecycle have been added to the Elasticsearch configuration.
- The ability to define the purpose of API Proxies and filter API Proxies opened within and/or outside the organization/company has been added.
- The ability to test API Proxy Groups in the Test Console has been added
BUG FIXES
| Issue No | Description |
|---|---|
| APNZ-2428 | When I click the try button in DB-2-API, an error occurs and the try button does not work. |
| AC-2011 | The “enable relative path” field in the project cannot be disabled. |
| AC-2209 | When creating a revision, the old revision should be visible. |
| AC-2213 | The name of the test created in the Test Console cannot be changed. |
| AC-2334 | API Integration returns a null error when disabled without creating a server configuration. |
| AC-2352 | When you import Swagger and create a spec on the Spec API screen, the server information does not appear. |
| AC-2372 | When Circuit Breaker and Client Flow Banner are enabled, some required fields can be left blank. |
| AC-2387 | The integration application does not send emails and gives a dependency error when running in production mode. |
| AC-2388 | In the API Proxy created from DB-2-API, the parameters of the selected endpoint are not appearing in the Test Console. |
| AC-2391 | Privacy Management is showing an error in the API Proxy Settings tab and the list is not loading. |
| AC-2400 | If no project is selected, the Connection Management menu appears on the left side of the project menu even though you do not have permission. |
| AC-2410 | In analytics, if Total Time and Routing Time are the same in the Response Time graph, the graph is displaying incorrectly. |
| AC-2412 | When the last 5 minutes are selected in the Analytical Dashboard, some results are missing from the graphs. |
Version 2021.03.1
Publication Date : March 1, 2021
NEW FEATURES
- API Proxy Cloning
The ability to clone an API Proxy and thus create a new API Proxy with the same settings but a different name has been added. Cloning an API Proxy is a very useful method, especially when you want to open a new version of an API Proxy from a different address. For detailed information and usage, see the API Proxy Cloning page.
- Single and Distributed options in Load Balancing
Single and Distributed options have been added for Load Balancing in the API Proxy Routing section.
Single: Each Worker server keeps its own routing information for load balancing. This provides a significant performance increase in the routing process. However, when the load is distributed among the Worker servers, it does not guarantee 100% compliance with the selected algorithm (Round Robin, LRU, Weighted, etc.).
Distributed: During load balancing, a distributed cache is used to determine which Worker server the request will be sent to. This ensures that the load is distributed among the Worker servers in accordance with the selected algorithm (Round Robin, LRU, Weighted, etc.) 100%. However, performance is worse than the Single option.
For detailed information and usage, see the Routing Tab -> Load Balancing page.
- APICyrpt
APICrypt enables encrypted communication by passing request/response messages through an HSM device.
- Syslog Integration
Log records can also be written to Syslog and integrated with central log systems. For detailed information and usage, see the Syslog Settings page.
- Empty API
Empty API allows you to create an API proxy for APIs/web services that do not have an API definition file. This makes it easy to open code-first developed APIs via Apinizer. For detailed information and usage, see Creating an API Proxy -> Empty API page.
- Test Tools
Test tools can be used to send requests to APIs/Web Services and see whether a response is returned or not, or to view the content of the response. This allows you to quickly perform tests without leaving the Apinizer environment. For detailed information and usage, please refer to the Test page.
- Test History
A history is kept for all tests performed. It is possible to run the same tests using the records in the history.
- Test Collections
As test usage increases, it can become difficult to use the history. It is possible to make it more manageable by creating Test Collections and grouping test definitions.
- Testing with Logging
If there are requests with errors, they can be immediately retried from within the interface that displays the log records. This allows for quick and easy retesting by directly retrying the request that caused the error, without having to perform any search operations.
Expired Token Cleaner
A task has been created to automatically delete expired tokens stored in the database. If desired, the Apinizer administrator can stop this task from the Administration → Scheduled Jobs menu or restart it at any time. For detailed information and usage, see the Scheduled Jobs (ExpiredToken task) page.
IMPORTANT CHANGES AND IMPROVEMENTS
- The Endpoint to be opened for the relevant Task Flow in the Task Flow screen is passive by default, but users can activate it if they wish.
- If there is no SOAPAction header in the Soap1.1 service, the SOAPAction described in the WSDL is automatically added.
- The Error Message screen in the Admin menu has been revised for easier identification.
- The JDBC URL Template is now provided by default for database connectors.
- The Test Console and Test Tools have been added to the top menu so that they can be easily accessed from anywhere within the application.
- When changes are made to global policies, all API Proxies that use them are displayed on the same screen and can be redeployed.
BUG FIXES
| Issue No | Description |
|---|---|
| APNZ-2034 | An error appears in the browser console when retrieving the API proxy list for the Test Console. |
| APNZ-2091 | When the API Proxy creation type is KPS, the REST to SOAP option does not appear. |
| APNZ-2111 | There are errors in the test section of the LDAP Authentication Provider's advanced settings. |
| APNZ-2114 | Errors occur when updating the Integrator Environment. |
| APNZ-2121 | Parameters of type body are not visible in the DB-2-API Spec file. |
| APNZ-2021 | Even though the email action has been disabled, it is still sending emails. |
| APNZ-2096 | Errors are occurring on the Heartbeat Monitor screen. |
| APNZ-2136 | When only ‘/’ is written in the Apinizer rootcontext, a null error is received in the Service Access Address. |
| APNZ-2138 | In the Business Rule policy, an error occurs at runtime when “Condition is empty” is selected. |
| APNZ-2150 | An error occurs when statusCode is entered in the Script Policy screen. |
| APNZ-2152 | An encoding error occurs when sending JSON data in the query parameter. |
| APNZ-2148 | When testing the script policy, if an error occurs, the error message disappears before the user can read it. |
| APNZ-2154 | When you first open the API Traffic, API Analytics, and Audit pages in the API Proxy tabs, information about other API Proxies is displayed in addition to the selected API Proxy. |
| APNZ-2156 | The API Proxy returns an error when data is entered in only one of the three fields in the Policy Error Message format. |
| APNZ-2202 | The proxyTime, backendTime, and totalTime values in the Analytics tab of the API Proxy show the values of the incorrect fields. |
| APNZ-2208 | An error occurs when adding Code to the ibr response message in API design. |
| APNZ-2226 | Even if the method/endpoint is disabled in API Proxy, it still returns a response. |