Re: [Architecture] [Dev] Dev][VOTE] Release of WSO2 API Manager 2.6.0 RC3

[Tharindu Dharmarathna]

Hi All,

tested the following  in distributed setup
- Advance Throttling Policies
- Blocking Conditions
- Custom Rules

[+] Stable - go ahead and release

On Sun, Sep 16, 2018 at 9:58 AM Naduni Pamudika  wrote:

> Hi All,
>
> Tested the following with PostgreSql 9.5.
>
> - Basic API creation and invocation
> - Analytics
> - Web socket API creation, invocation and analytics
> - Secure vault
> - Dynamic endpoints
> - Secured endpoints
> - Publisher Rest APIs
>
> Tested Microgateway with Labels, without Labels, and overriding endpoints
>
> [+] Stable - go ahead and release
>
> Thanks,
> Naduni
>
> On Sat, Sep 15, 2018 at 9:09 PM, Chaminda Jayawardena 
> wrote:
>
>> Hi All,
>>
>> According to the latest TestGrid-integration test job which performed
>> with wso2am-2.6.0-rc3 release, has no single failure reported.
>> Generated results can be found here[1] and accordingly we are happy to
>> vote for the release of wso2am-2.6.0.
>>
>> [+] Stable - go ahead and release
>>
>> [1] [Test Grid] WSO2 APIM Integration Test Results #(121)
>>
>> Thanks,
>> Chaminda
>>
>> On Sat, Sep 15, 2018 at 5:33 PM Chamila Adhikarinayake 
>> wrote:
>>
>>> Tested
>>> -  Alerts generation using different user groups (creator, subscriber)
>>> for super tenant and tenant domain
>>> -  Email generation for the alerts for super tenant and tenant domain
>>> users
>>>
>>> No blockers found.
>>> [+] Stable - go ahead and release
>>>
>>>
>>> On Sat, Sep 15, 2018 at 4:55 PM, Rajith Roshan  wrote:
>>>
 Tested following scenarios.

 Basic API creation , publish and invoke flow
 Creating api using swagger
 Build a micro gw by using api created by swagger and invoke the
 resources
 Customize the life cycle to add new state and check the lifecycle
 transitions
 Tested the basic scope validation
 Tested the cross tenant subscription flow
 Tested cross tenant subscriptions with scope validation

 No blockers found.
 [+] Stable - go ahead and release

 Thanks!
 Rajith

 On Sat, Sep 15, 2018 at 4:27 PM Sanjeewa Malalgoda 
 wrote:

> Tested microgateway flows,
>
> Microgateway docker/VM mode with APIM 2.5
> Microgateway  API pull using name and label to create gateway.
>
> Microgateway docker/VM mode with APIM 2.6
>
> +1.
>
> Thanks,
> sanjeewa.
>
>
> On Sat, Sep 15, 2018 at 3:34 PM Nuwan Dias  wrote:
>
>> Tested the following.
>>
>> Basic API creation by creator role
>> Publishing by publisher role
>> User sign up
>> Creation and invocation of SOAP APIs
>> Microgateway VM mode
>> Microgateway docker mode
>>
>> [+] Stable - go ahead and release
>>
>> Thanks,
>> NuwanD.
>>
>> On Sat, Sep 15, 2018 at 10:34 AM Chamila Adhikarinayake <
>> chami...@wso2.com> wrote:
>>
>>> Microgateway RC3 can be found in
>>> https://github.com/wso2/product-microgateway/releases/tag/v2.6.0-rc3
>>>
>>>
>>> Thanks
>>> Chamila
>>>
>>> On Sat, Sep 15, 2018 at 7:04 AM, Chamila Adhikarinayake <
>>> chami...@wso2.com> wrote:
>>>
 Hi All,

 We are pleased to announce the third release candidate of WSO2
 API Manager 2.6.0.

 This release fixes the following issues.

 Fixes : carbon-apimgt
 
 Fixes : product-apim
 
 Fixes : analytics-apim
 
 Fixes : product-microgateway
 

 Source and Distribution,
- Runtime :
 https://github.com/wso2/product-apim/releases/tag/v2.6.0-rc3
- Analytics :
 https://github.com/wso2/analytics-apim/releases/tag/v2.6.0-rc3
- Tooling :
 https://github.com/wso2/devstudio-tooling-apim/releases/tag/v2.6.0-rc1
- Microgateway :
 https://github.com/wso2/product-microgateway/releases/tag/v2.6.0-rc2

 Please download, test the product and vote.

   [+] Stable - go ahead and release
   [-] Broken - do not release (explain why)

 Thanks,
 ~ WSO2 API Manager Team ~


 --
 Regards,
 Chamila Adhikarinayake
 Associate Technical Lead
 WSO2, Inc.
 Mobile - +94712346437
 Email  - chami...@wso2.com
 Blog  -  http://helpfromadhi.blogspot.com/

>>>
>>>
>>>
>>> --

Re: [Architecture] API-M and sticky session

[Tharindu Dharmarathna]

Hi Nicolas,

The sticky session in API MAnager is needed to manage the following aspects.

1. In all UI components, it needs to manage to keep session affinity for
keep session with the same instance
2. For all Admin Service Calls which use to validate tokens, Create APIS,
etc between nodes. it uses a session for not to re-authenticate with
servers.
3. In Gateway Component it does not need to have session affinity for the
services you expose as rest API whereas you do not use any session related
data.

Thanks




On Fri, Sep 14, 2018 at 3:45 PM Nicolas Maujean <
nicolas.maujean.fra...@gmail.com> wrote:

> hi,
>
>I woud like to understand why nginx plus is needed to manage wso2 api
> in active-active whereas we could install the sticky module of nginx ?
>
> 
> http://gravitronic.com/compiling-the-nginx-sticky-session-module-in-ubuntu/
>
>If my service or stateless, the sticky session is needed
>
> best regards,
>
> Nicolas Maujean
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>


-- 

*Tharindu Dharmarathna*Associate Technical Lead
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: *+94779109091*
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] API-M and sticky session

[Nicolas Maujean]

Hi Tharindu,

   Thank you for your feedback.

Some More questions :
- Why don’t use the sticky module of nginx which is free but nginx plus ?
- why validate tokens ? With share folder, tokens is not shared ?
- I don’t understand for UI components, can you provide me an example ?

Best regards,

Nicolas Maujean



Le dim. 16 sept. 2018 à 10:53, Tharindu Dharmarathna  a
écrit :

> Hi Nicolas,
>
> The sticky session in API MAnager is needed to manage the
> following aspects.
>
> 1. In all UI components, it needs to manage to keep session affinity for
> keep session with the same instance
> 2. For all Admin Service Calls which use to validate tokens, Create APIS,
> etc between nodes. it uses a session for not to re-authenticate with
> servers.
> 3. In Gateway Component it does not need to have session affinity for the
> services you expose as rest API whereas you do not use any session related
> data.
>
> Thanks
>
>
>
>
> On Fri, Sep 14, 2018 at 3:45 PM Nicolas Maujean <
> nicolas.maujean.fra...@gmail.com> wrote:
>
>> hi,
>>
>>I woud like to understand why nginx plus is needed to manage wso2 api
>> in active-active whereas we could install the sticky module of nginx ?
>>
>> 
>>
>> http://gravitronic.com/compiling-the-nginx-sticky-session-module-in-ubuntu/
>>
>>If my service or stateless, the sticky session is needed
>>
>> best regards,
>>
>> Nicolas Maujean
>>
> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
>>
>
> --
>
> *Tharindu Dharmarathna*Associate Technical Lead
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94779109091*
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] Adding information (credentials) in the url calling the backend for WSO2-APIM

[Nicolas Maujean]

Hi,

   Is it possible to add information automatically in the url calling  the
back end, givng enough information, the credentials allowing to the backend
to make further test for security purpose ?

best regards,

Nicolas Maujean
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Dev] Dev][VOTE] Release of WSO2 API Manager 2.6.0 RC3

[Vithursa Mahendrarajah]

Hi all,

I have tested following and no issues found:

   - Basic API flow - API creation, publishing and invocation
   - Create user with different roles
   - API documentation
   - Password recovery in API Store
   - User sign-up workflow
   - Add application with custom attributes
   - Block subscription to an API
   - Invoke API using SOAP client

[+] Stable - Go ahead and release

Thanks,
Vithursa

On Sun, Sep 16, 2018 at 2:11 PM Tharindu Dharmarathna 
wrote:

> Hi All,
>
> tested the following  in distributed setup
> - Advance Throttling Policies
> - Blocking Conditions
> - Custom Rules
>
> [+] Stable - go ahead and release
>
> On Sun, Sep 16, 2018 at 9:58 AM Naduni Pamudika  wrote:
>
>> Hi All,
>>
>> Tested the following with PostgreSql 9.5.
>>
>> - Basic API creation and invocation
>> - Analytics
>> - Web socket API creation, invocation and analytics
>> - Secure vault
>> - Dynamic endpoints
>> - Secured endpoints
>> - Publisher Rest APIs
>>
>> Tested Microgateway with Labels, without Labels, and overriding endpoints
>>
>> [+] Stable - go ahead and release
>>
>> Thanks,
>> Naduni
>>
>> On Sat, Sep 15, 2018 at 9:09 PM, Chaminda Jayawardena 
>> wrote:
>>
>>> Hi All,
>>>
>>> According to the latest TestGrid-integration test job which performed
>>> with wso2am-2.6.0-rc3 release, has no single failure reported.
>>> Generated results can be found here[1] and accordingly we are happy to
>>> vote for the release of wso2am-2.6.0.
>>>
>>> [+] Stable - go ahead and release
>>>
>>> [1] [Test Grid] WSO2 APIM Integration Test Results #(121)
>>>
>>> Thanks,
>>> Chaminda
>>>
>>> On Sat, Sep 15, 2018 at 5:33 PM Chamila Adhikarinayake <
>>> chami...@wso2.com> wrote:
>>>
 Tested
 -  Alerts generation using different user groups (creator, subscriber)
 for super tenant and tenant domain
 -  Email generation for the alerts for super tenant and tenant domain
 users

 No blockers found.
 [+] Stable - go ahead and release


 On Sat, Sep 15, 2018 at 4:55 PM, Rajith Roshan 
 wrote:

> Tested following scenarios.
>
> Basic API creation , publish and invoke flow
> Creating api using swagger
> Build a micro gw by using api created by swagger and invoke the
> resources
> Customize the life cycle to add new state and check the lifecycle
> transitions
> Tested the basic scope validation
> Tested the cross tenant subscription flow
> Tested cross tenant subscriptions with scope validation
>
> No blockers found.
> [+] Stable - go ahead and release
>
> Thanks!
> Rajith
>
> On Sat, Sep 15, 2018 at 4:27 PM Sanjeewa Malalgoda 
> wrote:
>
>> Tested microgateway flows,
>>
>> Microgateway docker/VM mode with APIM 2.5
>> Microgateway  API pull using name and label to create gateway.
>>
>> Microgateway docker/VM mode with APIM 2.6
>>
>> +1.
>>
>> Thanks,
>> sanjeewa.
>>
>>
>> On Sat, Sep 15, 2018 at 3:34 PM Nuwan Dias  wrote:
>>
>>> Tested the following.
>>>
>>> Basic API creation by creator role
>>> Publishing by publisher role
>>> User sign up
>>> Creation and invocation of SOAP APIs
>>> Microgateway VM mode
>>> Microgateway docker mode
>>>
>>> [+] Stable - go ahead and release
>>>
>>> Thanks,
>>> NuwanD.
>>>
>>> On Sat, Sep 15, 2018 at 10:34 AM Chamila Adhikarinayake <
>>> chami...@wso2.com> wrote:
>>>
 Microgateway RC3 can be found in
 https://github.com/wso2/product-microgateway/releases/tag/v2.6.0-rc3


 Thanks
 Chamila

 On Sat, Sep 15, 2018 at 7:04 AM, Chamila Adhikarinayake <
 chami...@wso2.com> wrote:

> Hi All,
>
> We are pleased to announce the third release candidate of WSO2
> API Manager 2.6.0.
>
> This release fixes the following issues.
>
> Fixes : carbon-apimgt
> 
> Fixes : product-apim
> 
> Fixes : analytics-apim
> 
> Fixes : product-microgateway
> 
>
> Source and Distribution,
>- Runtime :
> https://github.com/wso2/product-apim/releases/tag/v2.6.0-rc3
>- Analytics :
> https://github.com/wso2/analytics-apim/releases/tag/v2.6.0-rc3
>- Tooling :
> https://github.com/wso2/devstudio-tooling-apim/releases

Re: [Architecture] [Dev] Dev][VOTE] Release of WSO2 API Manager 2.6.0 RC3

[Dinusha Dissanayake]

Hi all,

Tested below.

1. Basic user creation API creation, subscription and invocation.
2. Microgateway with API labels
3. Throttling (subscription, application and advanced)
4. APIM gateway and microgateway with analytics.

No blockers found.

[+] Stable - Go ahead and release

Thanks,
DinushaD


On Sun, Sep 16, 2018 at 5:59 PM Vithursa Mahendrarajah 
wrote:

> Hi all,
>
> I have tested following and no issues found:
>
>- Basic API flow - API creation, publishing and invocation
>- Create user with different roles
>- API documentation
>- Password recovery in API Store
>- User sign-up workflow
>- Add application with custom attributes
>- Block subscription to an API
>- Invoke API using SOAP client
>
> [+] Stable - Go ahead and release
>
> Thanks,
> Vithursa
>
> On Sun, Sep 16, 2018 at 2:11 PM Tharindu Dharmarathna 
> wrote:
>
>> Hi All,
>>
>> tested the following  in distributed setup
>> - Advance Throttling Policies
>> - Blocking Conditions
>> - Custom Rules
>>
>> [+] Stable - go ahead and release
>>
>> On Sun, Sep 16, 2018 at 9:58 AM Naduni Pamudika  wrote:
>>
>>> Hi All,
>>>
>>> Tested the following with PostgreSql 9.5.
>>>
>>> - Basic API creation and invocation
>>> - Analytics
>>> - Web socket API creation, invocation and analytics
>>> - Secure vault
>>> - Dynamic endpoints
>>> - Secured endpoints
>>> - Publisher Rest APIs
>>>
>>> Tested Microgateway with Labels, without Labels, and overriding endpoints
>>>
>>> [+] Stable - go ahead and release
>>>
>>> Thanks,
>>> Naduni
>>>
>>> On Sat, Sep 15, 2018 at 9:09 PM, Chaminda Jayawardena >> > wrote:
>>>
 Hi All,

 According to the latest TestGrid-integration test job which performed
 with wso2am-2.6.0-rc3 release, has no single failure reported.
 Generated results can be found here[1] and accordingly we are happy to
 vote for the release of wso2am-2.6.0.

 [+] Stable - go ahead and release

 [1] [Test Grid] WSO2 APIM Integration Test Results #(121)

 Thanks,
 Chaminda

 On Sat, Sep 15, 2018 at 5:33 PM Chamila Adhikarinayake <
 chami...@wso2.com> wrote:

> Tested
> -  Alerts generation using different user groups (creator, subscriber)
> for super tenant and tenant domain
> -  Email generation for the alerts for super tenant and tenant domain
> users
>
> No blockers found.
> [+] Stable - go ahead and release
>
>
> On Sat, Sep 15, 2018 at 4:55 PM, Rajith Roshan 
> wrote:
>
>> Tested following scenarios.
>>
>> Basic API creation , publish and invoke flow
>> Creating api using swagger
>> Build a micro gw by using api created by swagger and invoke the
>> resources
>> Customize the life cycle to add new state and check the lifecycle
>> transitions
>> Tested the basic scope validation
>> Tested the cross tenant subscription flow
>> Tested cross tenant subscriptions with scope validation
>>
>> No blockers found.
>> [+] Stable - go ahead and release
>>
>> Thanks!
>> Rajith
>>
>> On Sat, Sep 15, 2018 at 4:27 PM Sanjeewa Malalgoda 
>> wrote:
>>
>>> Tested microgateway flows,
>>>
>>> Microgateway docker/VM mode with APIM 2.5
>>> Microgateway  API pull using name and label to create gateway.
>>>
>>> Microgateway docker/VM mode with APIM 2.6
>>>
>>> +1.
>>>
>>> Thanks,
>>> sanjeewa.
>>>
>>>
>>> On Sat, Sep 15, 2018 at 3:34 PM Nuwan Dias  wrote:
>>>
 Tested the following.

 Basic API creation by creator role
 Publishing by publisher role
 User sign up
 Creation and invocation of SOAP APIs
 Microgateway VM mode
 Microgateway docker mode

 [+] Stable - go ahead and release

 Thanks,
 NuwanD.

 On Sat, Sep 15, 2018 at 10:34 AM Chamila Adhikarinayake <
 chami...@wso2.com> wrote:

> Microgateway RC3 can be found in
> https://github.com/wso2/product-microgateway/releases/tag/v2.6.0-rc3
>
>
> Thanks
> Chamila
>
> On Sat, Sep 15, 2018 at 7:04 AM, Chamila Adhikarinayake <
> chami...@wso2.com> wrote:
>
>> Hi All,
>>
>> We are pleased to announce the third release candidate of
>> WSO2 API Manager 2.6.0.
>>
>> This release fixes the following issues.
>>
>> Fixes : carbon-apimgt
>> 
>> Fixes : product-apim
>> 
>> Fixes : analytics-apim
>> 

Re: [Architecture] [Dev] Dev][VOTE] Release of WSO2 API Manager 2.6.0 RC3

[Krishan Wijesena]

Hi All,

Tested following scenarios.

   - Workflows - Super-tenant/Tenant flow

API Subscription Workflow
Application Creation Workflow
Configure Workflow for tenants

   - Subscription blocking/ unblocking
   - Tested With IE 11 browser.

   Basic API flow
   Add/ update Microgateway labels.

[+] Stable - Go ahead and release

Thanks,
Krishan

On Sun, Sep 16, 2018 at 8:37 PM, Dinusha Dissanayake 
wrote:

> Hi all,
>
> Tested below.
>
> 1. Basic user creation API creation, subscription and invocation.
> 2. Microgateway with API labels
> 3. Throttling (subscription, application and advanced)
> 4. APIM gateway and microgateway with analytics.
>
> No blockers found.
>
> [+] Stable - Go ahead and release
>
> Thanks,
> DinushaD
>
>
> On Sun, Sep 16, 2018 at 5:59 PM Vithursa Mahendrarajah 
> wrote:
>
>> Hi all,
>>
>> I have tested following and no issues found:
>>
>>- Basic API flow - API creation, publishing and invocation
>>- Create user with different roles
>>- API documentation
>>- Password recovery in API Store
>>- User sign-up workflow
>>- Add application with custom attributes
>>- Block subscription to an API
>>- Invoke API using SOAP client
>>
>> [+] Stable - Go ahead and release
>>
>> Thanks,
>> Vithursa
>>
>> On Sun, Sep 16, 2018 at 2:11 PM Tharindu Dharmarathna 
>> wrote:
>>
>>> Hi All,
>>>
>>> tested the following  in distributed setup
>>> - Advance Throttling Policies
>>> - Blocking Conditions
>>> - Custom Rules
>>>
>>> [+] Stable - go ahead and release
>>>
>>> On Sun, Sep 16, 2018 at 9:58 AM Naduni Pamudika  wrote:
>>>
 Hi All,

 Tested the following with PostgreSql 9.5.

 - Basic API creation and invocation
 - Analytics
 - Web socket API creation, invocation and analytics
 - Secure vault
 - Dynamic endpoints
 - Secured endpoints
 - Publisher Rest APIs

 Tested Microgateway with Labels, without Labels, and overriding
 endpoints

 [+] Stable - go ahead and release

 Thanks,
 Naduni

 On Sat, Sep 15, 2018 at 9:09 PM, Chaminda Jayawardena <
 chami...@wso2.com> wrote:

> Hi All,
>
> According to the latest TestGrid-integration test job which performed
> with wso2am-2.6.0-rc3 release, has no single failure reported.
> Generated results can be found here[1] and accordingly we are happy to
> vote for the release of wso2am-2.6.0.
>
> [+] Stable - go ahead and release
>
> [1] [Test Grid] WSO2 APIM Integration Test Results #(121)
>
> Thanks,
> Chaminda
>
> On Sat, Sep 15, 2018 at 5:33 PM Chamila Adhikarinayake <
> chami...@wso2.com> wrote:
>
>> Tested
>> -  Alerts generation using different user groups (creator,
>> subscriber) for super tenant and tenant domain
>> -  Email generation for the alerts for super tenant and tenant
>> domain users
>>
>> No blockers found.
>> [+] Stable - go ahead and release
>>
>>
>> On Sat, Sep 15, 2018 at 4:55 PM, Rajith Roshan 
>> wrote:
>>
>>> Tested following scenarios.
>>>
>>> Basic API creation , publish and invoke flow
>>> Creating api using swagger
>>> Build a micro gw by using api created by swagger and invoke the
>>> resources
>>> Customize the life cycle to add new state and check the lifecycle
>>> transitions
>>> Tested the basic scope validation
>>> Tested the cross tenant subscription flow
>>> Tested cross tenant subscriptions with scope validation
>>>
>>> No blockers found.
>>> [+] Stable - go ahead and release
>>>
>>> Thanks!
>>> Rajith
>>>
>>> On Sat, Sep 15, 2018 at 4:27 PM Sanjeewa Malalgoda <
>>> sanje...@wso2.com> wrote:
>>>
 Tested microgateway flows,

 Microgateway docker/VM mode with APIM 2.5
 Microgateway  API pull using name and label to create gateway.

 Microgateway docker/VM mode with APIM 2.6

 +1.

 Thanks,
 sanjeewa.


 On Sat, Sep 15, 2018 at 3:34 PM Nuwan Dias  wrote:

> Tested the following.
>
> Basic API creation by creator role
> Publishing by publisher role
> User sign up
> Creation and invocation of SOAP APIs
> Microgateway VM mode
> Microgateway docker mode
>
> [+] Stable - go ahead and release
>
> Thanks,
> NuwanD.
>
> On Sat, Sep 15, 2018 at 10:34 AM Chamila Adhikarinayake <
> chami...@wso2.com> wrote:
>
>> Microgateway RC3 can be found in https://github.com/wso2/
>> product-microgateway/releases/tag/v2.6.0-rc3
>>
>> Thanks
>> Chamila
>>
>> On Sat, Sep 15, 2018 at 7:04 AM, Chamila Adhikarinayake <
>> chami...@wso2.com> wrote:
>>
>>> Hi

Re: [Architecture] Adding information (credentials) in the url calling the backend for WSO2-APIM

[Fazlan Nazeem]

Hi Nicolas,

I assume your question is regarding API Manager product. You can append
query params to the backend URL by adding a mediation flow to the API in
the inSequence.

http://ws.apache.org/ns/synapse"; name="sample">
>  expression="fn:concat(get-property('axis2','REST_URL_POSTFIX'),
> '&name=xyz')" scope="axis2" type="STRING"/>
> 


The above mediation sequence will append a query param named "name" which
has a value of "xyz" to the backend call.

The steps to include a custom insequence to your API can be found here[1]

[1] https://docs.wso2.com/display/AM210/Adding+Mediation+Extensions



On Sun, Sep 16, 2018 at 5:48 AM Nicolas Maujean <
nicolas.maujean.fra...@gmail.com> wrote:

> Hi,
>
>Is it possible to add information automatically in the url calling  the
> back end, givng enough information, the credentials allowing to the backend
> to make further test for security purpose ?
>
> best regards,
>
> Nicolas Maujean
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>


-- 
Thanks & Regards,

*Fazlan Nazeem*
Senior Software Engineer
WSO2 Inc
Mobile : +94772338839
fazl...@wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Dev] Dev][VOTE] Release of WSO2 API Manager 2.6.0 RC3

[Fazlan Nazeem]

Hi,

I have tested the below scenarios.


   - Adding a secondary userstore
   - Adding a user to the secondary userstore
   - Adding a role to the secondary userstore

Using the *secondary user* created tested the following operations

   - Basic API Creation in Publisher
   - Application creation
   - Subscribing to an API
   - Generating  tokens
   - Invoking
   - Scope registration and token generation with a scope.

No issues found.

[+] Stable - Go ahead and release

On Sun, Sep 16, 2018 at 10:25 AM Krishan Wijesena  wrote:

> Hi All,
>
> Tested following scenarios.
>
>- Workflows - Super-tenant/Tenant flow
>
> API Subscription Workflow
> Application Creation Workflow
> Configure Workflow for tenants
>
>- Subscription blocking/ unblocking
>- Tested With IE 11 browser.
>
>Basic API flow
>Add/ update Microgateway labels.
>
> [+] Stable - Go ahead and release
>
> Thanks,
> Krishan
>
> On Sun, Sep 16, 2018 at 8:37 PM, Dinusha Dissanayake 
> wrote:
>
>> Hi all,
>>
>> Tested below.
>>
>> 1. Basic user creation API creation, subscription and invocation.
>> 2. Microgateway with API labels
>> 3. Throttling (subscription, application and advanced)
>> 4. APIM gateway and microgateway with analytics.
>>
>> No blockers found.
>>
>> [+] Stable - Go ahead and release
>>
>> Thanks,
>> DinushaD
>>
>>
>> On Sun, Sep 16, 2018 at 5:59 PM Vithursa Mahendrarajah 
>> wrote:
>>
>>> Hi all,
>>>
>>> I have tested following and no issues found:
>>>
>>>- Basic API flow - API creation, publishing and invocation
>>>- Create user with different roles
>>>- API documentation
>>>- Password recovery in API Store
>>>- User sign-up workflow
>>>- Add application with custom attributes
>>>- Block subscription to an API
>>>- Invoke API using SOAP client
>>>
>>> [+] Stable - Go ahead and release
>>>
>>> Thanks,
>>> Vithursa
>>>
>>> On Sun, Sep 16, 2018 at 2:11 PM Tharindu Dharmarathna <
>>> tharin...@wso2.com> wrote:
>>>
 Hi All,

 tested the following  in distributed setup
 - Advance Throttling Policies
 - Blocking Conditions
 - Custom Rules

 [+] Stable - go ahead and release

 On Sun, Sep 16, 2018 at 9:58 AM Naduni Pamudika 
 wrote:

> Hi All,
>
> Tested the following with PostgreSql 9.5.
>
> - Basic API creation and invocation
> - Analytics
> - Web socket API creation, invocation and analytics
> - Secure vault
> - Dynamic endpoints
> - Secured endpoints
> - Publisher Rest APIs
>
> Tested Microgateway with Labels, without Labels, and overriding
> endpoints
>
> [+] Stable - go ahead and release
>
> Thanks,
> Naduni
>
> On Sat, Sep 15, 2018 at 9:09 PM, Chaminda Jayawardena <
> chami...@wso2.com> wrote:
>
>> Hi All,
>>
>> According to the latest TestGrid-integration test job which performed
>> with wso2am-2.6.0-rc3 release, has no single failure reported.
>> Generated results can be found here[1] and accordingly we are happy
>> to vote for the release of wso2am-2.6.0.
>>
>> [+] Stable - go ahead and release
>>
>> [1] [Test Grid] WSO2 APIM Integration Test Results #(121)
>>
>> Thanks,
>> Chaminda
>>
>> On Sat, Sep 15, 2018 at 5:33 PM Chamila Adhikarinayake <
>> chami...@wso2.com> wrote:
>>
>>> Tested
>>> -  Alerts generation using different user groups (creator,
>>> subscriber) for super tenant and tenant domain
>>> -  Email generation for the alerts for super tenant and tenant
>>> domain users
>>>
>>> No blockers found.
>>> [+] Stable - go ahead and release
>>>
>>>
>>> On Sat, Sep 15, 2018 at 4:55 PM, Rajith Roshan 
>>> wrote:
>>>
 Tested following scenarios.

 Basic API creation , publish and invoke flow
 Creating api using swagger
 Build a micro gw by using api created by swagger and invoke the
 resources
 Customize the life cycle to add new state and check the lifecycle
 transitions
 Tested the basic scope validation
 Tested the cross tenant subscription flow
 Tested cross tenant subscriptions with scope validation

 No blockers found.
 [+] Stable - go ahead and release

 Thanks!
 Rajith

 On Sat, Sep 15, 2018 at 4:27 PM Sanjeewa Malalgoda <
 sanje...@wso2.com> wrote:

> Tested microgateway flows,
>
> Microgateway docker/VM mode with APIM 2.5
> Microgateway  API pull using name and label to create gateway.
>
> Microgateway docker/VM mode with APIM 2.6
>
> +1.
>
> Thanks,
> sanjeewa.
>
>
> On Sat, Sep 15, 2018 at 3:34 PM Nuwan Dias 
> wrote:
>
>> Tested the following.
>>

Re: [Architecture] Adding information (credentials) in the url calling the backend for WSO2-APIM

[Nicolas Maujean]

hi Fazlan,

   Thank you for your feedback. Yes, WSO2 API-Manager, can we add the
credentials associated to the token in oauth2 ?

best regards,

Nicolas Maujean

Le dim. 16 sept. 2018 à 18:32, Fazlan Nazeem  a écrit :

> Hi Nicolas,
>
> I assume your question is regarding API Manager product. You can append
> query params to the backend URL by adding a mediation flow to the API in
> the inSequence.
>
> http://ws.apache.org/ns/synapse"; name="sample">
>> > expression="fn:concat(get-property('axis2','REST_URL_POSTFIX'),
>> '&name=xyz')" scope="axis2" type="STRING"/>
>> 
>
>
> The above mediation sequence will append a query param named "name" which
> has a value of "xyz" to the backend call.
>
> The steps to include a custom insequence to your API can be found here[1]
>
> [1] https://docs.wso2.com/display/AM210/Adding+Mediation+Extensions
>
>
>
> On Sun, Sep 16, 2018 at 5:48 AM Nicolas Maujean <
> nicolas.maujean.fra...@gmail.com> wrote:
>
>> Hi,
>>
>>Is it possible to add information automatically in the url calling
>> the back end, givng enough information, the credentials allowing to the
>> backend to make further test for security purpose ?
>>
>> best regards,
>>
>> Nicolas Maujean
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>
>
> --
> Thanks & Regards,
>
> *Fazlan Nazeem*
> Senior Software Engineer
> WSO2 Inc
> Mobile : +94772338839
> fazl...@wso2.com
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Adding information (credentials) in the url calling the backend for WSO2-APIM

[Fazlan Nazeem]

Hi Nicolas,

Your question is not very clear to me. Can you explain a bit in detail?

On Sun, Sep 16, 2018 at 11:19 AM Nicolas Maujean <
nicolas.maujean.fra...@gmail.com> wrote:

> hi Fazlan,
>
>Thank you for your feedback. Yes, WSO2 API-Manager, can we add the
> credentials associated to the token in oauth2 ?
>
> best regards,
>
> Nicolas Maujean
>
> Le dim. 16 sept. 2018 à 18:32, Fazlan Nazeem  a écrit :
>
>> Hi Nicolas,
>>
>> I assume your question is regarding API Manager product. You can append
>> query params to the backend URL by adding a mediation flow to the API in
>> the inSequence.
>>
>> http://ws.apache.org/ns/synapse"; name="sample">
>>> >> expression="fn:concat(get-property('axis2','REST_URL_POSTFIX'),
>>> '&name=xyz')" scope="axis2" type="STRING"/>
>>> 
>>
>>
>> The above mediation sequence will append a query param named "name" which
>> has a value of "xyz" to the backend call.
>>
>> The steps to include a custom insequence to your API can be found here[1]
>>
>> [1] https://docs.wso2.com/display/AM210/Adding+Mediation+Extensions
>>
>>
>>
>> On Sun, Sep 16, 2018 at 5:48 AM Nicolas Maujean <
>> nicolas.maujean.fra...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>>Is it possible to add information automatically in the url calling
>>> the back end, givng enough information, the credentials allowing to the
>>> backend to make further test for security purpose ?
>>>
>>> best regards,
>>>
>>> Nicolas Maujean
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>
>>
>> --
>> Thanks & Regards,
>>
>> *Fazlan Nazeem*
>> Senior Software Engineer
>> WSO2 Inc
>> Mobile : +94772338839
>> fazl...@wso2.com
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>


-- 
Thanks & Regards,

*Fazlan Nazeem*
Senior Software Engineer
WSO2 Inc
Mobile : +94772338839
fazl...@wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Adding information (credentials) in the url calling the backend for WSO2-APIM

[Nicolas Maujean]

hi Fazlan,

   Sure, when we use service on WSO2 API-M, we use WSO2-IS to manage token.
We would like to secure webservice and make sure only people allowed to see
the informations can do it, so we would like to provide when making a
query, the credentials of the person associated to the token, so we can
make the verification on the back end side, is it possible to provide those
informations using WSO2 API-M ?

best regards,

Nicolas Maujean


Le dim. 16 sept. 2018 à 19:35, Fazlan Nazeem  a écrit :

> Hi Nicolas,
>
> Your question is not very clear to me. Can you explain a bit in detail?
>
> On Sun, Sep 16, 2018 at 11:19 AM Nicolas Maujean <
> nicolas.maujean.fra...@gmail.com> wrote:
>
>> hi Fazlan,
>>
>>Thank you for your feedback. Yes, WSO2 API-Manager, can we add the
>> credentials associated to the token in oauth2 ?
>>
>> best regards,
>>
>> Nicolas Maujean
>>
>> Le dim. 16 sept. 2018 à 18:32, Fazlan Nazeem  a écrit :
>>
>>> Hi Nicolas,
>>>
>>> I assume your question is regarding API Manager product. You can append
>>> query params to the backend URL by adding a mediation flow to the API in
>>> the inSequence.
>>>
>>> http://ws.apache.org/ns/synapse"; name="sample">
 >>> expression="fn:concat(get-property('axis2','REST_URL_POSTFIX'),
 '&name=xyz')" scope="axis2" type="STRING"/>
 
>>>
>>>
>>> The above mediation sequence will append a query param named "name"
>>> which has a value of "xyz" to the backend call.
>>>
>>> The steps to include a custom insequence to your API can be found here[1]
>>>
>>> [1] https://docs.wso2.com/display/AM210/Adding+Mediation+Extensions
>>>
>>>
>>>
>>> On Sun, Sep 16, 2018 at 5:48 AM Nicolas Maujean <
>>> nicolas.maujean.fra...@gmail.com> wrote:
>>>
 Hi,

Is it possible to add information automatically in the url calling
 the back end, givng enough information, the credentials allowing to the
 backend to make further test for security purpose ?

 best regards,

 Nicolas Maujean
 ___
 Architecture mailing list
 Architecture@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

>>>
>>>
>>> --
>>> Thanks & Regards,
>>>
>>> *Fazlan Nazeem*
>>> Senior Software Engineer
>>> WSO2 Inc
>>> Mobile : +94772338839
>>> fazl...@wso2.com
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>
>
> --
> Thanks & Regards,
>
> *Fazlan Nazeem*
> Senior Software Engineer
> WSO2 Inc
> Mobile : +94772338839
> fazl...@wso2.com
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [APIM][300][Store] Feature to change password of an user

[Isura Karunaratne]

On Thu, Sep 6, 2018 at 5:31 PM Vithursa Mahendrarajah 
wrote:

> Hi Dulanja,
>
> Please find my answers in-line:
>
> On Thu, Sep 6, 2018 at 10:45 AM Dulanja Liyanage  wrote:
>
>> Hi Vithursa,
>>
>> Few questions:
>>
>> 1. What happens when the user enters a wrong username? As a security best
>> practice, the returned message must not indicate that the username is
>> invalid. Because, a rogue user can determine valid usernames of the system
>> by using this feature (i.e. username harvesting). Therefore, for both valid
>> and invalid usernames, system should show a message similar to "A password
>> reset email has been sent to the registered email address".
>>
>
> As per current implementation, it returns message to indicate that the
> user name is invalid. I am agreeing with the point you mentioned, but on
> the other hand, it will not give a proper guide in situation like when user
> mistakenly enters their user name wrong.  I checked this feature in other
> accounts as well which indicate whether the user name is valid or not.
>
>>
>> 2. How are you storing the confirmation codes against the user? Is it as
>> a claim of the user or in the registry?
>>
>
> I hoped to store it as a claim of user (admin has access to confirmation
> code).
>
IMO this is not correct. Then the users who can view the user profiles of
others, can view the confirmation codes? Then they can change the passwords
of those users using those confirmation codes.



> 3. What is the validity of the confirmation code and how you plan to
>> cleanup the expired/used codes?
>>
>
> We can define it to be a day and store generated time along with the
> code.  Regarding the cleanup of used codes, once the user clicks on the
> link, gets verified and resets password. we can remove the confirmation
> code after successful reset. It won't be valid thereafter.
> Regarding the cleanup of expired codes,we do not need to remove expired
> codes as there will be one code per user, validating expiry of confirmation
> code would be enough. If it is necessary, we can do it by weekly scheduled
> task.
>
 Better to have a scheduled task, otheriwse the table will be grown if
users won't click on the email link.

>
> Also, to verify the confirmation code, we can have two options as:
>
>1. Send redirect link in mail (we have this in previous version)
>2. Send confirmation code (which user should enter to continue
>password reset, like in Facebook)
>
> Which one would be more feasible to have. Provide your thoughts.
>
In API wise there is no much difference between both options. We better to
support both options.


> Thanks,
> Vithursa
>

Thanks
Isura.

>
>> Thanks,
>> Dulanja
>>
>>
>> On Wed, Sep 5, 2018 at 11:02 PM, Vithursa Mahendrarajah <
>> vithu...@wso2.com> wrote:
>>
>>> [Update]
>>>
>>> Hi all,
>>>
>>> I have implemented UI changes to accommodate password reset feature.
>>> Forgot password option in login page [Img-1], requesting user name for
>>> validating the user [Img-2], redirection page [Img-3] and page to reset
>>> password [Img-4].
>>> In back end, I have implemented a MSF4J endpoint to validate the entered
>>> user name. Currently, I am implementing REST APIs in carbon-auth to
>>> generate random code (Using secureRandom [1]) and to send notifications
>>> with link to reset password.
>>>
>>> [1]
>>> https://docs.oracle.com/javase/7/docs/api/java/security/SecureRandom.html
>>>
>>> Thanks,
>>>
>>> On Thu, Aug 23, 2018 at 10:10 AM Ishara Cooray  wrote:
>>>
 +1 to make password-rest as the base path if we are not going to have
 any other apis other than password reset.

 since clicking on the url in the e-mail is something that is confirming
 the password reset action I would suggest to change the endpoint as 
 *confirm
 *than notify

 /initiate
> /confirm   -  endpoint gets called when user clicks on the link,
> validates the confirmation key
> /
>

 Hope we can use the same password-reset api for change password request
 as well.


 Thanks & Regards,
 Ishara Cooray
 Senior Software Engineer
 Mobile : +9477 262 9512
 WSO2, Inc. | http://wso2.com/
 Lean . Enterprise . Middleware

 On Tue, Aug 21, 2018 at 5:43 PM, Sanjeewa Malalgoda 
 wrote:

>
>
> On Tue, Aug 21, 2018 at 5:31 PM Vithursa Mahendrarajah <
> vithu...@wso2.com> wrote:
>
>> Hi all,
>>
>> As per suggestions, I will work on reset password feature. Proposed
>> flow of implementation for this feature is as follows:
>>
>> [image: first_reset.png]  [image:
>> second_reset.png]
>>
>> We need following APIs to handle reset password request:
>> /password-reset-initiate  - generates a confirmation key
>> /password-reset-notify   -  endpoint gets called when user clicks on
>> the link, validates the confirmation key
>> /password-reset - end point to reset password, ultimatel

Re: [Architecture] Adding information (credentials) in the url calling the backend for WSO2-APIM

[Fazlan Nazeem]

Hi Nicolas,

Yes. Usually, the use case you described is achieved via a JWT token which
has data related to the user who invoked the API in API Manager. This
will not include the user password, but the username will be included.

On the backend web service, you can decode the JWT and do any validations
you want. Please check [1] for more information.

[1]
https://docs.wso2.com/display/AM170/Passing+Enduser+Attributes+to+the+Backend+Using+JWT


On Sun, Sep 16, 2018 at 11:41 AM Nicolas Maujean <
nicolas.maujean.fra...@gmail.com> wrote:

> hi Fazlan,
>
>Sure, when we use service on WSO2 API-M, we use WSO2-IS to manage
> token. We would like to secure webservice and make sure only people allowed
> to see the informations can do it, so we would like to provide when making
> a query, the credentials of the person associated to the token, so we can
> make the verification on the back end side, is it possible to provide those
> informations using WSO2 API-M ?
>
> best regards,
>
> Nicolas Maujean
>
>
> Le dim. 16 sept. 2018 à 19:35, Fazlan Nazeem  a écrit :
>
>> Hi Nicolas,
>>
>> Your question is not very clear to me. Can you explain a bit in detail?
>>
>> On Sun, Sep 16, 2018 at 11:19 AM Nicolas Maujean <
>> nicolas.maujean.fra...@gmail.com> wrote:
>>
>>> hi Fazlan,
>>>
>>>Thank you for your feedback. Yes, WSO2 API-Manager, can we add the
>>> credentials associated to the token in oauth2 ?
>>>
>>> best regards,
>>>
>>> Nicolas Maujean
>>>
>>> Le dim. 16 sept. 2018 à 18:32, Fazlan Nazeem  a
>>> écrit :
>>>
 Hi Nicolas,

 I assume your question is regarding API Manager product. You can append
 query params to the backend URL by adding a mediation flow to the API in
 the inSequence.

 http://ws.apache.org/ns/synapse"; name="sample">
>  expression="fn:concat(get-property('axis2','REST_URL_POSTFIX'),
> '&name=xyz')" scope="axis2" type="STRING"/>
> 


 The above mediation sequence will append a query param named "name"
 which has a value of "xyz" to the backend call.

 The steps to include a custom insequence to your API can be found
 here[1]

 [1] https://docs.wso2.com/display/AM210/Adding+Mediation+Extensions



 On Sun, Sep 16, 2018 at 5:48 AM Nicolas Maujean <
 nicolas.maujean.fra...@gmail.com> wrote:

> Hi,
>
>Is it possible to add information automatically in the url calling
> the back end, givng enough information, the credentials allowing to the
> backend to make further test for security purpose ?
>
> best regards,
>
> Nicolas Maujean
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>


 --
 Thanks & Regards,

 *Fazlan Nazeem*
 Senior Software Engineer
 WSO2 Inc
 Mobile : +94772338839
 fazl...@wso2.com
 ___
 Architecture mailing list
 Architecture@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>
>>
>> --
>> Thanks & Regards,
>>
>> *Fazlan Nazeem*
>> Senior Software Engineer
>> WSO2 Inc
>> Mobile : +94772338839
>> fazl...@wso2.com
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>


-- 
Thanks & Regards,

*Fazlan Nazeem*
Senior Software Engineer
WSO2 Inc
Mobile : +94772338839
fazl...@wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Adding information (credentials) in the url calling the backend for WSO2-APIM

[Nicolas Maujean]

Thank you

Le dim. 16 sept. 2018 à 19:54, Fazlan Nazeem  a écrit :

> Hi Nicolas,
>
> Yes. Usually, the use case you described is achieved via a JWT token which
> has data related to the user who invoked the API in API Manager. This
> will not include the user password, but the username will be included.
>
> On the backend web service, you can decode the JWT and do any validations
> you want. Please check [1] for more information.
>
> [1]
> https://docs.wso2.com/display/AM170/Passing+Enduser+Attributes+to+the+Backend+Using+JWT
>
>
> On Sun, Sep 16, 2018 at 11:41 AM Nicolas Maujean <
> nicolas.maujean.fra...@gmail.com> wrote:
>
>> hi Fazlan,
>>
>>Sure, when we use service on WSO2 API-M, we use WSO2-IS to manage
>> token. We would like to secure webservice and make sure only people allowed
>> to see the informations can do it, so we would like to provide when making
>> a query, the credentials of the person associated to the token, so we can
>> make the verification on the back end side, is it possible to provide those
>> informations using WSO2 API-M ?
>>
>> best regards,
>>
>> Nicolas Maujean
>>
>>
>> Le dim. 16 sept. 2018 à 19:35, Fazlan Nazeem  a écrit :
>>
>>> Hi Nicolas,
>>>
>>> Your question is not very clear to me. Can you explain a bit in detail?
>>>
>>> On Sun, Sep 16, 2018 at 11:19 AM Nicolas Maujean <
>>> nicolas.maujean.fra...@gmail.com> wrote:
>>>
 hi Fazlan,

Thank you for your feedback. Yes, WSO2 API-Manager, can we add the
 credentials associated to the token in oauth2 ?

 best regards,

 Nicolas Maujean

 Le dim. 16 sept. 2018 à 18:32, Fazlan Nazeem  a
 écrit :

> Hi Nicolas,
>
> I assume your question is regarding API Manager product. You can
> append query params to the backend URL by adding a mediation flow to the
> API in the inSequence.
>
> http://ws.apache.org/ns/synapse"; name="sample">
>> > expression="fn:concat(get-property('axis2','REST_URL_POSTFIX'),
>> '&name=xyz')" scope="axis2" type="STRING"/>
>> 
>
>
> The above mediation sequence will append a query param named "name"
> which has a value of "xyz" to the backend call.
>
> The steps to include a custom insequence to your API can be found
> here[1]
>
> [1] https://docs.wso2.com/display/AM210/Adding+Mediation+Extensions
>
>
>
> On Sun, Sep 16, 2018 at 5:48 AM Nicolas Maujean <
> nicolas.maujean.fra...@gmail.com> wrote:
>
>> Hi,
>>
>>Is it possible to add information automatically in the url
>> calling  the back end, givng enough information, the credentials allowing
>> to the backend to make further test for security purpose ?
>>
>> best regards,
>>
>> Nicolas Maujean
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>
>
> --
> Thanks & Regards,
>
> *Fazlan Nazeem*
> Senior Software Engineer
> WSO2 Inc
> Mobile : +94772338839
> fazl...@wso2.com
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
 ___
 Architecture mailing list
 Architecture@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

>>>
>>>
>>> --
>>> Thanks & Regards,
>>>
>>> *Fazlan Nazeem*
>>> Senior Software Engineer
>>> WSO2 Inc
>>> Mobile : +94772338839
>>> fazl...@wso2.com
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>
>
> --
> Thanks & Regards,
>
> *Fazlan Nazeem*
> Senior Software Engineer
> WSO2 Inc
> Mobile : +94772338839
> fazl...@wso2.com
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Dev] Dev][VOTE] Release of WSO2 API Manager 2.6.0 RC3

[Dushani Wellappili]

Hi,

I have tested the below scenarios with MSSQL 2017 for both tenant and super
tenant


   - Basic API Creation, Application creation, subscribing, generating
   tokens, invoking, store sign up
   - Application properties
   - API properties
   - SP Init SSO and IDP Init SSO with wso2is-km-5.7.0 RC3
   - Publisher access control
   - Application Sharing with Multiple Groups using defaultgrouping
   extractor
   - Forgot password, account locking, password policies

No blockers found.

[+] Stable - Go ahead and release




*Dushani Wellappili*
Software Engineer - WSO2

Email : dusha...@wso2.com
Mobile : +94779367571
Web : https://wso2.com/




On Sun, Sep 16, 2018 at 10:22 PM Fazlan Nazeem  wrote:

> Hi,
>
> I have tested the below scenarios.
>
>
>- Adding a secondary userstore
>- Adding a user to the secondary userstore
>- Adding a role to the secondary userstore
>
> Using the *secondary user* created tested the following operations
>
>- Basic API Creation in Publisher
>- Application creation
>- Subscribing to an API
>- Generating  tokens
>- Invoking
>- Scope registration and token generation with a scope.
>
> No issues found.
>
> [+] Stable - Go ahead and release
>
> On Sun, Sep 16, 2018 at 10:25 AM Krishan Wijesena 
> wrote:
>
>> Hi All,
>>
>> Tested following scenarios.
>>
>>- Workflows - Super-tenant/Tenant flow
>>
>> API Subscription Workflow
>> Application Creation Workflow
>> Configure Workflow for tenants
>>
>>- Subscription blocking/ unblocking
>>- Tested With IE 11 browser.
>>
>>Basic API flow
>>Add/ update Microgateway labels.
>>
>> [+] Stable - Go ahead and release
>>
>> Thanks,
>> Krishan
>>
>> On Sun, Sep 16, 2018 at 8:37 PM, Dinusha Dissanayake 
>> wrote:
>>
>>> Hi all,
>>>
>>> Tested below.
>>>
>>> 1. Basic user creation API creation, subscription and invocation.
>>> 2. Microgateway with API labels
>>> 3. Throttling (subscription, application and advanced)
>>> 4. APIM gateway and microgateway with analytics.
>>>
>>> No blockers found.
>>>
>>> [+] Stable - Go ahead and release
>>>
>>> Thanks,
>>> DinushaD
>>>
>>>
>>> On Sun, Sep 16, 2018 at 5:59 PM Vithursa Mahendrarajah <
>>> vithu...@wso2.com> wrote:
>>>
 Hi all,

 I have tested following and no issues found:

- Basic API flow - API creation, publishing and invocation
- Create user with different roles
- API documentation
- Password recovery in API Store
- User sign-up workflow
- Add application with custom attributes
- Block subscription to an API
- Invoke API using SOAP client

 [+] Stable - Go ahead and release

 Thanks,
 Vithursa

 On Sun, Sep 16, 2018 at 2:11 PM Tharindu Dharmarathna <
 tharin...@wso2.com> wrote:

> Hi All,
>
> tested the following  in distributed setup
> - Advance Throttling Policies
> - Blocking Conditions
> - Custom Rules
>
> [+] Stable - go ahead and release
>
> On Sun, Sep 16, 2018 at 9:58 AM Naduni Pamudika 
> wrote:
>
>> Hi All,
>>
>> Tested the following with PostgreSql 9.5.
>>
>> - Basic API creation and invocation
>> - Analytics
>> - Web socket API creation, invocation and analytics
>> - Secure vault
>> - Dynamic endpoints
>> - Secured endpoints
>> - Publisher Rest APIs
>>
>> Tested Microgateway with Labels, without Labels, and overriding
>> endpoints
>>
>> [+] Stable - go ahead and release
>>
>> Thanks,
>> Naduni
>>
>> On Sat, Sep 15, 2018 at 9:09 PM, Chaminda Jayawardena <
>> chami...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> According to the latest TestGrid-integration test job which
>>> performed with wso2am-2.6.0-rc3 release, has no single failure reported.
>>> Generated results can be found here[1] and accordingly we are happy
>>> to vote for the release of wso2am-2.6.0.
>>>
>>> [+] Stable - go ahead and release
>>>
>>> [1] [Test Grid] WSO2 APIM Integration Test Results #(121)
>>>
>>> Thanks,
>>> Chaminda
>>>
>>> On Sat, Sep 15, 2018 at 5:33 PM Chamila Adhikarinayake <
>>> chami...@wso2.com> wrote:
>>>
 Tested
 -  Alerts generation using different user groups (creator,
 subscriber) for super tenant and tenant domain
 -  Email generation for the alerts for super tenant and tenant
 domain users

 No blockers found.
 [+] Stable - go ahead and release


 On Sat, Sep 15, 2018 at 4:55 PM, Rajith Roshan 
 wrote:

> Tested following scenarios.
>
> Basic API creation , publish and invoke flow
> Creating api using swagger
> Build a micro gw by using api created by swagger and invoke the
> resources
> Customize the life cycle to add

Re: [Architecture] [VOTE] Release of WSO2 Stream Processor 4.3.0 RC3

[Sajith Perera]

Tested the following.

Siddhi Stores Query API[editor/worker runtime]
Distributed Message Tracer[worker/dashboard runtime]
SP Distributed Deployment[2 Manger/ 5 Worker(including single receiver)
runtimes]
Editor Sample:
 - Store RDBMS MySQL/Oracle[editor]
 - Store Cassedra[editor]

No blockers found.

[+] Stable - go ahead and release

Thanks,
SajithD

On Sat, Sep 15, 2018 at 1:05 AM, Dilini Muthumala  wrote:

> Hi all,
>
>
> WSO2 Stream Processor team is pleased to announce the third
> release candidate of WSO2 Stream Processor 4.3.0.
>
>
> WSO2 Stream Processor is an open source embodiment of the WSO2 Analytics
> platform, of which the real-time, incremental & intelligent data processing
> capabilities let digital businesses create actionable business insights and
> data products.
>
>
> Please find the improvements and fixes related to this release:
>
> - siddhi
> 
>
> - carbon-analytics-common
> 
>
> - carbon-analytics
> 
>
> - carbon-dashboards
> 
>
> - analytics-solutions
> 
>
> - product-sp
> 
>
>
> You can download the product distribution from: https://github.com/wso2/
> product-sp/releases/download/v4.3.0-rc3/wso2sp-4.3.0-rc3.zip
>
>
> The tag to be voted upon: 
> *https://github.com/wso2/product-sp/releases/tag/v4.3.0-rc3
> *
>
>
> Please download, test the product and vote.
>
>
> [+] Stable - go ahead and release
>
> [-] Broken - do not release (explain why)
>
>
> Thanks,
>
> - WSO2 Stream Processor Team -
>



-- 

Sajith Dimal
Seniror Software Engineer
Email : saji...@wso2.com
Mobile : +94783101496
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware


Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
re-transmit, disseminate, or otherwise use the information contained in
this communication. Internet communications cannot be guaranteed to be
timely, secure, error or virus-free. The sender does not accept liability
for any errors or omissions.
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Dev] [VOTE] Release of WSO2 Stream Processor 4.3.0 RC3

[Niveathika Rajendran]

Hi all,

I have tested the following,
   1. Local IdPClient
   2. Login/Logout Rest API
   3. Authentication Interceptor
   4. HTTP Analytics Solution [worker/dashboard]
   5. Monitoring dashboard for a single node [Node view/App view]
   6. Editor sample:
  - MongoDB
  - Aggregate Data Incrementally

[+] Stable go ahead and release

Best Regards,
*Niveathika Rajendran,*
*Software Engineer.*
*Mobile : +94 077 903 7536*





On Mon, Sep 17, 2018 at 1:55 AM Sajith Perera  wrote:

> Tested the following.
>
> Siddhi Stores Query API[editor/worker runtime]
> Distributed Message Tracer[worker/dashboard runtime]
> SP Distributed Deployment[2 Manger/ 5 Worker(including single receiver)
> runtimes]
> Editor Sample:
>  - Store RDBMS MySQL/Oracle[editor]
>  - Store Cassedra[editor]
>
> No blockers found.
>
> [+] Stable - go ahead and release
>
> Thanks,
> SajithD
>
> On Sat, Sep 15, 2018 at 1:05 AM, Dilini Muthumala  wrote:
>
>> Hi all,
>>
>>
>> WSO2 Stream Processor team is pleased to announce the third
>> release candidate of WSO2 Stream Processor 4.3.0.
>>
>>
>> WSO2 Stream Processor is an open source embodiment of the WSO2 Analytics
>> platform, of which the real-time, incremental & intelligent data processing
>> capabilities let digital businesses create actionable business insights and
>> data products.
>>
>>
>> Please find the improvements and fixes related to this release:
>>
>> - siddhi
>> 
>>
>> - carbon-analytics-common
>> 
>>
>> - carbon-analytics
>> 
>>
>> - carbon-dashboards
>> 
>>
>> - analytics-solutions
>> 
>>
>> - product-sp
>> 
>>
>>
>> You can download the product distribution from:
>> https://github.com/wso2/product-sp/releases/download/v4.3.0-rc3/wso2sp-4.3.0-rc3.zip
>>
>>
>> The tag to be voted upon: 
>> *https://github.com/wso2/product-sp/releases/tag/v4.3.0-rc3
>> *
>>
>>
>> Please download, test the product and vote.
>>
>>
>> [+] Stable - go ahead and release
>>
>> [-] Broken - do not release (explain why)
>>
>>
>> Thanks,
>>
>> - WSO2 Stream Processor Team -
>>
>
>
>
> --
> 
> Sajith Dimal
> Seniror Software Engineer
> Email : saji...@wso2.com
> Mobile : +94783101496
> WSO2 Inc. | http://wso2.com
> lean.enterprise.middleware
>
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, re-transmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
> ___
> Dev mailing list
> d...@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Dev] [VOTE] Release of WSO2 Stream Processor 4.3.0 RC3

[Tanya Madurapperuma]

Hi All,

I have tested following.

   1. Basic dashboard functionalities
  - Create dashboard
  - Drag and drop widgets
  - Create Pages in dashboard
  - Hide Pages
   2. Dashboard import / export feature
   3. Dashboard and widget report generation feature

No issues found.

[+] Stable go ahead and release

Thanks,
Tanya

On Mon, Sep 17, 2018 at 7:56 AM, Niveathika Rajendran 
wrote:

> Hi all,
>
> I have tested the following,
>1. Local IdPClient
>2. Login/Logout Rest API
>3. Authentication Interceptor
>4. HTTP Analytics Solution [worker/dashboard]
>5. Monitoring dashboard for a single node [Node view/App view]
>6. Editor sample:
>   - MongoDB
>   - Aggregate Data Incrementally
>
> [+] Stable go ahead and release
>
> Best Regards,
> *Niveathika Rajendran,*
> *Software Engineer.*
> *Mobile : +94 077 903 7536*
>
>
>
>
>
> On Mon, Sep 17, 2018 at 1:55 AM Sajith Perera  wrote:
>
>> Tested the following.
>>
>> Siddhi Stores Query API[editor/worker runtime]
>> Distributed Message Tracer[worker/dashboard runtime]
>> SP Distributed Deployment[2 Manger/ 5 Worker(including single receiver)
>> runtimes]
>> Editor Sample:
>>  - Store RDBMS MySQL/Oracle[editor]
>>  - Store Cassedra[editor]
>>
>> No blockers found.
>>
>> [+] Stable - go ahead and release
>>
>> Thanks,
>> SajithD
>>
>> On Sat, Sep 15, 2018 at 1:05 AM, Dilini Muthumala 
>> wrote:
>>
>>> Hi all,
>>>
>>>
>>> WSO2 Stream Processor team is pleased to announce the third
>>> release candidate of WSO2 Stream Processor 4.3.0.
>>>
>>>
>>> WSO2 Stream Processor is an open source embodiment of the WSO2 Analytics
>>> platform, of which the real-time, incremental & intelligent data processing
>>> capabilities let digital businesses create actionable business insights and
>>> data products.
>>>
>>>
>>> Please find the improvements and fixes related to this release:
>>>
>>> - siddhi
>>> 
>>>
>>> - carbon-analytics-common
>>> 
>>>
>>> - carbon-analytics
>>> 
>>>
>>> - carbon-dashboards
>>> 
>>>
>>> - analytics-solutions
>>> 
>>>
>>> - product-sp
>>> 
>>>
>>>
>>> You can download the product distribution from: https://github.com/wso2/
>>> product-sp/releases/download/v4.3.0-rc3/wso2sp-4.3.0-rc3.zip
>>>
>>>
>>> The tag to be voted upon: 
>>> *https://github.com/wso2/product-sp/releases/tag/v4.3.0-rc3
>>> *
>>>
>>>
>>> Please download, test the product and vote.
>>>
>>>
>>> [+] Stable - go ahead and release
>>>
>>> [-] Broken - do not release (explain why)
>>>
>>>
>>> Thanks,
>>>
>>> - WSO2 Stream Processor Team -
>>>
>>
>>
>>
>> --
>> 
>> Sajith Dimal
>> Seniror Software Engineer
>> Email : saji...@wso2.com
>> Mobile : +94783101496
>> WSO2 Inc. | http://wso2.com
>> lean.enterprise.middleware
>>
>>
>> Disclaimer: This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s.
>> If you are not the intended recipient/s, or believe that you may have
>> received this communication in error, please reply to the sender indicating
>> that fact and delete the copy you received and in addition, you should not
>> print, copy, re-transmit, disseminate, or otherwise use the information
>> contained in this communication. Internet communications cannot be
>> guaranteed to be timely, secure, error or virus-free. The sender does not
>> accept liability for any errors or omissions.
>> ___
>> Dev mailing list
>> d...@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
*Tanya Madurapperuma* | Associate Technical Lead| WSO2 Inc.
(m) +94718184439 | (e) ta...@wso2.com


___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

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

[Dilin Dampahalage]

Hi all,

I have tested IS 5.7.0-RC3 with IS Analytics 5.7.0 Beta and it works fine.

No issues were found.

 [+] Stable - go ahead and release

Thanks,
Dilin


On Sun, Sep 16, 2018 at 9:09 AM Abilashini Thiyagarajah 
wrote:

> Hi all,
>
> I have tested the following scenarios,
>
> - Role-based adaptive authentication
> - User-age-based adaptive authentication
> - Tenant-based adaptive authentication
> - New-device-based adaptive authentication
> - ACR-based adaptive authentication
> - Self-registration and account confirmation with & without consent
> purposes
> - Account recovery
>
> - username
> - password - using mail notification and challenge question
>
> - Creating users using the ask password option
>
> No issues were found.
>
>  [+] Stable - go ahead and release
>
> Thanks,
> Abilashini
>
>
> On Sat, Sep 15, 2018 at 3:27 PM Sarubi Thillainathan 
> wrote:
>
>> Hi All,
>>
>> I have tested the following on both LDAP and JDBC user stores and no
>> issues were found.
>>
>> * Multi-attribute filter search with and without pagination
>> * All the available SCIM2 endpoints which are given in doc [1]
>>
>> [+] Stable - go ahead and release.
>>
>> [1] https://docs.wso2.com/display/IS570/apidocs/SCIM2-endpoints/
>>
>> On Sat, Sep 15, 2018 at 2:24 AM Mathuriga Thavarajah 
>> wrote:
>>
>>> Hi All,
>>>
>>> I have tested the following and no issues were found.
>>>
>>> * Settip up MySQL 5.7
>>> * Configuring a Read-write Active Directory User Store as a
>>> secondary user store
>>> * Configuring Multi-factor Authentication (Basic and Google as a
>>> federated authenticator)
>>> * Configuring LDAP Active Directory as a primary store in WSO2
>>> Identity Server 5.7.0 RC3 on windows instance.
>>>
>>> [+] Stable - go ahead and release.
>>>
>>> Regards,
>>> Mathuriga.
>>>
>>>
>>> On Fri, Sep 14, 2018 at 5:23 PM Thanuja Jayasinghe 
>>> wrote:
>>>
 Hi All,

 I have tested the following and no issues were found.

- User account association
- Workflow management
- Adaptive authentication
- Role-based
   - User age based

 [+] Stable - go ahead and release

 Thanks,
 Thanuja
 ___
 Dev mailing list
 d...@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev

>>>
>>>
>>> --
>>>
>>> *Mathuriga Thavarajah*
>>> Software Engineer
>>> WSO2 Inc. - http ://wso2.com
>>>
>>> Email : mathur...@wso2.com
>>> Mobile  : +94778191300
>>>
>>>
>>>
>>> *[image: http://wso2.com/signature] *
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>
>>
>> --
>> *Sarubi Thillainathan *
>> *Software Engineer - WSO2 Inc.*
>>
>> *Mobile : +94 (0) 76 68 49 101*
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>
>
> --
> Abilashini Thiyagarajah
> Software Engineer
> WSO2, Inc.
> Mobile: +94 778983001
> 
> ___
> Dev mailing list
> d...@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 

*Dilin Dampahalage*
Software Engineer | WSO2

Email : di...@wso2.com
Mobile : +94 771 462939
web : http://wso2.com


___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

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

[Thanuja Jayasinghe]

Hi All,

Thanks for testing WSO2 Identity Server 5.7.0-RC3.

Since this vote passed with 28 +1s and 0 -1s, we’re hereby closing this
vote and proceeding with the Identity Server 5.7.0 GA release.

Thanks,
Thanuja

On Mon, Sep 17, 2018 at 10:01 AM Dilin Dampahalage  wrote:

> Hi all,
>
> I have tested IS 5.7.0-RC3 with IS Analytics 5.7.0 Beta and it works fine.
>
> No issues were found.
>
>  [+] Stable - go ahead and release
>
> Thanks,
> Dilin
>
>
> On Sun, Sep 16, 2018 at 9:09 AM Abilashini Thiyagarajah <
> abilash...@wso2.com> wrote:
>
>> Hi all,
>>
>> I have tested the following scenarios,
>>
>> - Role-based adaptive authentication
>> - User-age-based adaptive authentication
>> - Tenant-based adaptive authentication
>> - New-device-based adaptive authentication
>> - ACR-based adaptive authentication
>> - Self-registration and account confirmation with & without consent
>> purposes
>> - Account recovery
>>
>> - username
>> - password - using mail notification and challenge question
>>
>> - Creating users using the ask password option
>>
>> No issues were found.
>>
>>  [+] Stable - go ahead and release
>>
>> Thanks,
>> Abilashini
>>
>>
>> On Sat, Sep 15, 2018 at 3:27 PM Sarubi Thillainathan 
>> wrote:
>>
>>> Hi All,
>>>
>>> I have tested the following on both LDAP and JDBC user stores and no
>>> issues were found.
>>>
>>> * Multi-attribute filter search with and without pagination
>>> * All the available SCIM2 endpoints which are given in doc [1]
>>>
>>> [+] Stable - go ahead and release.
>>>
>>> [1] https://docs.wso2.com/display/IS570/apidocs/SCIM2-endpoints/
>>>
>>> On Sat, Sep 15, 2018 at 2:24 AM Mathuriga Thavarajah 
>>> wrote:
>>>
 Hi All,

 I have tested the following and no issues were found.

 * Settip up MySQL 5.7
 * Configuring a Read-write Active Directory User Store as a
 secondary user store
 * Configuring Multi-factor Authentication (Basic and Google as
 a federated authenticator)
 * Configuring LDAP Active Directory as a primary store in WSO2
 Identity Server 5.7.0 RC3 on windows instance.

 [+] Stable - go ahead and release.

 Regards,
 Mathuriga.


 On Fri, Sep 14, 2018 at 5:23 PM Thanuja Jayasinghe 
 wrote:

> Hi All,
>
> I have tested the following and no issues were found.
>
>- User account association
>- Workflow management
>- Adaptive authentication
>- Role-based
>   - User age based
>
> [+] Stable - go ahead and release
>
> Thanks,
> Thanuja
> ___
> Dev mailing list
> d...@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


 --

 *Mathuriga Thavarajah*
 Software Engineer
 WSO2 Inc. - http ://wso2.com

 Email : mathur...@wso2.com
 Mobile  : +94778191300



 *[image: http://wso2.com/signature] *
 ___
 Architecture mailing list
 Architecture@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

>>>
>>>
>>> --
>>> *Sarubi Thillainathan *
>>> *Software Engineer - WSO2 Inc.*
>>>
>>> *Mobile : +94 (0) 76 68 49 101*
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>
>>
>> --
>> Abilashini Thiyagarajah
>> Software Engineer
>> WSO2, Inc.
>> Mobile: +94 778983001
>> 
>> ___
>> Dev mailing list
>> d...@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
> --
>
> *Dilin Dampahalage*
> Software Engineer | WSO2
>
> Email : di...@wso2.com
> Mobile : +94 771 462939
> web : http://wso2.com
>
> 
> ___
> Dev mailing list
> d...@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
*Thanuja Lakmal*
Associate Technical Lead
WSO2 Inc. http://wso2.com/
*lean.enterprise.middleware*
Mobile: +94715979891
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Dev] [VOTE] Release of WSO2 Stream Processor 4.3.0 RC3

[Anusha Jayasundara]

Hi All,

I have tested followings,

   1. Minimum HA scenario
  - Setup 2 nodes
  - Change Passive to active
  - Data persistence between two nodes
  - Monitoring dashboard for the HA scenario
  2. Editor Samples
  - Redis Sample
  - IBMMQSample
  - RDBMS Sample
   3. Business Rules
  - Create business rule from scratch and template
  - Delete business rules
  - Edit business rules
  - Add deployed APIM siddhi app details to the business rule table

No issue Found

[+] Stable go ahead and release


Thanks,


On Mon, Sep 17, 2018 at 9:50 AM Tanya Madurapperuma  wrote:

> Hi All,
>
> I have tested following.
>
>1. Basic dashboard functionalities
>   - Create dashboard
>   - Drag and drop widgets
>   - Create Pages in dashboard
>   - Hide Pages
>2. Dashboard import / export feature
>3. Dashboard and widget report generation feature
>
> No issues found.
>
> [+] Stable go ahead and release
>
> Thanks,
> Tanya
>
> On Mon, Sep 17, 2018 at 7:56 AM, Niveathika Rajendran  > wrote:
>
>> Hi all,
>>
>> I have tested the following,
>>1. Local IdPClient
>>2. Login/Logout Rest API
>>3. Authentication Interceptor
>>4. HTTP Analytics Solution [worker/dashboard]
>>5. Monitoring dashboard for a single node [Node view/App view]
>>6. Editor sample:
>>   - MongoDB
>>   - Aggregate Data Incrementally
>>
>> [+] Stable go ahead and release
>>
>> Best Regards,
>> *Niveathika Rajendran,*
>> *Software Engineer.*
>> *Mobile : +94 077 903 7536*
>>
>>
>>
>>
>>
>> On Mon, Sep 17, 2018 at 1:55 AM Sajith Perera  wrote:
>>
>>> Tested the following.
>>>
>>> Siddhi Stores Query API[editor/worker runtime]
>>> Distributed Message Tracer[worker/dashboard runtime]
>>> SP Distributed Deployment[2 Manger/ 5 Worker(including single receiver)
>>> runtimes]
>>> Editor Sample:
>>>  - Store RDBMS MySQL/Oracle[editor]
>>>  - Store Cassedra[editor]
>>>
>>> No blockers found.
>>>
>>> [+] Stable - go ahead and release
>>>
>>> Thanks,
>>> SajithD
>>>
>>> On Sat, Sep 15, 2018 at 1:05 AM, Dilini Muthumala 
>>> wrote:
>>>
 Hi all,


 WSO2 Stream Processor team is pleased to announce the third
 release candidate of WSO2 Stream Processor 4.3.0.


 WSO2 Stream Processor is an open source embodiment of the WSO2
 Analytics platform, of which the real-time, incremental & intelligent
 data processing capabilities let digital businesses create actionable
 business insights and data products.


 Please find the improvements and fixes related to this release:

 - siddhi
 

 - carbon-analytics-common
 

 - carbon-analytics
 

 - carbon-dashboards
 

 - analytics-solutions
 

 - product-sp
 


 You can download the product distribution from:
 https://github.com/wso2/product-sp/releases/download/v4.3.0-rc3/wso2sp-4.3.0-rc3.zip


 The tag to be voted upon: 
 *https://github.com/wso2/product-sp/releases/tag/v4.3.0-rc3
 *


 Please download, test the product and vote.


 [+] Stable - go ahead and release

 [-] Broken - do not release (explain why)


 Thanks,

 - WSO2 Stream Processor Team -

>>>
>>>
>>>
>>> --
>>> 
>>> Sajith Dimal
>>> Seniror Software Engineer
>>> Email : saji...@wso2.com
>>> Mobile : +94783101496
>>> WSO2 Inc. | http://wso2.com
>>> lean.enterprise.middleware
>>>
>>>
>>> Disclaimer: This communication may contain privileged or other
>>> confidential information and is intended exclusively for the addressee/s.
>>> If you are not the intended recipient/s, or believe that you may have
>>> received this communication in error, please reply to the sender indicating
>>> that fact and delete the copy you received and in addition, you should not
>>> print, copy, re-transmit, disseminate, or otherwise use the information
>>> contained in this communication. Internet communications cannot be
>>> guaranteed to be timely, secure, error or virus-free. The sender does not
>>> accept liability for any errors or omissions.
>>> ___
>>> Dev mailing list
>>> d...@wso2.org
>>> 

Re: [Architecture] [Dev] [VOTE] Release of WSO2 Stream Processor 4.3.0 RC3

[Eranga Liyanage]

Hi All,

I've smoke tested following on Windows 10 Chrome.

   - Editor
   - Business Rules
   - Status Dashboard
   - Dashboard Portal

No issues found.

[+] Stable - go ahead and release.

Best regards
Eranga.


On Mon, Sep 17, 2018 at 10:29 AM Anusha Jayasundara 
wrote:

> Hi All,
>
> I have tested followings,
>
>1. Minimum HA scenario
>   - Setup 2 nodes
>   - Change Passive to active
>   - Data persistence between two nodes
>   - Monitoring dashboard for the HA scenario
>   2. Editor Samples
>   - Redis Sample
>   - IBMMQSample
>   - RDBMS Sample
>3. Business Rules
>   - Create business rule from scratch and template
>   - Delete business rules
>   - Edit business rules
>   - Add deployed APIM siddhi app details to the business rule table
>
> No issue Found
>
> [+] Stable go ahead and release
>
>
> Thanks,
>
>
> On Mon, Sep 17, 2018 at 9:50 AM Tanya Madurapperuma 
> wrote:
>
>> Hi All,
>>
>> I have tested following.
>>
>>1. Basic dashboard functionalities
>>   - Create dashboard
>>   - Drag and drop widgets
>>   - Create Pages in dashboard
>>   - Hide Pages
>>2. Dashboard import / export feature
>>3. Dashboard and widget report generation feature
>>
>> No issues found.
>>
>> [+] Stable go ahead and release
>>
>> Thanks,
>> Tanya
>>
>> On Mon, Sep 17, 2018 at 7:56 AM, Niveathika Rajendran <
>> niveath...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> I have tested the following,
>>>1. Local IdPClient
>>>2. Login/Logout Rest API
>>>3. Authentication Interceptor
>>>4. HTTP Analytics Solution [worker/dashboard]
>>>5. Monitoring dashboard for a single node [Node view/App view]
>>>6. Editor sample:
>>>   - MongoDB
>>>   - Aggregate Data Incrementally
>>>
>>> [+] Stable go ahead and release
>>>
>>> Best Regards,
>>> *Niveathika Rajendran,*
>>> *Software Engineer.*
>>> *Mobile : +94 077 903 7536*
>>>
>>>
>>>
>>>
>>>
>>> On Mon, Sep 17, 2018 at 1:55 AM Sajith Perera  wrote:
>>>
 Tested the following.

 Siddhi Stores Query API[editor/worker runtime]
 Distributed Message Tracer[worker/dashboard runtime]
 SP Distributed Deployment[2 Manger/ 5 Worker(including single receiver)
 runtimes]
 Editor Sample:
  - Store RDBMS MySQL/Oracle[editor]
  - Store Cassedra[editor]

 No blockers found.

 [+] Stable - go ahead and release

 Thanks,
 SajithD

 On Sat, Sep 15, 2018 at 1:05 AM, Dilini Muthumala 
 wrote:

> Hi all,
>
>
> WSO2 Stream Processor team is pleased to announce the third
> release candidate of WSO2 Stream Processor 4.3.0.
>
>
> WSO2 Stream Processor is an open source embodiment of the WSO2
> Analytics platform, of which the real-time, incremental & intelligent
> data processing capabilities let digital businesses create actionable
> business insights and data products.
>
>
> Please find the improvements and fixes related to this release:
>
> - siddhi
> 
>
> - carbon-analytics-common
> 
>
> - carbon-analytics
> 
>
> - carbon-dashboards
> 
>
> - analytics-solutions
> 
>
> - product-sp
> 
>
>
> You can download the product distribution from:
> https://github.com/wso2/product-sp/releases/download/v4.3.0-rc3/wso2sp-4.3.0-rc3.zip
>
>
> The tag to be voted upon: 
> *https://github.com/wso2/product-sp/releases/tag/v4.3.0-rc3
> *
>
>
> Please download, test the product and vote.
>
>
> [+] Stable - go ahead and release
>
> [-] Broken - do not release (explain why)
>
>
> Thanks,
>
> - WSO2 Stream Processor Team -
>



 --
 
 Sajith Dimal
 Seniror Software Engineer
 Email : saji...@wso2.com
 Mobile : +94783101496
 WSO2 Inc. | http://wso2.com
 lean.enterprise.middleware


 Disclaimer: This communication may contain privileged or other
 confidential information and is intended exclusively for the addressee/s.
 If you are not the intended recipient/s, or believe that you may have
 received this communication in error, 

Re: [Architecture] [Dev] [VOTE] Release of WSO2 Stream Processor 4.3.0 RC3

[Chathuranga Siriwardhana]

Hi all,

I tested the following samples in the editor.

   -  AggregateDataIncrementally
   - AggregateOverTime
   - RDBMSSample
   - StreamingRegressor
   - SweetProductionDataPreprocessing
   - JoinWithStoredData

[+] Stable go ahead and release

Best regards,
Chathuranga Siriwardhana,
Software Engineering Intern.
Mobile: +94713604485


On Mon, Sep 17, 2018 at 11:00 AM Senuri De Silva  wrote:

> Hi all,
>
> I have tested the following.
>
> 1. Dashboard and widget report generation feature.
> 2. Editor samples
>
>- PMML Model Processor
>- Alerts and Thresholds
>- Pattern Matching
>- R Script Sample
>- Script Js Sample
>- Sentiment Sample
>- Streaming Hoeffding Classifier Sample
>- Streaming K Means Sample
>
> No issues found.
>
> [+] Stable go ahead and release
>
> Thanks,
> Senuri
>
> On Mon, Sep 17, 2018 at 10:29 AM, Anusha Jayasundara 
> wrote:
>
>> Hi All,
>>
>> I have tested followings,
>>
>>1. Minimum HA scenario
>>   - Setup 2 nodes
>>   - Change Passive to active
>>   - Data persistence between two nodes
>>   - Monitoring dashboard for the HA scenario
>>   2. Editor Samples
>>   - Redis Sample
>>   - IBMMQSample
>>   - RDBMS Sample
>>3. Business Rules
>>   - Create business rule from scratch and template
>>   - Delete business rules
>>   - Edit business rules
>>   - Add deployed APIM siddhi app details to the business rule table
>>
>> No issue Found
>>
>> [+] Stable go ahead and release
>>
>>
>> Thanks,
>>
>>
>> On Mon, Sep 17, 2018 at 9:50 AM Tanya Madurapperuma 
>> wrote:
>>
>>> Hi All,
>>>
>>> I have tested following.
>>>
>>>1. Basic dashboard functionalities
>>>   - Create dashboard
>>>   - Drag and drop widgets
>>>   - Create Pages in dashboard
>>>   - Hide Pages
>>>2. Dashboard import / export feature
>>>3. Dashboard and widget report generation feature
>>>
>>> No issues found.
>>>
>>> [+] Stable go ahead and release
>>>
>>> Thanks,
>>> Tanya
>>>
>>> On Mon, Sep 17, 2018 at 7:56 AM, Niveathika Rajendran <
>>> niveath...@wso2.com> wrote:
>>>
 Hi all,

 I have tested the following,
1. Local IdPClient
2. Login/Logout Rest API
3. Authentication Interceptor
4. HTTP Analytics Solution [worker/dashboard]
5. Monitoring dashboard for a single node [Node view/App view]
6. Editor sample:
   - MongoDB
   - Aggregate Data Incrementally

 [+] Stable go ahead and release

 Best Regards,
 *Niveathika Rajendran,*
 *Software Engineer.*
 *Mobile : +94 077 903 7536*





 On Mon, Sep 17, 2018 at 1:55 AM Sajith Perera  wrote:

> Tested the following.
>
> Siddhi Stores Query API[editor/worker runtime]
> Distributed Message Tracer[worker/dashboard runtime]
> SP Distributed Deployment[2 Manger/ 5 Worker(including single
> receiver) runtimes]
> Editor Sample:
>  - Store RDBMS MySQL/Oracle[editor]
>  - Store Cassedra[editor]
>
> No blockers found.
>
> [+] Stable - go ahead and release
>
> Thanks,
> SajithD
>
> On Sat, Sep 15, 2018 at 1:05 AM, Dilini Muthumala 
> wrote:
>
>> Hi all,
>>
>>
>> WSO2 Stream Processor team is pleased to announce the third
>> release candidate of WSO2 Stream Processor 4.3.0.
>>
>>
>> WSO2 Stream Processor is an open source embodiment of the WSO2
>> Analytics platform, of which the real-time, incremental & intelligent
>> data processing capabilities let digital businesses create actionable
>> business insights and data products.
>>
>>
>> Please find the improvements and fixes related to this release:
>>
>> - siddhi
>> 
>>
>> - carbon-analytics-common
>> 
>>
>> - carbon-analytics
>> 
>>
>> - carbon-dashboards
>> 
>>
>> - analytics-solutions
>> 
>>
>> - product-sp
>> 
>>
>>
>> You can download the product distribution from:
>> https://github.com/wso2/product-sp/releases/download/v4.3.0-rc3/wso2sp-4.3.0-rc3.zip
>>
>>
>> The tag to be voted upon: 
>> *https://github.com/wso2/product-sp/releases/tag/v4.3.0-rc3
>> 

Re: [Architecture] [Dev] [VOTE] Release of WSO2 Stream Processor 4.3.0 RC3

[Damith Wickramasinghe]

Hi all,

Tested following,

- HA scenarios
  - state syncing
  - ports open/close in active and passive nodes
  - active siddhi apps in active and passive nodes via management
apis

- Editor samples
  - DataPreprocessing
  - ExtractNamedEntities
  - StreamingPerceptron

- Editor open, save , delete , export , import , open sample functionalities

No issues found.

[+] Stable go ahead and release

Regards,
Damith.

On Mon, Sep 17, 2018 at 5:30 AM, Senuri De Silva  wrote:

> Hi all,
>
> I have tested the following.
>
> 1. Dashboard and widget report generation feature.
> 2. Editor samples
>
>- PMML Model Processor
>- Alerts and Thresholds
>- Pattern Matching
>- R Script Sample
>- Script Js Sample
>- Sentiment Sample
>- Streaming Hoeffding Classifier Sample
>- Streaming K Means Sample
>
> No issues found.
>
> [+] Stable go ahead and release
>
> Thanks,
> Senuri
>
> On Mon, Sep 17, 2018 at 10:29 AM, Anusha Jayasundara 
> wrote:
>
>> Hi All,
>>
>> I have tested followings,
>>
>>1. Minimum HA scenario
>>   - Setup 2 nodes
>>   - Change Passive to active
>>   - Data persistence between two nodes
>>   - Monitoring dashboard for the HA scenario
>>   2. Editor Samples
>>   - Redis Sample
>>   - IBMMQSample
>>   - RDBMS Sample
>>3. Business Rules
>>   - Create business rule from scratch and template
>>   - Delete business rules
>>   - Edit business rules
>>   - Add deployed APIM siddhi app details to the business rule table
>>
>> No issue Found
>>
>> [+] Stable go ahead and release
>>
>>
>> Thanks,
>>
>>
>> On Mon, Sep 17, 2018 at 9:50 AM Tanya Madurapperuma 
>> wrote:
>>
>>> Hi All,
>>>
>>> I have tested following.
>>>
>>>1. Basic dashboard functionalities
>>>   - Create dashboard
>>>   - Drag and drop widgets
>>>   - Create Pages in dashboard
>>>   - Hide Pages
>>>2. Dashboard import / export feature
>>>3. Dashboard and widget report generation feature
>>>
>>> No issues found.
>>>
>>> [+] Stable go ahead and release
>>>
>>> Thanks,
>>> Tanya
>>>
>>> On Mon, Sep 17, 2018 at 7:56 AM, Niveathika Rajendran <
>>> niveath...@wso2.com> wrote:
>>>
 Hi all,

 I have tested the following,
1. Local IdPClient
2. Login/Logout Rest API
3. Authentication Interceptor
4. HTTP Analytics Solution [worker/dashboard]
5. Monitoring dashboard for a single node [Node view/App view]
6. Editor sample:
   - MongoDB
   - Aggregate Data Incrementally

 [+] Stable go ahead and release

 Best Regards,
 *Niveathika Rajendran,*
 *Software Engineer.*
 *Mobile : +94 077 903 7536*





 On Mon, Sep 17, 2018 at 1:55 AM Sajith Perera  wrote:

> Tested the following.
>
> Siddhi Stores Query API[editor/worker runtime]
> Distributed Message Tracer[worker/dashboard runtime]
> SP Distributed Deployment[2 Manger/ 5 Worker(including single
> receiver) runtimes]
> Editor Sample:
>  - Store RDBMS MySQL/Oracle[editor]
>  - Store Cassedra[editor]
>
> No blockers found.
>
> [+] Stable - go ahead and release
>
> Thanks,
> SajithD
>
> On Sat, Sep 15, 2018 at 1:05 AM, Dilini Muthumala 
> wrote:
>
>> Hi all,
>>
>>
>> WSO2 Stream Processor team is pleased to announce the third
>> release candidate of WSO2 Stream Processor 4.3.0.
>>
>>
>> WSO2 Stream Processor is an open source embodiment of the WSO2
>> Analytics platform, of which the real-time, incremental & intelligent
>> data processing capabilities let digital businesses create actionable
>> business insights and data products.
>>
>>
>> Please find the improvements and fixes related to this release:
>>
>> - siddhi
>> 
>>
>> - carbon-analytics-common
>> 
>>
>> - carbon-analytics
>> 
>>
>> - carbon-dashboards
>> 
>>
>> - analytics-solutions
>> 
>>
>> - product-sp
>> 
>>
>>
>> You can download the product distribution from:
>> https://github.com/wso2/product-sp/releases/download/v
>> 4.3.0-rc3/wso2sp-4.3.0-rc3.zip
>>
>>
>> The tag to be voted upon:

Re: [Architecture] [Dev] Dev][VOTE] Release of WSO2 API Manager 2.6.0 RC3

[Ishara Cooray]

Tested the following.

Store REST API
External Stores
Store tag listing and tagwiseMode

[+] Stable - go ahead and release


Thanks & Regards,
Ishara Cooray
Senior Software Engineer
Mobile : +9477 262 9512
WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

>
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Dev] Dev][VOTE] Release of WSO2 API Manager 2.6.0 RC3

[Pubudu Gunatilaka]

Hi,

Tested the following scenarios.

- JWT generation in API Manager
- API Micorgateway generation using a Swagger Imported API
- API Microgateway API invocation with a JWT and without a subscription
(JWT validation only)
- API Microgateway run on VM/Docker

[+] Stable - go ahead and release.

Thank you!

On Mon, Sep 17, 2018 at 11:26 AM Ishara Cooray  wrote:

> Tested the following.
>
> Store REST API
> External Stores
> Store tag listing and tagwiseMode
>
> [+] Stable - go ahead and release
>
>
> Thanks & Regards,
> Ishara Cooray
> Senior Software Engineer
> Mobile : +9477 262 9512
> WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
>>
>> ___
> Dev mailing list
> d...@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Senior Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774078049 <%2B94772207163>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture