wso2/product-apim v4.0.0-m1

WSO2 API Manager 4.0.0-M1 Released!

on GitHub

The WSO2 API Manager team is pleased to announce the release of API Manager 4.0.0-M1!

It's now available to download.

Distribution

You can download API Manager 4.0.0-M1 from here.

• wso2am-4.0.0-m1

How to run

1. Extract the downloaded zip file.
2. Go to the bin directory in the extracted folder.
3. Run the wso2server.sh file if you are on a Linux/Mac OS or run the wso2server.bat file if you are on a Windows OS.

What's new

• Synchronizing Throttle Policies within Traffic Manager nodes
• Configuring PingFederate as KeyManager
• Configuring Auth0 as KeyManager
• Downloading Postman collection for OpenAPI/GraphQL Schema
• Changing Default Token Expiry Time in Developer Portal
• Role-based scope validation for WSO2 IS connector
• API UUID migration from Registry to AM_API table in APIM database

See details of all the changes including new features, improvements, and bug fixes in this milestone release.

Known Issues

All the open issues pertaining to WSO2 API Manager are reported at here.

How To Contribute

Your feedback is most welcome!

Mailing Lists

Join our mailing lists and correspond with the developers directly. We also encourage you to take part in discussions related to the product on the architecture and dev mailing list. If you have any questions regarding the product you can use our StackOverflow forum to raise them as well.

Developer List : dev@wso2.org
Architecture List : architecture@wso2.org
User Forum : StackOverflow

Slack Channels

Join us via this to our wso2-apim.slack.com for even better communication. You can talk to our developers directly regarding any issues, concerns about the product. We encourage you to start discussions or join any ongoing discussions with the team, via our slack channels.

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 ~