Re: [Architecture] [Dev] [Vote] Release of WSO2 EI Analytics v7.1.0 RC1

Hi All, +1 from the Security Team as the required security scans got completed. Best Regards, Nadeeshani. On Wed, Nov 11, 2020 at 2:22 PM Chanika Geeganage wrote: > Hi All, > > WSO2 Enterprise Integrator team is pleased to announce the first release > candidate of WSO2 EI Analytics v7.1.0

Re: [Architecture] [Dev] [Vote] Release of WSO2 API Microgateway 3.1.0 RC2

Hi All, Since analysis of the security scan reports are completed, +1 from platform security team to proceed. Best Regards, Nadeeshani. On Wed, Mar 25, 2020 at 8:50 PM Chashika Weerathunga wrote: > Hi all, > > Tested the following scenarios. > > >- GRPC support >- Micro gateway cache

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

Hi All, +1 from Platform Security Team. Thank You, Nadeeshani. On Wed, Jun 20, 2018 at 10:32 PM, Niveathika Rajendran wrote: > Hi, > > I have tested the following and found no issues, > > 1. HTTP Analytics Dashboard > 2. Twitter Dashboard > 3. Authentication & Authorization > 4. Generated

Re: [Architecture] [Dev] [VOTE] Release of WSO2 Identity Server 5.6.0 RC3

Hi All, +1 from Platform Security Team. Thank You, Nadeeshani. On Tue, Jun 19, 2018 at 4:42 PM, Ashen Weerathunga wrote: > Hi All, > > I have tested the following and found no issues. > >- Consent Management for Self Sign Up. >- Creating Users with the Ask Password Option. >-

Re: [Architecture] [Dev] [VOTE] Release WSO2 Enterprise Integrator 6.3.0 RC2

Hi All, +1 from Platform Security Team. Thank You, Nadeeshani. On Mon, Jun 18, 2018 at 7:29 PM, Asanka Abeyweera wrote: > Hi All, > > I tested the basic functionality of a 2 node message broker cluster using > Oracle as the RDBMS. > > No blockers found. > > [+] Stable - go ahead and release

Re: [Architecture] Support for html formatted text in parameters in the template manager

Hi Nadun, You may try to encode the characters in the UI level as in [1]. Encode the required parameters using *Encode.forHtmlContent* or suitable encoding type. For more information about output encoding, follow the Secure Engineering Guideline [2]. This might help to resolve the issue. [1]

[Architecture] Invitation: Tier Implementation Discussion @ Thu Mar 3, 2016 4pm - 5pm (nadeesha...@wso2.com)

ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Kasun De Silva;X-NUM-GUESTS=0:mailto:kas...@wso2.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE ;CN=Nadeeshani Pathirennehelage;X-NUM-GUESTS=0:mailto:nadeesha...@wso2.com ATTENDEE

Re: [Architecture] App Factory Tier Implementation

Hi All, This is the updated user interface design for the *application level tier implementation.* When an application owner creates a new application, he can select the pricing plan for that application. ​ Then, for each application, application owner can choose container specs for the

Re: [Architecture] App Factory Tier Implementation

Hi All, *​Further clarification of Tier User Stories.* Appfactoery set up engineer will define the container_specs. As an example t2.small with the features CPU 1, memory 2 and memeory 4GB. He will also be defining the subscription plans. Then organizations(Tenants) can subscribe to the plans.

[Architecture] App Factory Tier Implementation

structure will be useful for the administration to develop applications for configuring the tiers. Moreover it will be useful to render the subscription plan to the end users through UI. Would appreciate it if you could give your suggestions and comments on this. Thanks, Nadeeshani -- Pathirennehelage