Re: [Architecture] [RRT] Improving caching based on cache-control and ETag headers

Hi Keerthika, We should have an option for disregarding the cache-control headers and the default value should be that the cache-control headers be disregarded. This is because the current cache mediator is written so that it is fully backward compatible with the older versions of the cache

[Architecture] WSO2 API Manager 2.1.0-update6 Released!

The WSO2 API Manager team is pleased to announce the release of version 2.1.0-update6 of API Manager. *WSO2 API Manager is a platform for creating, managing, consuming and monitoring APIs. It employs proven SOA best practices to solve a wide range of API management challenges such as API

Re: [Architecture] [RRT] XML, JSON, Shema validation threat protectors in APIM 2.1.x

On Fri, Jan 12, 2018 at 3:21 PM, Hasunie Adikari wrote: > Hi all, > > I encounter an issue while writing a unit test to clone the input stream. > I implemented the cloning method[1] a way that gets the input stream from > the passthrough pipe. As I discussed with the EI team,

[Architecture] [IAM] [IS 5.5.0] Request Object persistance

Hi All, In this effort we are storing the processed claims from the request object [1] against the code or the access token. The persistence of JWT will happen when the response comes to the authorization endpoint. 1. Authorization request is sent to the authz EP with the request object.

Re: [Architecture] [RRT] Improving caching based on cache-control and ETag headers

+1. Thanks Riyafa for the suggestion. Thanks, Keerthika. On Fri, Jan 12, 2018 at 3:05 PM, Riyafa Abdul Hameed wrote: > Hi Keerthika, > > We should have an option for disregarding the cache-control headers and > the default value should be that the cache-control headers be

[Architecture] [RRT] CMIS Connector

Hi All, *CMIS* (Content Management Interoperability Services) is the OASIS specification for content management interoperability. It allows client and servers to talk together in HTTP (REST with JSON, AtomPub or SOAP) using a unified domain model. We have planned to implement CMIS connector for

Re: [Architecture] [RRT] XML, JSON, Shema validation threat protectors in APIM 2.1.x

Hi all, I encounter an issue while writing a unit test to clone the input stream. I implemented the cloning method[1] a way that gets the input stream from the passthrough pipe. As I discussed with the EI team, We can't mock the pipe and also there were some obstacles for creating the pipe and I

Re: [Architecture] Identity Server 6

Hi Jørgen, Thank you for bringing this up. As you know the latest released version of the Identity Server is 5.4.0. And there are two releases (5.4.1 and 5.5.0) planned before 6.0.0 Most of the features planned for 6.0.0 were moved to 5.5.0. So with the new plan... 1) The theme of 5.5.0 is

Re: [Architecture] [MB4] Authorization Model for Message Broker

Hi Hasitha, Please refer my comments inline. On Fri, Jan 12, 2018 at 9:56 AM, Hasitha Hiranya wrote: > Hi Waruna, > > In MB 3.1.0 authentication model, we gave publish/subscribe permission > automatically to the user who created the queue. > Are we having same concept here

Re: [Architecture] [IAM] [IS 5.5.0] Request Object persistance

Hi Hasanthi, As discussed offline lets change the schema as in below ER diagram. Further, as we process the Request Object ​while processing the authentication request, then we can save the requested claim information in to the DB against session_id. Once, the authentication is completed and

Re: [Architecture] Identity Server 6

Hi Rushmin, Thanks for the swift reply. We are in the final decision phase on deciding technology for a platform delivering Identity management as a service targeting local municipalities as a first step and then moving into SMB with similar services as a phase 2. It seems improved

Re: [Architecture] [MB4] Restful Admin API's for Message Broker

Hi Asitha, Don't we need APIs to update the existing Queues and Exchanges? This can be achieved by the *PUT *method. Regards, Vinod On Fri, Jan 12, 2018 at 11:22 AM, Asitha Nanayakkara wrote: > +1. At the moment we don't have that feature implemented within broker > core. I

Re: [Architecture] [MB4] Dead Letter Exchange implementation

On Fri, Jan 12, 2018 at 11:27 AM, Hasitha Hiranya wrote: > Hi Asanka, > > +1. Seems we need to consider all clients w:r:t a queue. > In previous model also we had a property to count number of times a > message was delivered and a delivery rule to evaluate but it was >

Re: [Architecture] [MB4] Restful Admin API's for Message Broker

Hi Vinod, Updating queues, bindings, and exchanges are invalid scenarios in AMQP model. On Fri, Jan 12, 2018 at 1:57 PM, Vinod Kavinda wrote: > Hi Asitha, > Don't we need APIs to update the existing Queues and Exchanges? This can > be achieved by the *PUT *method. > > Regards,

Re: [Architecture] [MB4] HA Support

Hi Asanka, Renamed "haConfig" to "failover" based on the offline discussion. Thank you, Maryam On Tue, Dec 19, 2017 at 7:05 PM, Asanka Abeyweera wrote: > Hi Maryam, > > Shall we rename the "haConfig" to "ha-clustering"? I'm not sure if we > should use camel case in the yaml

Re: [Architecture] [MB4] HA Support

Hi All, As mentioned, an extensible point "org.wso2.broker.coordination.HaStrategy" has been introduced, which can be implemented to provide variations upon which HA support will be based. Any new/custom implementation would have to notify the listeners listening on node state changes (when a