Skip to content

WSO2 API Manager 4.4.0-Beta Released!

Pre-release
Pre-release
Compare
Choose a tag to compare
@RakhithaRR RakhithaRR released this 20 Oct 05:09
· 77 commits to master since this release
v4.4.0-beta
1fe8935

The WSO2 API Manager team is pleased to announce the release of API Manager 4.4.0-Beta!

It's now available to download.

Distribution

You can download API Manager 4.4.0-Beta from here.

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. 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.

What's New

  • AI API Gateway
  • Support sequences as API backends
  • Disable subscription requirement for API consumption
  • Subscription approval support from API Publisher
  • WSO2 Identity Server 7.0 Authorization Server Support
  • Allow privileged users to update subscription business plan for existing subscriptions
  • Support separate client side MTLS for production and sandbox environments
  • Application level throttle policy reset support
  • Filtering support for denylist throttling policies
  • Enhanced content search support with OpenAPI definition search
  • Multi DC Replication support for PostgreSQL
  • Audience Validation support for JWTs
  • Transaction Counter for Gateway

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.4.0-Beta 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 [email protected], 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 ~

Assets 3
Loading