Re: [Architecture] APIM Statistics introduce new field to the Analytics events

Hi, One scenario I faced with a customer is as follows. 1. A Custom HTTP header is coming with each request specifying the region request was originated. 2. At gateway, this needs to be extracted as an field and published to Analyser. 3. Analyser summarises the data and put to a DB

Re: [Architecture] Sharing common SPA components within and between product(s)

It is also possible to link two npm projects without pushing to central repo, see https://docs.npmjs.com/cli/link On Thu, Jan 4, 2018 at 12:00 PM, Kasun Thennakoon wrote: > Hi all, > > In API Manager 3.0.0 we have mainly 3 SPA applications which are > Publisher[1], Store[2],

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

Hi Hasunie, This is expected since the synapse engine now expecting an already built message. If I understood your requirement correctly, one option is to use a Builder Mediator before using any content aware mediator. Even though we do not recommend the Builder mediators now, still we can use it

Re: [Architecture] [X509 Authenticator] Certificate Revocation Verification with CRL and OCSP

Hi, Thanks a lot for your valuable feedbacks. Please find the current implementation details as follows. - Certificate validators can be configured in /repository/conf/security/certificate-validators.xml as follows with configured priorities. This will be added to tenant registry in

Re: [Architecture] [Dev] [VOTE] Release WSO2 Stream Processor 4.0.0 RC2

Hi Raveen, In Carbon 4.4.x code I could see that, 'sh' command[1] is used to determine whether the operating system is Windows or not. So based on the code you have pointed[2],it has changed to 'bash' and now the new 'bash' option is not working on some of the Windows systems. I could confirm

Re: [Architecture] question to updates strategy

On Tue, Jan 2, 2018 at 9:35 PM, Roman CHRENKO wrote: > Hi, Kasun. > > Thank you for your answer. But where can I find OSGI version ranges which > you mentioned in previous post? > > I parsed (by shell script) all JAR files in WSO2 IS installation directory > (994

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

Hi Dushan, On Wed, Jan 3, 2018 at 9:06 AM, Dushan Abeyruwan wrote: > Hi Hasunie, > Current PTT design would build the message whenever if there is content > aware mediator available. However IIRC, I did this *message.builder.the > invoked* thing to cope with the WSO2 ELB we

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

Hi Isuru, Here we are trying to avoid building the message in gateway itself since building the entire malicious payload may lead gateway crashes. Instead of counting limits after building the tree, We manually build the message through third-party library and parser will keep counting nodes

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

Hi Hasunie, Are we gaining a significant performance improvement in this approach by making mediators content-unaware ? To perform these validations messages should be built and we are internally using woodstox in our builders too. At mediator level generally we shouldn't mess-up with

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

Hi Hasunie, Current PTT design would build the message whenever if there is content aware mediator available. However IIRC, I did this *message.builder.the invoked* thing to cope with the WSO2 ELB we had (a few years ago). To be honest, that looks ugly isn it (in terms of overall picture).

Re: [Architecture] question to updates strategy

Hi, Kasun. Thank you for your answer. But where can I find OSGI version ranges which you mentioned in previous post? I parsed (by shell script) all JAR files in WSO2 IS installation directory (994 files), find all "META-INF\DEPENDENCIES" files and there was no reference to

[Architecture] Sharing common SPA components within and between product(s)

Hi all, In API Manager 3.0.0 we have mainly 3 SPA applications which are Publisher[1], Store[2], and Admin[3] apps. We have structured the SPA apps in a way that, an App consists of 2 main elements, Data models and React components. Data models are used to fetch data from REST APIs and