Skip to content

Releases: wso2/product-microgateway

WSO2 API Microgateway 3.2.10 Released!

17 Dec 05:33
Compare
Choose a tag to compare

What's new in 3.2.10

This is a maintenance release of API Microgateway 3.2.0. This Release includes below improvements and fixes.

Bug Fixes

Fixed Issues

Known Issues

Open Issues

Try it

Quick start guide

Contributing

How To Contribute

Your feedback is most welcome!

Contributing Code

Read through the project Contribution Guidelines to learn how to contribute with code.

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, documentation faults, and feature requests regarding WSO2 API Microgateway through the Github 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--

WSO2 API Microgateway 3.2.9 Released!

08 Jan 06:04
Compare
Choose a tag to compare

What's new in 3.2.9

This is a maintenance release of API Microgateway 3.2.0. This Release includes below improvements and fixes.

Bug Fixes

Fixed Issues

Known Issues

Open Issues

Try it

Quick start guide

Contributing

How To Contribute

Your feedback is most welcome!

Contributing Code

Read through the project Contribution Guidelines to learn how to contribute with code.

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, documentation faults, and feature requests regarding WSO2 API Microgateway through the Github 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--

WSO2 API Microgateway 3.2.8 Released!

03 Oct 09:22
Compare
Choose a tag to compare

What's new in 3.2.8

This is a maintenance release of API Microgateway 3.2.0. This Release includes below improvements and fixes.

Bug Fixes

Fixed Issues

Known Issues

Open Issues

Try it

Quick start guide

Contributing

How To Contribute

Your feedback is most welcome!

Contributing Code

Read through the project Contribution Guidelines to learn how to contribute with code.

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, documentation faults, and feature requests regarding WSO2 API Microgateway through the Github 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--

WSO2 API Microgateway 3.2.7 Released!

24 Apr 13:53
Compare
Choose a tag to compare

What's new in 3.2.7

This is a maintenance release of API Microgateway 3.2.0. This Release includes below improvements and fixes.

Bug Fixes

Fixed Issues

Known Issues

Open Issues

Try it

Quick start guide

Contributing

How To Contribute

Your feedback is most welcome!

Contributing Code

Read through the project Contribution Guidelines to learn how to contribute with code.

User Forum

If you have any questions regarding the product you can use our StackOverflow forum to raise them.

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, documentation faults, and feature requests regarding WSO2 API Microgateway through the Github 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--

Choreo Connect 1.2.0 Released!

22 Mar 12:30
Compare
Choose a tag to compare

Choreo Connect is a cloud-native, open-source, and developer-centric API gateway. It provides first-class support for Kubernetes while facilitating an array of API management quality of services (QoS), such as message security, rate-limiting, observability, and message mediation. It is powered by Envoy Proxy!

Choreo Connect 1.2.0 is compatible with WSO2 API Manager 4.2.0.

What's new in 1.2.0

More in 1.2.0 New Features

Improvements

  • Publish Custom Attributes With Choreo Connect Analytics.
  • JMX monitoring for Enforcer.
  • Include original inbound path in Router access logs.
  • Support subdomain origin in CORS.
  • Create single cluster for Sand and Prod endpoints if the endpoint is same.

More about 1.2.0 Improvements

Bug fixes

Bug fixes

Known Issues

Open Issues

Try it

Quick start guide

How To Contribute

Your feedback is most welcome!

Contributing Code

Read through the project Contribution Guidelines to learn how to contribute with code.

User Forum

If you have any questions regarding the product you can use our StackOverflow forum to raise them.

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, documentation faults, and feature requests regarding Choreo Connect through the Github 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.

--Choreo Connect Team--

Choreo Connect 1.2.0-RC1 Released!

11 Mar 01:51
Compare
Choose a tag to compare
Pre-release

What's new in 1.2.0-RC1

This is the first release candidate of the Choreo Connect 1.2.0.

Choreo Connect is a cloud-native, open-source, and developer-centric API gateway. It provides first-class support for Kubernetes while facilitating an array of API management quality of services (QoS), such as message security rate-limiting, observability and message mediation. It is powered by Envoy Proxy!

Choreo Connect 1.2.0 is compatible with WSO2 API Manager 4.2.0.

Try it

Quick start guide

New Features

  • Graph QL API support
  • HTTP2 support
  • SOAP APIs support
  • Open Telemetry support
  • Mutual SSL authentication for APIs
  • Support Operation Level API Policies
  • JWKS Endpoint for the Enforcer
  • Compression Filter for Choreo Connect

Bug fixes and Tasks

Known Issues

Open Issues

Contributing

How To Contribute

Your feedback is most welcome !

Contributing Code

Read through the project Contribution Guidelines to learn how to contribute with code.

User Forum

If you have any questions regarding the product you can use our StackOverflow forum to raise them.

Discord

Join us via this to our WSO2 Discord account 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 Discord.

Reporting Issues

We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Microgateway through
the Github 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.

--Choreo Connect Team--

Choreo Connect 1.2.0-Beta Released!

22 Feb 08:23
Compare
Choose a tag to compare
Pre-release

What's new in 1.2.0-Beta

This is the beta release of the Choreo Connect 1.2.0.

Improvements, Bug Fixes and Tasks completed

Known Issues

Open Issues

Try it

Quick start guide

Contributing

How To Contribute

Your feedback is most welcome !

Contributing Code

Read through the project Contribution Guidelines to learn how to contribute with code.

User Forum

If you have any questions regarding the product you can use our StackOverflow forum to raise them.

Discord

Join us via this to our WSO2 Discord account 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 Discord.

Reporting Issues

We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Microgateway through
the Github 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.

--Choreo Connect Team--

WSO2 API Microgateway 3.2.6 Released!

30 Jan 11:40
Compare
Choose a tag to compare

What's new in 3.2.6

This is a maintenance release of API Microgateway 3.2.0. This Release includes below improvements and fixes.

Bug Fixes

Known Issues

Open Issues

Try it

Quick start guide

Contributing

How To Contribute

Your feedback is most welcome!

Contributing Code

Read through the project Contribution Guidelines to learn how to contribute with code.

User Forum

If you have any questions regarding the product you can use our StackOverflow forum to raise them.

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

Reporting Issues

We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Microgateway through the Github 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--

Choreo Connect 1.2.0-Alpha Released!

30 Jan 04:54
Compare
Choose a tag to compare
Pre-release

What's new in 1.2.0-Alpha

This is the alpha release of the Choreo Connect 1.2.0.

New Features

  • Graph QL API support
  • HTTP2 support
  • SOAP APIs support
  • Open Telemetry support
  • Mutual SSL authentication for APIs
  • Support Operation Level API Policies
  • JWKS Endpoint for the Enforcer
  • Compression Filter for Choreo Connect

Completed Issues

Known Issues

Open Issues

Try it

Quick start guide

Contributing

How To Contribute

Your feedback is most welcome !

Contributing Code

Read through the project Contribution Guidelines to learn how to contribute with code.

User Forum

If you have any questions regarding the product you can use our StackOverflow forum to raise them.

Discord

Join us via this to our WSO2 Discord account 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 Discord.

Reporting Issues

We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Microgateway through
the Github 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.

--Choreo Connect Team--

Choreo Connect 1.2.0-M1 Released!

15 Jan 12:48
Compare
Choose a tag to compare
Pre-release

What's new in 1.2.0-M1

This is the milestone 1 release of the Choreo Connect 1.2.0.

New Features

  • Graph QL API support
  • HTTP2 support
  • SOAP APIs support
  • Open Telemetry support
  • Mutual SSL authentication for APIs
  • Support Operation Level API Policies
  • JWKS Endpoint for the Enforcer
  • Compression Filter for Choreo Connect

Improvements and Bug fixes

Known Issues

Open Issues

Try it

Quick start guide

Contributing

How To Contribute

Your feedback is most welcome !

Contributing Code

Read through the project Contribution Guidelines to learn how to contribute with code.

User Forum

If you have any questions regarding the product you can use our StackOverflow forum to raise them.

Discord

Join us via this to our WSO2 Discord account 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 Discord.

Reporting Issues

We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Microgateway through
the Github 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.

--Choreo Connect Team--