Skip to main content

WSO2 released the latest products with GDPR at forefront

WSO2 released the latest product versions of its open source middleware stack with the theme of GDPR (General Data Protection Regulation) compliance. You can learn more about GDPR at below link.
Understanding General Data Protection Regulation (GDPR) and the business impact
Do you know how your personal data is used and exchanged within Facebook or Google? How do you feel if you see your…medium.com
Here are the new product versions released with this theme.
  • WSO2 API Manager 2.2.0
  • WSO2 Identity Server 5.5.0
  • WSO2 Enterprise Integrator 6.2.0 (formerly known as ESB)
  • WSO2 Stream Processor 4.1.0 (formerly known as DAS/BAM)
In addition to these open source products, WSO2 also released it’s very own solution for Open Banking as
  • WSO2 Open Banking 1.0
This release includes the necessary features to make WSO2 platform GDPR compliance in almost all aspects. On top of that, different products have pretty cool new features which customers were looking for quite some time. You can learn about the new features of each product by referring to the following release note links.
About this Release - API Manager 2.2.0 - WSO2 Documentation
About this Release - API Manager 2.2.0 - WSO2 Documentationdocs.wso2.com
About this Release - Enterprise Integrator 6.2.0 - WSO2 Documentation
WSO2 Enterprise Integrator (WSO2 EI) version 6.2.0 is the next level of the ESB, which provides a powerful solution for…docs.wso2.com
About this Release - Identity Server 5.5.0 - WSO2 Documentation
5.5.0 is the successor of version 5.4.1. It contains the following new features and enhancements to comply with the…docs.wso2.com
About This Release - Stream Processor 4.1.0 - WSO2 Documentation
Edit descriptiondocs.wso2.com
Key Concepts - WSO2 Open Banking - WSO2 Documentation
Before getting TPPs connected with the Banks and onboard, they are subjected to a thorough verification. This…docs.wso2.com
Try out these latest products and keep transforming digitally with open source !!!
Labels:

Comments

  1. AnonymousMay 15, 2018 at 11:47 PM

    This comment has been removed by the author.

    ReplyDelete

Post a Comment

Popular posts from this blog

How to protect your APIs with self contained access token (JWT) using WSO2 API Manager and WSO2 Identity Server

In a typical enterprise information system, there is a high chance that people will use different types of systems built by different vendors to implement certain types of functionalities. The APIs might be hosted in an API Manager developed by vendor A and the user management can be implemented using a different vendor (vendor B). In this type of a situation, one system will not be able to directly contact the other system but they want to use both systems in tandem. Self-contained access tokens are used in these types of situations where applications can get the token from one system and use that in another system to access protected resources. In this scenario, the second system does not need to make a contact to the first system over the network to validate the user information since the token is self-contained and it has relevant details about the user. This will improve the token processing time significantly since it completely removes the network interaction. The below fig...
1 comment
Read more

WSO2 ESB creating a response for a "GET" request

When you are creating REST APIs with WSO2 ESB, you may need to send some response message back to the user when something goes wrong. In this kind of scenario, you can create a payload inside the ESB and send it back. For doing this, you can use the below configuration. <api xmlns=" http://ws.apache.org/ ns/synapse " name="LoopBackProxy" context="/loopback">    <resource methods="POST GET">       <inSequence>          <property name="NO_ENTITY_BODY" scope="axis2" action="remove"></property>          <log level="full"></log>          <payloadFactory media-type="xml">             <format>                <m:messageBeforeLoopBack xmlns:m=" http://services...
Post a Comment
Read more

How to configure timeouts in WSO2 ESB to get rid of client timeout errors

WSO2 ESB has defined some configuration parameters which controls the timeout of a particular request which is going out of ESB. In a particular  scneario, your client sends a request to ESB, and then ESB sends a request to another endpoint to serve the request. CLIENT->WSO2 ESB->BACKEND The reason for clients getting timeout is that ESB timeout is larger than client's timeout. This can be solved by either increasing the timeout at client side or by decreasing the timeout in ESB side. In any of the case, you can control the timeout in ESB using the below properties. 1) Global timeout defined in synapse.properties (ESB_HOME\repository\conf\) file. This will decide the maximum time that a callback is waiting in the ESB for a response for a particular request. If ESB does not get any response from Back End, it will drop the message and clears out the call back. This is a global level parameter which affects all the endpoints configured in ESB. synapse.global_timeout_inte...
6 comments
Read more