Version 2024.01.2 Patch
Date of version: March 22, 2024
This section contains Removed Features, New Features, Important Enhancements, Modifications and Bug Fixes for patch version 2024.01.2.
If the Apinizer update is done from the YAML file, the given line in cache-deployment.yaml should be updated to its new version. Otherwise, the Cache won't start.
Old version:
- name: CACHE_SERVICE_NAME
value: cache-http-service.prod.svc.cluster.local
New version:
- name: CACHE_SERVICE_NAME
value: cache-http-service
Removed Features
APNZ-4155 The 4000-character limit for the Product Description field has been removed in the API Portal.
New Features
APNZ-4083 Test Console Audit Screen
A screen for Test Console Audit Logs has been created, displaying tests conducted from the console along with the username. See.
APNZ-4122 Total Number of Methods in Proxies Displayed on the Overview Screen
Information about the total number of methods in proxies has been added to the Overview screen. See.
APNZ-4157 New Report: API Endpoint Creation By Time
API Endpoint Creation By Time report is added to visualize API Endpoints by grouping it by time. See.
APNZ-4158 New Graphics on the Overview Screen
Charts displaying the distribution and count of API Proxies, connections, and HTTP Method types have been added to the Overview screen. See.
APNZ-4160 Getting Claim Value in JWT with Business Rule
Two new fields have been added to the business rule for extracting claim values from JWT: Extract JWT Header Claim and Extract JWT Body Claim. See.
APNZ-4167 Running the Policy Based on Environment
Environment name and ID information have been added to the Context Value in Variable and Script.
APNZ-4185 ZoneID Value in Context Value
ZoneID value can be entered for values containing date in Context Value. See.
APNZ-4190 New Fields in Script and Variable Context Value
New fields have been added to the Context Value in Script and Variable.
APNZ-4202 Accessing Secret Values Belonging to Credential with the Script Policy
Access to secret values belonging to identity information has been enabled with the Script policy.
Important Enhancements and Modifications
APNZ-4084 The ability to enable/disable all policies within the API Proxy method has been added. See.
APNZ-4163 The ability to enable or disable Quick Test has been added to the System Settings. See.
APNZ-4166 Automatic filling of the backend API version during parsing from Swagger and OpenAPI has been added.
APNZ-4170 The option to add JSON as a string or JSON itself has been added to the Jose Implementation policy. See.
APNZ-4171 The entered description for the environment is now visible on the list screen.
APNZ-4173 The popup display of Context Values has been enhanced.
APNZ-4181 The process of extracting the status code from the response has been added to the context variable.
APNZ-4182 The ability to select the client identity with a variable has been added to the Jose Validation policy. See.
APNZ-4191 In JSON Schema Validation, the allowance for an empty JSON path and the capability for separate validation of multiple JSON schemas for the target path have been implemented. See.
APNZ-4192 Allowance for an empty XPath has been implemented in XML Schema Validation. See.
APNZ-4200 When adding actions, for the data types Extract Body and Header, the target variable label has been changed to "Extraction Target Variable".
Bug Fixes
Issue No | Description |
---|---|
APNZ-4096 | Fixed errors related to screens accessible and operable by a user with only the Analyzer role in the development menu. |
APNZ-4149 | The issue of users who cannot log in not being recorded in the audit has been resolved. |
APNZ-4156 | The issue of the authentication information not appearing in the Portal for services created with API Creator has been resolved. |
APNZ-4177 | The issue of the pod list not appearing in Kubernetes resources has been fixed. |
APNZ-4194 | The issue of empty request bodies when adding an API Proxy created with DB2API as a new API Proxy from another project has been fixed. |
APNZ-4195 | Errors encountered during LDAP testing have been addressed and resolved. |