What is new in this release
The WSO2 API Manager version 2.2.0 is the successor of version 2.1.0. It contains the following new features and enhancements:
General Data Protection Regulation (GDPR) Compliance
Compliance with GDPR Regulations with the implementation of the Right to be Forgotten through a tool that allows external user’s personally identifiable information (PII) to be anonymized.
Support for consent management policies for third-party applications and user sign-up pages.
Introduction of cookie policies and privacy policies.
Ability to restrict view/edit rights of APIs to selected user groups on the API Publisher.
Ability to share an application across multiple user groups.
Ability to use any header to carry the Bearer token to the Gateway, instead of the Authorization header.
Ability to upload certs to access back-end services using self-signed certs.
On-Premise/Hybrid API Gateway; an immutable API Gateway that can bootstrap itself on startup with the APIs to host.
API Design and Documentation
Ability to add additional properties for APIs and use those properties in the search option.
Enhanced support for exposing SOAP services as REST APIs by auto-generating the REST interface by parsing the WSDL of the SOAP Service.
- Ability to import and export applications and subscriptions
- Password recovery option for the API Store (Developer Portal).
- Compatibility with WSO2 IAM version 5.5.0 as the Key Manager Profile of API Manager 2.2.0.
What has changed in this release
Removed features and functionalities
No features/functionality have been removed in this release.
Deprecated features and functionalities
This release includes the following features/functionalities that were deprecated, which may be removed in a future release. To view previously deprecated features, see the About this Release page of the previous version.
Gateway Manager profilePrior to WSO2 API Manager 2.1.0, the Publisher and Gateway were required to be on two different cluster domains. However, from WSO2 API Manager 2.1.0 onward clustering is no longer a necessity, because the Publisher can play the role of the Gateway Manager. Therefore, now, the Gateway Manager profile (
-Dprofile=gateway-manager)has been deprecated as it is redundant.
When proper Database Administrative (DBA) practices are followed, the systems (except analytics products) are not granted DDL (Data Definition) rights on the schema. Therefore, maintaining the
-DSetupoption is redundant and typically unusable. As a result, WSO2 has deprecated the
-DSetupoption. Note that the proper practice is for the DBA to run the DDL statements manually so that the DBA can examine and optimize any DDL statement (if necessary) based on the DBA best practices that are in place within the organization.
Analyzing Logs with the Log Analyzer is deprecated from this release onwards and is disabled by default.
This section lists out the features that were updated or introduced newly to WSO2 API-M 2.2.0 via WUM updates.
|Updated or newly introduced feature||The date of the update|
|Defining a custom user claim as the group extractor claim||December 9, 2018|
|Working with Observability||December 19, 2018|
Compatible WSO2 product versions
WSO2 API-M 2.2.0 is based on WSO2 Carbon 4.4.26 and is expected to be compatible with any of the WSO2 products that are based on any Carbon 4.4.x version (except when using WSO2 Identity Server as a Key Manager, in which case you must use WSO2 Identity Server 5.5.0). If you get any compatibility issues, please contact team WSO2. For information on the third-party software required with API-M 2.2.0, see Installation Prerequisites. For more information on the products in each Carbon platform release, see the Release Matrix.
For a list of known issues, see WSO2 API Manager 2.2.0 - Known Issues in Github.
For the latest performance test results, see WSO2 API-M Performance and Capacity Planning.