WSO2 API Manager 4.3.0-M1 Released! The WSO2 API Manager Team is pleased to announce the release of API Manager 4.3.0-M1
The WSO2 API Manager is a platform for building and managing APIs. It helps developers implement APIs by integrating different types of systems and APIs, and also helps to manage them using its API governance and lifecycle management capabilities. APIs could be built by integrating different types of APIs such as traditional request-response style APIs and event-driven APIs using a low-code/no-code development experience and exposing it to consumers through its API Gateway. WSO2 API Manager 4.3.0-M1 consists of the following main components. *Runtimes* - API Manager download <https://github.com/wso2/product-apim/releases/download/v4.3.0-m1/wso2am-4.3.0-m1.zip> - API Manager Analytics *Tooling distributions* - API Controller download <https://github.com/wso2/product-apim-tooling/releases/tag/v4.3.0-m1> API Manager The API Manager component addresses all aspects of API management in the platform. It consists of an API Gateway, API Publisher, Developer Portal, Key Manager and Traffic Manager. How to run (Ignore steps 1 and 2 if you already have JDK 17 installed on your machine) 1. Install JDK Version 17. 2. Set the JAVA_HOME environment variable. 3. Download <https://github.com/wso2/product-apim/releases/download/v4.3.0-m1/wso2am-4.3.0-m1.zip> and extract the downloaded ZIP file. 4. Go to the bin directory in the extracted folder. 5. Run the api-manager.sh file if you are on a Linux/Mac OS or run the api-manager.bat file if you are on a Windows OS. sh api-manager.sh api-manager.bat --run What's New - API level policy support for API Manager - Support deploy/undeploy global level policies from UI/REST APIs - Role based access control for admin UI & Role based access control for management (admin) APIs - Ability to add revision descriptions for API revisions - Support authentication header name from Publisher portal at API level - Key Manager visibility support in Developer portal - Versioning support for API Products - Application level policies with burst control support - Distributed backend throttling mechanism, a shared counter-based algorithm to efficiently manage API traffic - Engaging an approval workflow when deploying a revision - JWKS endpoint support, enabling seamless validation of backend access tokens send by API gateway - Enhance API tiles. Support optional properties (external APIs, business information etc.) in API Information - Support configuring resource attributes for OpenTelemetry connection Fixed Issues See details of all the changes including improvements, and bug fixes <https://github.com/wso2/api-manager/issues?q=is%3Aclosed+milestone%3A4.3.0-M1+label%3AComponent%2FAPIM> in this release. API Manager Analytics API Manager Analytics provides monitoring and business analytics of the API echo system. API Manager Analytics is hosted as a cloud service. How to use analytics 1. Sign up to Choreo cloud <https://console.choreo.dev/> and register an on premise deployment. 2. Generate a On prem key <https://console.choreo.dev/user-settings/onpremkeys> for the registered environment. The on-prem key represents the on premise API-M environment of your deployment. 3. Open the <APIM_HOME>/repository/conf/deployment.toml to configure cloud analytics. 4. Configure the API Manager for analytics as follow: [apim.analytics] enable = true config_endpoint = "https://analytics-event-auth.choreo.dev/auth/v1"; auth_token = "<on prem token>" 1. Follow the instructions given in the “How to run” section of “API Manager” and start API Manager. 2. Create APIs and generate some traffic in your environment. 3. Log in to the Analytics cloud portal <https://console.choreo.dev/insights/overview> to view the analytics for your environment. 4. Refer to the API manager analytics to learn more about configuring analytics and viewing reports. Fixed Issues See details of all the changes including new features, improvements, and bug fixes <https://github.com/wso2/api-manager/issues?q=is%3Aclosed+milestone%3A4.3.0-M1+label%3AComponent%2FAnalytics> in this release. API Controller (apictl) WSO2 API Controller (apictl) is a command-line tool providing the capability to move APIs, API Products, and Applications across environments and to perform CI/CD operations. It can also be used to perform these same tasks on a Kubernetes deployment. In addition, apictl can be used as a developer CLI tool for Choreo Connect (API Microgateway). Furthermore, it can perform Micro Integrator server specific operations such as monitoring synapse artifacts and performing MI management/administrative tasks from the command line. How to run 1. Select the archive suitable for your platform (Mac, Windows, Linux) from this link <https://github.com/wso2/product-apim-tooling/releases/tag/v4.3.0-m1> and extract it to a desired location and navigate to it. Then execute apictl to start the application. - NOTE: Execute ./apictl if the working directory is the same where the executable resides. - Add the location of the extracted folder to your system's $PATH variable to access the executable from anywhere. 1. Execute apictl --help for further instructions. What's New - Add versioning support to API Products in API CTL Fixed Issues See details of all the changes including new features, improvements, and bug fixes <https://github.com/wso2/api-manager/issues?q=is%3Aclosed+milestone%3A4.3.0-M1+label%3AComponent%2FAPICTL> in this release. Known Issues All the open issues pertaining to all the runtimes and tooling distributions of WSO2 API Manager-4.3.0-M1 are reported here <https://github.com/wso2/api-manager/issues?q=is%3Aissue+is%3Aopen>. How You Can ContributeCommunityYou can use our Discord Channel and Stackoverflow Collective to engage with a wider audience https://wso2.com/community/Reporting Issues We encourage you to report issues, improvements and feature requests through our public product Git repository. - WSO2 API Manager Git Issues <https://github.com/wso2/api-manager/issues> Important: Please be advised that security issues must be reported to secur...@wso2.com, not as a GitHub issue, in order to reach the proper audience. We strongly advise following the WSO2 Security Vulnerability Reporting Guidelines <https://docs.wso2.com/display/Security/WSO2+Security+Vulnerability+Reporting+Guidelines> when reporting the security issues. ~ WSO2 API Manager Team ~ -- *Naduni Pamudika* | Associate Technical Lead | WSO2 Inc. (m) +94 (71) 9143658 | (w) +94 (11) 2145345 | (e) nad...@wso2.com [image: http://wso2.com/signature] <http://wso2.com/signature>
_______________________________________________ Announce mailing list Announce@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/announce
