WSO2 API Manager 4.3.0-M1 Released!
Pre-releaseThe WSO2 API Manager team is pleased to announce the release of API Manager 4.3.0-M1!
It's now available to download.
Distribution
You can download API Manager 4.3.0-M1 from here.
How to run
(Ignore steps 1 and 2 if you already have JDK 17 installed on your machine)
- Install JDK Version 17.
- Set the JAVA_HOME environment variable.
- Extract the downloaded zip file.
- Go to the bin directory in the extracted folder.
- Run the
api-manager.sh
file if you are on a Linux/Mac OS or run theapi-manager.bat
file if you are on a Windows OS.
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 in this release.
Known Issues
All the open issues pertaining to WSO2 API Manager-4.3.0-M1 are reported here.
How To Contribute
Your feedback is most welcome!
Community
You 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 regarding WSO2 API Manager through WSO2 API Manager GIT Issues.
And please be advised that security issues must be reported to security@wso2.com, not as a GitHub issue, in order to reach the proper audience. We strongly advise following the WSO2 Security Vulnerability Reporting Guidelines when reporting the security issues.
~ WSO2 API Manager Team ~