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

[Hasanthi Purnima Dissanayake]

Hi All,

I have tested following features.

   1. OIDC backchannel logout
   2. SAML front channel logout.

No blocking issues found.

[+] Stable - go ahead and release.

Thanks,
Hasanthi



On Wed, May 22, 2019 at 8:03 AM Isuranga Perera  wrote:

> All:
> I have tested Federated Authentication
> [+] Stable - go ahead and release.
>
> Best Regards
> Isuranga Perera
>
> On Sun, May 19, 2019 at 7:30 PM Shanika Wickramasinghe 
> wrote:
>
>> Hi All,
>>
>> I have tested the SAML SSO with POST binding and Redirect binding flows
>> and no issues found.
>>
>> +1 Go Ahead and Release
>>
>>
>> Thanks,
>>
>> Shanika
>>
>> On Thu, May 16, 2019 at 12:33 PM Hasanthi Purnima Dissanayake <
>> hasan...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> The reason of breaking the RC2 vote is because it is reported an unused
>>> commented configuration description in carbon.xml [1]. From RC3 release
>>> that commented line in the configuration file is removed and no other code
>>> level changes done.
>>>
>>> Further in the Analytics-IS pack, the versions are updated according to
>>> the latest released SP pack versions [2].
>>>
>>> [1] [Dev][VOTE] Release WSO2 Identity Server 5.8.0 RC2
>>> [2] [VOTE] Release of WSO2 Stream Processor 4.4.0 RC6
>>>
>>> Thanks,
>>> Hasanthi
>>>
>>> On Thu, May 16, 2019 at 12:30 PM Hasanthi Purnima Dissanayake <
>>> hasan...@wso2.com> wrote:
>>>
 Hi all,

 We are pleased to announce the third release candidate of WSO2 Identity
 Server 5.8.0.

 This release fixes the following issues,

- 5.8.0-RC3 fixes

- 5.8.0-RC2 fixes

- 5.8.0-RC1 fixes

- 5.8.0-Beta5 fixes

- 5.8.0-Beta4 fixes

- 5.8.0-Beta3 fixes

- 5.8.0-Beta fixes

- 5.8.0-Alpha5 fixes

- 5.8.0-Alpha4 fixes

- 5.8.0-Alpha3 fixes

- 5.8.0-Alpha2 fixes

- 5.8.0-Alpha fixes

- 5.8.0-M26 fixes

- 5.8.0-M25 fixes

- 5.8.0-M24 fixes

- 5.8.0-M6 fixes

- 5.8.0-M5 fixes

- 5.8.0-M4 fixes

- 5.8.0-M3 fixes

- 5.8.0-M2 fixes

- 5.8.0-M1 fixes



 Source and distribution

 Runtime - https://github.com/wso2/product-is/releases/tag/v
 
 5.8.0-rc3
 
 Analytics -
 https://github.com/wso2/analytics-is/releases/tag/v5.8.0-rc3
 


 Please download, test the product and vote.

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


 Thanks,
 - WSO2 Identity and Access Management Team -

 --

 Hasanthi Dissanayake

 Senior Software Engineer | WSO2

 E: hasan...@wso2.com
 M :0718407133| http://wso2.com 

>>>
>>>
>>> --
>>>
>>> Hasanthi Dissanayake
>>>
>>> Senior Software Engineer | WSO2
>>>
>>> E: hasan...@wso2.com
>>> M :0718407133| http://wso2.com 
>>>
>>
>>
>> --
>> *Shanika Wickramasinghe*
>> Software Engineer - QA Team
>>
>> Email: shani...@wso2.com
>> Mobile  : +94713503563
>> Web : http://wso2.com
>>
>> 
>>
>
>
> --
> *Isuranga Perera* | Software Engineer | WSO2 Inc.
>  +94 71 735 7034 | isura...@wso2.com 
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https:

Re: [Architecture] [Dev] [VOTE] Release WSO2 Enterprise Integrator 6.5.0 RC1

[Sajitha Liyanage]

Hi all,

I have tested the followings,

   - Manage endpoints in Management Console and Integration Studio
   - HTTP Inbound Protocol
   - HTTPS Inbound Protocol

+1 Stable - Go ahead and release.

Best Regards,
Sajitha

On Wed, May 22, 2019 at 6:11 AM Thishani Lucas  wrote:

> Hi all,
>
> Tested the following.
>
>- XACML authorization with entitlement mediator.
>- Smooks mediator.
>- Mediation debugging with Integration Studio.
>
> [+] Stable - Go ahead and release.
>
> Thanks.
>
> On Sun, May 19, 2019 at 2:07 AM Sameera Gunarathne 
> wrote:
>
>> Hi all,
>>
>> I tested the following cases.
>>
>>- Split aggregate pattern  with Iterate and Aggregate mediators
>>- Web socket transport
>>- BPMN process creation and task execution in BPS profile
>>- BPMN rest APIs
>>
>> +1 Stable, Go ahead and release.
>>
>> Thanks and Regards,
>> Sameera.
>>
>> On Sat, May 18, 2019 at 2:56 PM Nirothipan Megalingham <
>> nirothi...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> I've tested the following in Ubuntu 18.04 and found no blocker issues
>>> while testing.
>>>
>>>- Deploying sample composite applications in ESB server and Micro
>>>Integrator.
>>>- Listing the artifacts deployed in Micro Integrator via CLI.
>>>- Switch Mediator created in Integration Studio and Management
>>>Console.
>>>- Simple Scheduled Tasks.
>>>- ESB as JMS Producer and Consumer with WSO2 MB.
>>>
>>> +1 for the release.
>>>
>>> Thanks
>>> Nirothipan
>>>
>>>
>>> On Sat, May 18, 2019 at 10:56 AM Kesavan Yogarajah 
>>> wrote:
>>>
 Hi All,

 I tested the following, and no issues found.

- Salesforce Connector
- Salesforce custom inbound Endpoint
- Script mediator


 [+] Stable - go ahead and release

 Thanks
 Kesavan

 Kesavan Yogarajah
 Software Engineer
 Mobile :+94 (0) 779 758021
 kesav...@wso2.com
 WSO2, Inc.
 lean . enterprise . middleware


 On Fri, May 17, 2019 at 11:15 PM Mathuriga Thavarajah <
 mathur...@wso2.com> wrote:

> Hi All,
>
> Security Scanning reports (Static and Dynamic) were analyzed and
> reviewed. Hence +1 from the Platform Security Team for proceeding with the
> release.
>
> Thanks.
>
> Regards,
> Mathuriga.
>
> On Fri, May 17, 2019 at 7:06 PM Chanika Geeganage 
> wrote:
>
>> Hi All,
>>
>> I tested following scenarios ( artifacts were created using both
>> management console and integration studio).
>> 1. Call Template
>> 2. Adding a datasource
>> 3. Generating a dataservice form the datasource
>> 4. Creating a dataservice and uploading a dataservice
>> 5. Tested sample dataservices
>> 6. Odata
>>
>> [+] Stable - go ahead and release
>>
>> On Thu, May 16, 2019 at 7:33 PM Nirothipan Megalingham <
>> nirothi...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> We are pleased to announce the first release candidate of WSO2
>>> Enterprise Integrator 6.5.0.
>>>
>>> Please find the list of tasks / bug fixes and improvements shipped
>>> with this release below
>>>
>>>- Tasks/bug fixes and improvements in Enterprise Integrator
>>>
>>> 
>>>- Tasks/bug fixes and improvements in Micro Integrator
>>>
>>> 
>>>
>>> Known Issues
>>>
>>>- https://github.com/wso2/product-ei/issues
>>>- https://github.com/wso2/micro-integrator/issues
>>>
>>> The tag to be voted upon:
>>> https://github.com/wso2/product-ei/tree/v6.5.0-rc1
>>>
>>> Source and binary distributions:
>>> https://github.com/wso2/product-ei/releases/tag/v6.5.0-rc1
>>>
>>> Please test and vote as follows
>>>
>>> [+] Stable - go ahead and release
>>> [-] Broken - do not release (explain why)
>>>
>>> You may find the official documentation in:
>>> https://docs.wso2.com/display/EI6xx
>>>
>>> ~ The Enterprise Integrator Team ~
>>>
>>>
>>> --
>>>
>>> *M.Nirothipan* | Senior Software Engineer | WSO2 Inc.
>>>
>>> (m) +94772172692 | (e) nirothi...@wso2.com
>>>
>>> [image: http://wso2.com/signature] 
>>>
>>>
>>
>> --
>>
>> *Chanika Geeganage* | Associate Technical Lead | WSO2 Inc.
>>
>> (m) +94-77-3522586 | (e) chan...@wso2.com
>>
>> 
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>
>
> --
>
> *Mathuriga Thavarajah*
> Software Engineer
>>

Re: [Architecture] [Dev] [VOTE] Release WSO2 Enterprise Integrator 6.5.0 RC1

[Menuka Warushavithana]

Hi all,

I have tested the following and found no issues.

   - CXF WS-RM Inbound Protocol
   - WebSocket Inbound Protocol


+1 Stable - go ahead and release.


Thanks,
Menuka

On Wed, May 22, 2019 at 6:11 AM Thishani Lucas  wrote:

> Hi all,
>
> Tested the following.
>
>- XACML authorization with entitlement mediator.
>- Smooks mediator.
>- Mediation debugging with Integration Studio.
>
> [+] Stable - Go ahead and release.
>
> Thanks.
>
> On Sun, May 19, 2019 at 2:07 AM Sameera Gunarathne 
> wrote:
>
>> Hi all,
>>
>> I tested the following cases.
>>
>>- Split aggregate pattern  with Iterate and Aggregate mediators
>>- Web socket transport
>>- BPMN process creation and task execution in BPS profile
>>- BPMN rest APIs
>>
>> +1 Stable, Go ahead and release.
>>
>> Thanks and Regards,
>> Sameera.
>>
>> On Sat, May 18, 2019 at 2:56 PM Nirothipan Megalingham <
>> nirothi...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> I've tested the following in Ubuntu 18.04 and found no blocker issues
>>> while testing.
>>>
>>>- Deploying sample composite applications in ESB server and Micro
>>>Integrator.
>>>- Listing the artifacts deployed in Micro Integrator via CLI.
>>>- Switch Mediator created in Integration Studio and Management
>>>Console.
>>>- Simple Scheduled Tasks.
>>>- ESB as JMS Producer and Consumer with WSO2 MB.
>>>
>>> +1 for the release.
>>>
>>> Thanks
>>> Nirothipan
>>>
>>>
>>> On Sat, May 18, 2019 at 10:56 AM Kesavan Yogarajah 
>>> wrote:
>>>
 Hi All,

 I tested the following, and no issues found.

- Salesforce Connector
- Salesforce custom inbound Endpoint
- Script mediator


 [+] Stable - go ahead and release

 Thanks
 Kesavan

 Kesavan Yogarajah
 Software Engineer
 Mobile :+94 (0) 779 758021
 kesav...@wso2.com
 WSO2, Inc.
 lean . enterprise . middleware


 On Fri, May 17, 2019 at 11:15 PM Mathuriga Thavarajah <
 mathur...@wso2.com> wrote:

> Hi All,
>
> Security Scanning reports (Static and Dynamic) were analyzed and
> reviewed. Hence +1 from the Platform Security Team for proceeding with the
> release.
>
> Thanks.
>
> Regards,
> Mathuriga.
>
> On Fri, May 17, 2019 at 7:06 PM Chanika Geeganage 
> wrote:
>
>> Hi All,
>>
>> I tested following scenarios ( artifacts were created using both
>> management console and integration studio).
>> 1. Call Template
>> 2. Adding a datasource
>> 3. Generating a dataservice form the datasource
>> 4. Creating a dataservice and uploading a dataservice
>> 5. Tested sample dataservices
>> 6. Odata
>>
>> [+] Stable - go ahead and release
>>
>> On Thu, May 16, 2019 at 7:33 PM Nirothipan Megalingham <
>> nirothi...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> We are pleased to announce the first release candidate of WSO2
>>> Enterprise Integrator 6.5.0.
>>>
>>> Please find the list of tasks / bug fixes and improvements shipped
>>> with this release below
>>>
>>>- Tasks/bug fixes and improvements in Enterprise Integrator
>>>
>>> 
>>>- Tasks/bug fixes and improvements in Micro Integrator
>>>
>>> 
>>>
>>> Known Issues
>>>
>>>- https://github.com/wso2/product-ei/issues
>>>- https://github.com/wso2/micro-integrator/issues
>>>
>>> The tag to be voted upon:
>>> https://github.com/wso2/product-ei/tree/v6.5.0-rc1
>>>
>>> Source and binary distributions:
>>> https://github.com/wso2/product-ei/releases/tag/v6.5.0-rc1
>>>
>>> Please test and vote as follows
>>>
>>> [+] Stable - go ahead and release
>>> [-] Broken - do not release (explain why)
>>>
>>> You may find the official documentation in:
>>> https://docs.wso2.com/display/EI6xx
>>>
>>> ~ The Enterprise Integrator Team ~
>>>
>>>
>>> --
>>>
>>> *M.Nirothipan* | Senior Software Engineer | WSO2 Inc.
>>>
>>> (m) +94772172692 | (e) nirothi...@wso2.com
>>>
>>> [image: http://wso2.com/signature] 
>>>
>>>
>>
>> --
>>
>> *Chanika Geeganage* | Associate Technical Lead | WSO2 Inc.
>>
>> (m) +94-77-3522586 | (e) chan...@wso2.com
>>
>> 
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>
>
> --
>
> *Mathuriga Thavarajah*
> Software Engineer
> WSO2 Inc. - http ://wso2.com
>
>

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

[Hasanthi Purnima Dissanayake]

Hi All,

We had an issue receiving the replies to this thread and seems some of the
replies have lost due to this. Hence if you have sent a vote and it is not
available in the archive [1] please re-send the vote. All the votes we
received are positive once, so we are planing to close the vote with in few
hours. If you have any concerns please raise ASAP.

[1] https://wso2.markmail.org/thread/xuyn7ilrts2xvdsn

Thanks,
Hasanthi

On Wed, May 22, 2019 at 5:15 PM Hasanthi Purnima Dissanayake <
hasan...@wso2.com> wrote:

> Hi All,
>
> I have tested following features.
>
>1. OIDC backchannel logout
>2. SAML front channel logout.
>
> No blocking issues found.
>
> [+] Stable - go ahead and release.
>
> Thanks,
> Hasanthi
>
>
>
> On Wed, May 22, 2019 at 8:03 AM Isuranga Perera  wrote:
>
>> All:
>> I have tested Federated Authentication
>> [+] Stable - go ahead and release.
>>
>> Best Regards
>> Isuranga Perera
>>
>> On Sun, May 19, 2019 at 7:30 PM Shanika Wickramasinghe 
>> wrote:
>>
>>> Hi All,
>>>
>>> I have tested the SAML SSO with POST binding and Redirect binding flows
>>> and no issues found.
>>>
>>> +1 Go Ahead and Release
>>>
>>>
>>> Thanks,
>>>
>>> Shanika
>>>
>>> On Thu, May 16, 2019 at 12:33 PM Hasanthi Purnima Dissanayake <
>>> hasan...@wso2.com> wrote:
>>>
 Hi All,

 The reason of breaking the RC2 vote is because it is reported an unused
 commented configuration description in carbon.xml [1]. From RC3 release
 that commented line in the configuration file is removed and no other code
 level changes done.

 Further in the Analytics-IS pack, the versions are updated according to
 the latest released SP pack versions [2].

 [1] [Dev][VOTE] Release WSO2 Identity Server 5.8.0 RC2
 [2] [VOTE] Release of WSO2 Stream Processor 4.4.0 RC6

 Thanks,
 Hasanthi

 On Thu, May 16, 2019 at 12:30 PM Hasanthi Purnima Dissanayake <
 hasan...@wso2.com> wrote:

> Hi all,
>
> We are pleased to announce the third release candidate of WSO2
> Identity Server 5.8.0.
>
> This release fixes the following issues,
>
>- 5.8.0-RC3 fixes
>
>- 5.8.0-RC2 fixes
>
>- 5.8.0-RC1 fixes
>
>- 5.8.0-Beta5 fixes
>
>- 5.8.0-Beta4 fixes
>
>- 5.8.0-Beta3 fixes
>
>- 5.8.0-Beta fixes
>
>- 5.8.0-Alpha5 fixes
>
>- 5.8.0-Alpha4 fixes
>
>- 5.8.0-Alpha3 fixes
>
>- 5.8.0-Alpha2 fixes
>
>- 5.8.0-Alpha fixes
>
>- 5.8.0-M26 fixes
>
>- 5.8.0-M25 fixes
>
>- 5.8.0-M24 fixes
>
>- 5.8.0-M6 fixes
>
>- 5.8.0-M5 fixes
>
>- 5.8.0-M4 fixes
>
>- 5.8.0-M3 fixes
>
>- 5.8.0-M2 fixes
>
>- 5.8.0-M1 fixes
>
>
>
> Source and distribution
>
> Runtime - https://github.com/wso2/product-is/releases/tag/v
> 
> 5.8.0-rc3
> 
> Analytics -
> https://github.com/wso2/analytics-is/releases/tag/v5.8.0-rc3
> 
>
>
> Please download, test the product and vote.
>
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
>
> Thanks,
> - WSO2 Identity and Access Management Team -
>
> --
>
> Hasanthi Dissanayake
>
> Senior Software Engineer | WSO2
>

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

[Ashen Weerathunga]

Hi All,

I have tested the following scenarios related to IS analytics and found no
issues.

   - Publishing login and session events to the IS analytics server
   - Analyzing login attempts
   - Analyzing session statistics
   - Triggering suspicious login alerts

[+] Stable - go ahead and release

Thanks,
Ashen

On Wed, May 22, 2019 at 5:41 PM Hasanthi Purnima Dissanayake <
hasan...@wso2.com> wrote:

> Hi All,
>
> I have tested following features.
>
>1. OIDC backchannel logout
>2. SAML front channel logout.
>
> No blocking issues found.
>
> [+] Stable - go ahead and release.
>
> Thanks,
> Hasanthi
>
>
>
> On Wed, May 22, 2019 at 8:03 AM Isuranga Perera  wrote:
>
>> All:
>> I have tested Federated Authentication
>> [+] Stable - go ahead and release.
>>
>> Best Regards
>> Isuranga Perera
>>
>> On Sun, May 19, 2019 at 7:30 PM Shanika Wickramasinghe 
>> wrote:
>>
>>> Hi All,
>>>
>>> I have tested the SAML SSO with POST binding and Redirect binding flows
>>> and no issues found.
>>>
>>> +1 Go Ahead and Release
>>>
>>>
>>> Thanks,
>>>
>>> Shanika
>>>
>>> On Thu, May 16, 2019 at 12:33 PM Hasanthi Purnima Dissanayake <
>>> hasan...@wso2.com> wrote:
>>>
 Hi All,

 The reason of breaking the RC2 vote is because it is reported an unused
 commented configuration description in carbon.xml [1]. From RC3 release
 that commented line in the configuration file is removed and no other code
 level changes done.

 Further in the Analytics-IS pack, the versions are updated according to
 the latest released SP pack versions [2].

 [1] [Dev][VOTE] Release WSO2 Identity Server 5.8.0 RC2
 [2] [VOTE] Release of WSO2 Stream Processor 4.4.0 RC6

 Thanks,
 Hasanthi

 On Thu, May 16, 2019 at 12:30 PM Hasanthi Purnima Dissanayake <
 hasan...@wso2.com> wrote:

> Hi all,
>
> We are pleased to announce the third release candidate of WSO2
> Identity Server 5.8.0.
>
> This release fixes the following issues,
>
>- 5.8.0-RC3 fixes
>
>- 5.8.0-RC2 fixes
>
>- 5.8.0-RC1 fixes
>
>- 5.8.0-Beta5 fixes
>
>- 5.8.0-Beta4 fixes
>
>- 5.8.0-Beta3 fixes
>
>- 5.8.0-Beta fixes
>
>- 5.8.0-Alpha5 fixes
>
>- 5.8.0-Alpha4 fixes
>
>- 5.8.0-Alpha3 fixes
>
>- 5.8.0-Alpha2 fixes
>
>- 5.8.0-Alpha fixes
>
>- 5.8.0-M26 fixes
>
>- 5.8.0-M25 fixes
>
>- 5.8.0-M24 fixes
>
>- 5.8.0-M6 fixes
>
>- 5.8.0-M5 fixes
>
>- 5.8.0-M4 fixes
>
>- 5.8.0-M3 fixes
>
>- 5.8.0-M2 fixes
>
>- 5.8.0-M1 fixes
>
>
>
> Source and distribution
>
> Runtime - https://github.com/wso2/product-is/releases/tag/v
> 
> 5.8.0-rc3
> 
> Analytics -
> https://github.com/wso2/analytics-is/releases/tag/v5.8.0-rc3
> 
>
>
> Please download, test the product and vote.
>
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
>
> Thanks,
> - WSO2 Identity and Access Management Team -
>
> --
>
> Hasanthi Dissanayake
>
> Senior Software Engineer | WSO2
>
> E: hasan...@wso2.com
> M :0718407133| http://wso2.com 
>


 --

>>

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

[Farasath Ahamed]

Hi All,

Test the below scenarios in IS 5.8.0 RC3 pack.

   - Token revocation with authorization code reuse
   - OIDC UserInfo with token sent in the request body and as bearer header
   - OAuth Application Owner update
   - Verified no username enumeration attacks possible during password
   recovery flows.


[+] Stable - go ahead and release.


Regards,
Farasath

On Wed, May 22, 2019 at 5:41 PM Hasanthi Purnima Dissanayake <
hasan...@wso2.com> wrote:

> Hi All,
>
> I have tested following features.
>
>1. OIDC backchannel logout
>2. SAML front channel logout.
>
> No blocking issues found.
>
> [+] Stable - go ahead and release.
>
> Thanks,
> Hasanthi
>
>
>
> On Wed, May 22, 2019 at 8:03 AM Isuranga Perera  wrote:
>
>> All:
>> I have tested Federated Authentication
>> [+] Stable - go ahead and release.
>>
>> Best Regards
>> Isuranga Perera
>>
>> On Sun, May 19, 2019 at 7:30 PM Shanika Wickramasinghe 
>> wrote:
>>
>>> Hi All,
>>>
>>> I have tested the SAML SSO with POST binding and Redirect binding flows
>>> and no issues found.
>>>
>>> +1 Go Ahead and Release
>>>
>>>
>>> Thanks,
>>>
>>> Shanika
>>>
>>> On Thu, May 16, 2019 at 12:33 PM Hasanthi Purnima Dissanayake <
>>> hasan...@wso2.com> wrote:
>>>
 Hi All,

 The reason of breaking the RC2 vote is because it is reported an unused
 commented configuration description in carbon.xml [1]. From RC3 release
 that commented line in the configuration file is removed and no other code
 level changes done.

 Further in the Analytics-IS pack, the versions are updated according to
 the latest released SP pack versions [2].

 [1] [Dev][VOTE] Release WSO2 Identity Server 5.8.0 RC2
 [2] [VOTE] Release of WSO2 Stream Processor 4.4.0 RC6

 Thanks,
 Hasanthi

 On Thu, May 16, 2019 at 12:30 PM Hasanthi Purnima Dissanayake <
 hasan...@wso2.com> wrote:

> Hi all,
>
> We are pleased to announce the third release candidate of WSO2
> Identity Server 5.8.0.
>
> This release fixes the following issues,
>
>- 5.8.0-RC3 fixes
>
>- 5.8.0-RC2 fixes
>
>- 5.8.0-RC1 fixes
>
>- 5.8.0-Beta5 fixes
>
>- 5.8.0-Beta4 fixes
>
>- 5.8.0-Beta3 fixes
>
>- 5.8.0-Beta fixes
>
>- 5.8.0-Alpha5 fixes
>
>- 5.8.0-Alpha4 fixes
>
>- 5.8.0-Alpha3 fixes
>
>- 5.8.0-Alpha2 fixes
>
>- 5.8.0-Alpha fixes
>
>- 5.8.0-M26 fixes
>
>- 5.8.0-M25 fixes
>
>- 5.8.0-M24 fixes
>
>- 5.8.0-M6 fixes
>
>- 5.8.0-M5 fixes
>
>- 5.8.0-M4 fixes
>
>- 5.8.0-M3 fixes
>
>- 5.8.0-M2 fixes
>
>- 5.8.0-M1 fixes
>
>
>
> Source and distribution
>
> Runtime - https://github.com/wso2/product-is/releases/tag/v
> 
> 5.8.0-rc3
> 
> Analytics -
> https://github.com/wso2/analytics-is/releases/tag/v5.8.0-rc3
> 
>
>
> Please download, test the product and vote.
>
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
>
> Thanks,
> - WSO2 Identity and Access Management Team -
>
> --
>
> Hasanthi Dissanayake
>
> Senior Software Engineer | WSO2
>
> E: hasan...@wso2.com
> M :0718407133| http://wso2.c

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

[Kanapriya Kuleswararajan]

Hi All,
Resend the vote as I couldn't find my name in the archive.

Tested the following and It works fine.

- Basic functionality with EmailOTP (Basic authenticator/Federated
Authenticator as first step and EmailOTP as the second step)
- EmailOTP with Email Templates
- TOTP with basic functionality
- X509 with basic functionality
- Tried EmailOTP/TOTP with secondary user stores.

[+1] Stable - go ahead and release


Kanapriya Kuleswararajan
Senior Software Engineer
Mobile : - 0774894438
Mail : - kanapr...@wso2.com
LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/
WSO2, Inc.
lean . enterprise . middleware



On Wed, May 22, 2019 at 7:46 PM Hasanthi Purnima Dissanayake <
hasan...@wso2.com> wrote:

> Hi All,
>
> We had an issue receiving the replies to this thread and seems some of the
> replies have lost due to this. Hence if you have sent a vote and it is not
> available in the archive [1] please re-send the vote. All the votes we
> received are positive once, so we are planing to close the vote with in few
> hours. If you have any concerns please raise ASAP.
>
> [1] https://wso2.markmail.org/thread/xuyn7ilrts2xvdsn
>
> Thanks,
> Hasanthi
>
> On Wed, May 22, 2019 at 5:15 PM Hasanthi Purnima Dissanayake <
> hasan...@wso2.com> wrote:
>
>> Hi All,
>>
>> I have tested following features.
>>
>>1. OIDC backchannel logout
>>2. SAML front channel logout.
>>
>> No blocking issues found.
>>
>> [+] Stable - go ahead and release.
>>
>> Thanks,
>> Hasanthi
>>
>>
>>
>> On Wed, May 22, 2019 at 8:03 AM Isuranga Perera 
>> wrote:
>>
>>> All:
>>> I have tested Federated Authentication
>>> [+] Stable - go ahead and release.
>>>
>>> Best Regards
>>> Isuranga Perera
>>>
>>> On Sun, May 19, 2019 at 7:30 PM Shanika Wickramasinghe <
>>> shani...@wso2.com> wrote:
>>>
 Hi All,

 I have tested the SAML SSO with POST binding and Redirect binding flows
 and no issues found.

 +1 Go Ahead and Release


 Thanks,

 Shanika

 On Thu, May 16, 2019 at 12:33 PM Hasanthi Purnima Dissanayake <
 hasan...@wso2.com> wrote:

> Hi All,
>
> The reason of breaking the RC2 vote is because it is reported an
> unused commented configuration description in carbon.xml [1]. From RC3
> release that commented line in the configuration file is removed and no
> other code level changes done.
>
> Further in the Analytics-IS pack, the versions are updated according
> to the latest released SP pack versions [2].
>
> [1] [Dev][VOTE] Release WSO2 Identity Server 5.8.0 RC2
> [2] [VOTE] Release of WSO2 Stream Processor 4.4.0 RC6
>
> Thanks,
> Hasanthi
>
> On Thu, May 16, 2019 at 12:30 PM Hasanthi Purnima Dissanayake <
> hasan...@wso2.com> wrote:
>
>> Hi all,
>>
>> We are pleased to announce the third release candidate of WSO2
>> Identity Server 5.8.0.
>>
>> This release fixes the following issues,
>>
>>- 5.8.0-RC3 fixes
>>
>>- 5.8.0-RC2 fixes
>>
>>- 5.8.0-RC1 fixes
>>
>>- 5.8.0-Beta5 fixes
>>
>>- 5.8.0-Beta4 fixes
>>
>>- 5.8.0-Beta3 fixes
>>
>>- 5.8.0-Beta fixes
>>
>>- 5.8.0-Alpha5 fixes
>>
>>- 5.8.0-Alpha4 fixes
>>
>>- 5.8.0-Alpha3 fixes
>>
>>- 5.8.0-Alpha2 fixes
>>
>>- 5.8.0-Alpha fixes
>>
>>- 5.8.0-M26 fixes
>>
>>- 5.8.0-M25 fixes
>>
>>- 5.8.0-M24 fixes
>>
>>- 5.8.0-M6 fixes
>>
>>- 5.8.0-M5 fixes
>>
>>- 5.8.0-M4 fixes
>>
>>- 5.8.0-M3 fixes
>>
>>- 5.8.0-M2 fixes
>>
>>- 5.8.0-M1 fixes
>>

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

[Isura Karunaratne]

Hi all,

Tested following features and no issues found.

   - Self User Registration
   - Password Policy
   - Password History
   - Password Recovery
   - Account Locking

[+] Stable - go ahead and release.

Cheers,
Isura.

On Wed, May 22, 2019 at 8:07 PM Farasath Ahamed  wrote:

> Hi All,
>
> Test the below scenarios in IS 5.8.0 RC3 pack.
>
>- Token revocation with authorization code reuse
>- OIDC UserInfo with token sent in the request body and as bearer
>header
>- OAuth Application Owner update
>- Verified no username enumeration attacks possible during password
>recovery flows.
>
>
> [+] Stable - go ahead and release.
>
>
> Regards,
> Farasath
>
> On Wed, May 22, 2019 at 5:41 PM Hasanthi Purnima Dissanayake <
> hasan...@wso2.com> wrote:
>
>> Hi All,
>>
>> I have tested following features.
>>
>>1. OIDC backchannel logout
>>2. SAML front channel logout.
>>
>> No blocking issues found.
>>
>> [+] Stable - go ahead and release.
>>
>> Thanks,
>> Hasanthi
>>
>>
>>
>> On Wed, May 22, 2019 at 8:03 AM Isuranga Perera 
>> wrote:
>>
>>> All:
>>> I have tested Federated Authentication
>>> [+] Stable - go ahead and release.
>>>
>>> Best Regards
>>> Isuranga Perera
>>>
>>> On Sun, May 19, 2019 at 7:30 PM Shanika Wickramasinghe <
>>> shani...@wso2.com> wrote:
>>>
 Hi All,

 I have tested the SAML SSO with POST binding and Redirect binding flows
 and no issues found.

 +1 Go Ahead and Release


 Thanks,

 Shanika

 On Thu, May 16, 2019 at 12:33 PM Hasanthi Purnima Dissanayake <
 hasan...@wso2.com> wrote:

> Hi All,
>
> The reason of breaking the RC2 vote is because it is reported an
> unused commented configuration description in carbon.xml [1]. From RC3
> release that commented line in the configuration file is removed and no
> other code level changes done.
>
> Further in the Analytics-IS pack, the versions are updated according
> to the latest released SP pack versions [2].
>
> [1] [Dev][VOTE] Release WSO2 Identity Server 5.8.0 RC2
> [2] [VOTE] Release of WSO2 Stream Processor 4.4.0 RC6
>
> Thanks,
> Hasanthi
>
> On Thu, May 16, 2019 at 12:30 PM Hasanthi Purnima Dissanayake <
> hasan...@wso2.com> wrote:
>
>> Hi all,
>>
>> We are pleased to announce the third release candidate of WSO2
>> Identity Server 5.8.0.
>>
>> This release fixes the following issues,
>>
>>- 5.8.0-RC3 fixes
>>
>>- 5.8.0-RC2 fixes
>>
>>- 5.8.0-RC1 fixes
>>
>>- 5.8.0-Beta5 fixes
>>
>>- 5.8.0-Beta4 fixes
>>
>>- 5.8.0-Beta3 fixes
>>
>>- 5.8.0-Beta fixes
>>
>>- 5.8.0-Alpha5 fixes
>>
>>- 5.8.0-Alpha4 fixes
>>
>>- 5.8.0-Alpha3 fixes
>>
>>- 5.8.0-Alpha2 fixes
>>
>>- 5.8.0-Alpha fixes
>>
>>- 5.8.0-M26 fixes
>>
>>- 5.8.0-M25 fixes
>>
>>- 5.8.0-M24 fixes
>>
>>- 5.8.0-M6 fixes
>>
>>- 5.8.0-M5 fixes
>>
>>- 5.8.0-M4 fixes
>>
>>- 5.8.0-M3 fixes
>>
>>- 5.8.0-M2 fixes
>>
>>- 5.8.0-M1 fixes
>>
>>
>>
>> Source and distribution
>>
>> Runtime - https://github.com/wso2/product-is/releases/tag/v
>> 
>> 5.8.0-rc3
>> 
>> Analytics -
>> https://github.com/wso2/analytics-is/releases/tag/v5.8.0-rc3
>> 

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

[Senthalan Kanagalingam]

Hi all,

I have tested the following functionalities

   - Create a service provider using file
   - SSO with SAML and OAuth app
   - Role-based adaptive authentication policy

No issues found, Hence +1 to go ahead and release.

Thanks,
Senthalan

On Wed, May 22, 2019 at 8:07 PM Farasath Ahamed  wrote:

> Hi All,
>
> Test the below scenarios in IS 5.8.0 RC3 pack.
>
>- Token revocation with authorization code reuse
>- OIDC UserInfo with token sent in the request body and as bearer
>header
>- OAuth Application Owner update
>- Verified no username enumeration attacks possible during password
>recovery flows.
>
>
> [+] Stable - go ahead and release.
>
>
> Regards,
> Farasath
>
> On Wed, May 22, 2019 at 5:41 PM Hasanthi Purnima Dissanayake <
> hasan...@wso2.com> wrote:
>
>> Hi All,
>>
>> I have tested following features.
>>
>>1. OIDC backchannel logout
>>2. SAML front channel logout.
>>
>> No blocking issues found.
>>
>> [+] Stable - go ahead and release.
>>
>> Thanks,
>> Hasanthi
>>
>>
>>
>> On Wed, May 22, 2019 at 8:03 AM Isuranga Perera 
>> wrote:
>>
>>> All:
>>> I have tested Federated Authentication
>>> [+] Stable - go ahead and release.
>>>
>>> Best Regards
>>> Isuranga Perera
>>>
>>> On Sun, May 19, 2019 at 7:30 PM Shanika Wickramasinghe <
>>> shani...@wso2.com> wrote:
>>>
 Hi All,

 I have tested the SAML SSO with POST binding and Redirect binding flows
 and no issues found.

 +1 Go Ahead and Release


 Thanks,

 Shanika

 On Thu, May 16, 2019 at 12:33 PM Hasanthi Purnima Dissanayake <
 hasan...@wso2.com> wrote:

> Hi All,
>
> The reason of breaking the RC2 vote is because it is reported an
> unused commented configuration description in carbon.xml [1]. From RC3
> release that commented line in the configuration file is removed and no
> other code level changes done.
>
> Further in the Analytics-IS pack, the versions are updated according
> to the latest released SP pack versions [2].
>
> [1] [Dev][VOTE] Release WSO2 Identity Server 5.8.0 RC2
> [2] [VOTE] Release of WSO2 Stream Processor 4.4.0 RC6
>
> Thanks,
> Hasanthi
>
> On Thu, May 16, 2019 at 12:30 PM Hasanthi Purnima Dissanayake <
> hasan...@wso2.com> wrote:
>
>> Hi all,
>>
>> We are pleased to announce the third release candidate of WSO2
>> Identity Server 5.8.0.
>>
>> This release fixes the following issues,
>>
>>- 5.8.0-RC3 fixes
>>
>>- 5.8.0-RC2 fixes
>>
>>- 5.8.0-RC1 fixes
>>
>>- 5.8.0-Beta5 fixes
>>
>>- 5.8.0-Beta4 fixes
>>
>>- 5.8.0-Beta3 fixes
>>
>>- 5.8.0-Beta fixes
>>
>>- 5.8.0-Alpha5 fixes
>>
>>- 5.8.0-Alpha4 fixes
>>
>>- 5.8.0-Alpha3 fixes
>>
>>- 5.8.0-Alpha2 fixes
>>
>>- 5.8.0-Alpha fixes
>>
>>- 5.8.0-M26 fixes
>>
>>- 5.8.0-M25 fixes
>>
>>- 5.8.0-M24 fixes
>>
>>- 5.8.0-M6 fixes
>>
>>- 5.8.0-M5 fixes
>>
>>- 5.8.0-M4 fixes
>>
>>- 5.8.0-M3 fixes
>>
>>- 5.8.0-M2 fixes
>>
>>- 5.8.0-M1 fixes
>>
>>
>>
>> Source and distribution
>>
>> Runtime - https://github.com/wso2/product-is/releases/tag/v
>> 
>> 5.8.0-rc3
>> 
>> Analytics -
>> https://github.com/wso2/analytics-is/releases/tag/v5.8.0-rc3
>> 

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

[Maduranga Siriwardena]

Hi All,

Tested the authorization code grant flow with below configs using a native
Android client.

   - PKCE enabled
   - authentication without the client secret enabled
   - Support PKCE 'Plain' Transform Algorithm disabled

[+] Stable - go ahead and release.

Regards,
Maduranga.

On Wed, May 22, 2019 at 8:07 PM Farasath Ahamed  wrote:

> Hi All,
>
> Test the below scenarios in IS 5.8.0 RC3 pack.
>
>- Token revocation with authorization code reuse
>- OIDC UserInfo with token sent in the request body and as bearer
>header
>- OAuth Application Owner update
>- Verified no username enumeration attacks possible during password
>recovery flows.
>
>
> [+] Stable - go ahead and release.
>
>
> Regards,
> Farasath
>
> On Wed, May 22, 2019 at 5:41 PM Hasanthi Purnima Dissanayake <
> hasan...@wso2.com> wrote:
>
>> Hi All,
>>
>> I have tested following features.
>>
>>1. OIDC backchannel logout
>>2. SAML front channel logout.
>>
>> No blocking issues found.
>>
>> [+] Stable - go ahead and release.
>>
>> Thanks,
>> Hasanthi
>>
>>
>>
>> On Wed, May 22, 2019 at 8:03 AM Isuranga Perera 
>> wrote:
>>
>>> All:
>>> I have tested Federated Authentication
>>> [+] Stable - go ahead and release.
>>>
>>> Best Regards
>>> Isuranga Perera
>>>
>>> On Sun, May 19, 2019 at 7:30 PM Shanika Wickramasinghe <
>>> shani...@wso2.com> wrote:
>>>
 Hi All,

 I have tested the SAML SSO with POST binding and Redirect binding flows
 and no issues found.

 +1 Go Ahead and Release


 Thanks,

 Shanika

 On Thu, May 16, 2019 at 12:33 PM Hasanthi Purnima Dissanayake <
 hasan...@wso2.com> wrote:

> Hi All,
>
> The reason of breaking the RC2 vote is because it is reported an
> unused commented configuration description in carbon.xml [1]. From RC3
> release that commented line in the configuration file is removed and no
> other code level changes done.
>
> Further in the Analytics-IS pack, the versions are updated according
> to the latest released SP pack versions [2].
>
> [1] [Dev][VOTE] Release WSO2 Identity Server 5.8.0 RC2
> [2] [VOTE] Release of WSO2 Stream Processor 4.4.0 RC6
>
> Thanks,
> Hasanthi
>
> On Thu, May 16, 2019 at 12:30 PM Hasanthi Purnima Dissanayake <
> hasan...@wso2.com> wrote:
>
>> Hi all,
>>
>> We are pleased to announce the third release candidate of WSO2
>> Identity Server 5.8.0.
>>
>> This release fixes the following issues,
>>
>>- 5.8.0-RC3 fixes
>>
>>- 5.8.0-RC2 fixes
>>
>>- 5.8.0-RC1 fixes
>>
>>- 5.8.0-Beta5 fixes
>>
>>- 5.8.0-Beta4 fixes
>>
>>- 5.8.0-Beta3 fixes
>>
>>- 5.8.0-Beta fixes
>>
>>- 5.8.0-Alpha5 fixes
>>
>>- 5.8.0-Alpha4 fixes
>>
>>- 5.8.0-Alpha3 fixes
>>
>>- 5.8.0-Alpha2 fixes
>>
>>- 5.8.0-Alpha fixes
>>
>>- 5.8.0-M26 fixes
>>
>>- 5.8.0-M25 fixes
>>
>>- 5.8.0-M24 fixes
>>
>>- 5.8.0-M6 fixes
>>
>>- 5.8.0-M5 fixes
>>
>>- 5.8.0-M4 fixes
>>
>>- 5.8.0-M3 fixes
>>
>>- 5.8.0-M2 fixes
>>
>>- 5.8.0-M1 fixes
>>
>>
>>
>> Source and distribution
>>
>> Runtime - https://github.com/wso2/product-is/releases/tag/v
>> 
>> 5.8.0-rc3
>> 
>> Analytics -
>> https://github.com/wso2/analytics-is/relea

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

[Thanuja Jayasinghe]

Hi All,

Tested following scenarios,

- Local user account association
- OAuth2 grat types (code, implicit, password, client credential)
- SAML2 SSO & SLO

[+] Stable - go ahead and release.

Thanks,
Thanuja

On Wed, May 22, 2019 at 8:07 PM Farasath Ahamed  wrote:

> Hi All,
>
> Test the below scenarios in IS 5.8.0 RC3 pack.
>
>- Token revocation with authorization code reuse
>- OIDC UserInfo with token sent in the request body and as bearer
>header
>- OAuth Application Owner update
>- Verified no username enumeration attacks possible during password
>recovery flows.
>
>
> [+] Stable - go ahead and release.
>
>
> Regards,
> Farasath
>
> On Wed, May 22, 2019 at 5:41 PM Hasanthi Purnima Dissanayake <
> hasan...@wso2.com> wrote:
>
>> Hi All,
>>
>> I have tested following features.
>>
>>1. OIDC backchannel logout
>>2. SAML front channel logout.
>>
>> No blocking issues found.
>>
>> [+] Stable - go ahead and release.
>>
>> Thanks,
>> Hasanthi
>>
>>
>>
>> On Wed, May 22, 2019 at 8:03 AM Isuranga Perera 
>> wrote:
>>
>>> All:
>>> I have tested Federated Authentication
>>> [+] Stable - go ahead and release.
>>>
>>> Best Regards
>>> Isuranga Perera
>>>
>>> On Sun, May 19, 2019 at 7:30 PM Shanika Wickramasinghe <
>>> shani...@wso2.com> wrote:
>>>
 Hi All,

 I have tested the SAML SSO with POST binding and Redirect binding flows
 and no issues found.

 +1 Go Ahead and Release


 Thanks,

 Shanika

 On Thu, May 16, 2019 at 12:33 PM Hasanthi Purnima Dissanayake <
 hasan...@wso2.com> wrote:

> Hi All,
>
> The reason of breaking the RC2 vote is because it is reported an
> unused commented configuration description in carbon.xml [1]. From RC3
> release that commented line in the configuration file is removed and no
> other code level changes done.
>
> Further in the Analytics-IS pack, the versions are updated according
> to the latest released SP pack versions [2].
>
> [1] [Dev][VOTE] Release WSO2 Identity Server 5.8.0 RC2
> [2] [VOTE] Release of WSO2 Stream Processor 4.4.0 RC6
>
> Thanks,
> Hasanthi
>
> On Thu, May 16, 2019 at 12:30 PM Hasanthi Purnima Dissanayake <
> hasan...@wso2.com> wrote:
>
>> Hi all,
>>
>> We are pleased to announce the third release candidate of WSO2
>> Identity Server 5.8.0.
>>
>> This release fixes the following issues,
>>
>>- 5.8.0-RC3 fixes
>>
>>- 5.8.0-RC2 fixes
>>
>>- 5.8.0-RC1 fixes
>>
>>- 5.8.0-Beta5 fixes
>>
>>- 5.8.0-Beta4 fixes
>>
>>- 5.8.0-Beta3 fixes
>>
>>- 5.8.0-Beta fixes
>>
>>- 5.8.0-Alpha5 fixes
>>
>>- 5.8.0-Alpha4 fixes
>>
>>- 5.8.0-Alpha3 fixes
>>
>>- 5.8.0-Alpha2 fixes
>>
>>- 5.8.0-Alpha fixes
>>
>>- 5.8.0-M26 fixes
>>
>>- 5.8.0-M25 fixes
>>
>>- 5.8.0-M24 fixes
>>
>>- 5.8.0-M6 fixes
>>
>>- 5.8.0-M5 fixes
>>
>>- 5.8.0-M4 fixes
>>
>>- 5.8.0-M3 fixes
>>
>>- 5.8.0-M2 fixes
>>
>>- 5.8.0-M1 fixes
>>
>>
>>
>> Source and distribution
>>
>> Runtime - https://github.com/wso2/product-is/releases/tag/v
>> 
>> 5.8.0-rc3
>> 
>> Analytics -
>> https://github.com/wso2/analytics-is/releases/tag/v5.8.0-rc3
>> 

Re: [Architecture] [Dev] [VOTE] Release WSO2 Enterprise Integrator 6.5.0 RC1

[Asanka Abeyweera]

Hi all,

I tested the following and found no blocking issues.

   - Micro Integrator basic functionality
   - Micro Integrator Docker image basic functionality
   - Micro Integrator basic functionality in a Kubernetes cluster

[+]  Stable - go ahead and release.

On Wed, May 22, 2019 at 5:59 PM Menuka Warushavithana 
wrote:

> Hi all,
>
> I have tested the following and found no issues.
>
>- CXF WS-RM Inbound Protocol
>- WebSocket Inbound Protocol
>
>
> +1 Stable - go ahead and release.
>
>
> Thanks,
> Menuka
>
> On Wed, May 22, 2019 at 6:11 AM Thishani Lucas  wrote:
>
>> Hi all,
>>
>> Tested the following.
>>
>>- XACML authorization with entitlement mediator.
>>- Smooks mediator.
>>- Mediation debugging with Integration Studio.
>>
>> [+] Stable - Go ahead and release.
>>
>> Thanks.
>>
>> On Sun, May 19, 2019 at 2:07 AM Sameera Gunarathne 
>> wrote:
>>
>>> Hi all,
>>>
>>> I tested the following cases.
>>>
>>>- Split aggregate pattern  with Iterate and Aggregate mediators
>>>- Web socket transport
>>>- BPMN process creation and task execution in BPS profile
>>>- BPMN rest APIs
>>>
>>> +1 Stable, Go ahead and release.
>>>
>>> Thanks and Regards,
>>> Sameera.
>>>
>>> On Sat, May 18, 2019 at 2:56 PM Nirothipan Megalingham <
>>> nirothi...@wso2.com> wrote:
>>>
 Hi all,

 I've tested the following in Ubuntu 18.04 and found no blocker issues
 while testing.

- Deploying sample composite applications in ESB server and Micro
Integrator.
- Listing the artifacts deployed in Micro Integrator via CLI.
- Switch Mediator created in Integration Studio and Management
Console.
- Simple Scheduled Tasks.
- ESB as JMS Producer and Consumer with WSO2 MB.

 +1 for the release.

 Thanks
 Nirothipan


 On Sat, May 18, 2019 at 10:56 AM Kesavan Yogarajah 
 wrote:

> Hi All,
>
> I tested the following, and no issues found.
>
>- Salesforce Connector
>- Salesforce custom inbound Endpoint
>- Script mediator
>
>
> [+] Stable - go ahead and release
>
> Thanks
> Kesavan
>
> Kesavan Yogarajah
> Software Engineer
> Mobile :+94 (0) 779 758021
> kesav...@wso2.com
> WSO2, Inc.
> lean . enterprise . middleware
>
>
> On Fri, May 17, 2019 at 11:15 PM Mathuriga Thavarajah <
> mathur...@wso2.com> wrote:
>
>> Hi All,
>>
>> Security Scanning reports (Static and Dynamic) were analyzed and
>> reviewed. Hence +1 from the Platform Security Team for proceeding with 
>> the
>> release.
>>
>> Thanks.
>>
>> Regards,
>> Mathuriga.
>>
>> On Fri, May 17, 2019 at 7:06 PM Chanika Geeganage 
>> wrote:
>>
>>> Hi All,
>>>
>>> I tested following scenarios ( artifacts were created using both
>>> management console and integration studio).
>>> 1. Call Template
>>> 2. Adding a datasource
>>> 3. Generating a dataservice form the datasource
>>> 4. Creating a dataservice and uploading a dataservice
>>> 5. Tested sample dataservices
>>> 6. Odata
>>>
>>> [+] Stable - go ahead and release
>>>
>>> On Thu, May 16, 2019 at 7:33 PM Nirothipan Megalingham <
>>> nirothi...@wso2.com> wrote:
>>>
 Hi all,

 We are pleased to announce the first release candidate of WSO2
 Enterprise Integrator 6.5.0.

 Please find the list of tasks / bug fixes and improvements shipped
 with this release below

- Tasks/bug fixes and improvements in Enterprise Integrator

 
- Tasks/bug fixes and improvements in Micro Integrator

 

 Known Issues

- https://github.com/wso2/product-ei/issues
- https://github.com/wso2/micro-integrator/issues

 The tag to be voted upon:
 https://github.com/wso2/product-ei/tree/v6.5.0-rc1

 Source and binary distributions:
 https://github.com/wso2/product-ei/releases/tag/v6.5.0-rc1

 Please test and vote as follows

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

 You may find the official documentation in:
 https://docs.wso2.com/display/EI6xx

 ~ The Enterprise Integrator Team ~


 --

 *M.Nirothipan* | Senior Software Engineer | WSO2 Inc.

 (m) +94772172692 | (e) nirothi...@wso2.com

 [image: http://wso2.com/signature] 

>

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

[Hasini Witharana]

HI All,

Following scenarios were tested

SCIM 2.0 Endpoints

   1. Bulk Endpoint
  - Create Users in Bulk
  2. Groups Endpoint
  - Create Group
  - Delete Group
  - Filter Groups
  3. Users Endpoint
  - Create User
  - Delete User by ID
  - Filter Users

[+] Stable - go ahead and release.

Best Regards,
Hasini.

On Wed, May 22, 2019 at 9:11 PM Kanapriya Kuleswararajan 
wrote:

> Hi All,
> Resend the vote as I couldn't find my name in the archive.
>
> Tested the following and It works fine.
>
> - Basic functionality with EmailOTP (Basic authenticator/Federated
> Authenticator as first step and EmailOTP as the second step)
> - EmailOTP with Email Templates
> - TOTP with basic functionality
> - X509 with basic functionality
> - Tried EmailOTP/TOTP with secondary user stores.
>
> [+1] Stable - go ahead and release
>
>
> Kanapriya Kuleswararajan
> Senior Software Engineer
> Mobile : - 0774894438
> Mail : - kanapr...@wso2.com
> LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/
> WSO2, Inc.
> lean . enterprise . middleware
>
>
>
> On Wed, May 22, 2019 at 7:46 PM Hasanthi Purnima Dissanayake <
> hasan...@wso2.com> wrote:
>
>> Hi All,
>>
>> We had an issue receiving the replies to this thread and seems some of
>> the replies have lost due to this. Hence if you have sent a vote and it is
>> not available in the archive [1] please re-send the vote. All the votes we
>> received are positive once, so we are planing to close the vote with in few
>> hours. If you have any concerns please raise ASAP.
>>
>> [1] https://wso2.markmail.org/thread/xuyn7ilrts2xvdsn
>>
>> Thanks,
>> Hasanthi
>>
>> On Wed, May 22, 2019 at 5:15 PM Hasanthi Purnima Dissanayake <
>> hasan...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> I have tested following features.
>>>
>>>1. OIDC backchannel logout
>>>2. SAML front channel logout.
>>>
>>> No blocking issues found.
>>>
>>> [+] Stable - go ahead and release.
>>>
>>> Thanks,
>>> Hasanthi
>>>
>>>
>>>
>>> On Wed, May 22, 2019 at 8:03 AM Isuranga Perera 
>>> wrote:
>>>
 All:
 I have tested Federated Authentication
 [+] Stable - go ahead and release.

 Best Regards
 Isuranga Perera

 On Sun, May 19, 2019 at 7:30 PM Shanika Wickramasinghe <
 shani...@wso2.com> wrote:

> Hi All,
>
> I have tested the SAML SSO with POST binding and Redirect binding
> flows and no issues found.
>
> +1 Go Ahead and Release
>
>
> Thanks,
>
> Shanika
>
> On Thu, May 16, 2019 at 12:33 PM Hasanthi Purnima Dissanayake <
> hasan...@wso2.com> wrote:
>
>> Hi All,
>>
>> The reason of breaking the RC2 vote is because it is reported an
>> unused commented configuration description in carbon.xml [1]. From RC3
>> release that commented line in the configuration file is removed and no
>> other code level changes done.
>>
>> Further in the Analytics-IS pack, the versions are updated according
>> to the latest released SP pack versions [2].
>>
>> [1] [Dev][VOTE] Release WSO2 Identity Server 5.8.0 RC2
>> [2] [VOTE] Release of WSO2 Stream Processor 4.4.0 RC6
>>
>> Thanks,
>> Hasanthi
>>
>> On Thu, May 16, 2019 at 12:30 PM Hasanthi Purnima Dissanayake <
>> hasan...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> We are pleased to announce the third release candidate of WSO2
>>> Identity Server 5.8.0.
>>>
>>> This release fixes the following issues,
>>>
>>>- 5.8.0-RC3 fixes
>>>
>>>- 5.8.0-RC2 fixes
>>>
>>>- 5.8.0-RC1 fixes
>>>
>>>- 5.8.0-Beta5 fixes
>>>
>>>- 5.8.0-Beta4 fixes
>>>
>>>- 5.8.0-Beta3 fixes
>>>
>>>- 5.8.0-Beta fixes
>>>
>>>- 5.8.0-Alpha5 fixes
>>>
>>>- 5.8.0-Alpha4 fixes
>>>
>>>- 5.8.0-Alpha3 fixes
>>>
>>>- 5.8.0-Alpha2 fixes
>>>
>>>- 5.8.0-Alpha fixes
>>>
>>>- 5.8.0-M26 fixes
>>>
>>>- 5.8.0-M25 fixes
>>>
>>>- 5.8.0-M24 fixes
>>>

Re: [Architecture] [Dev] [VOTE] Release WSO2 Enterprise Integrator 6.5.0 RC1

[Nirothipan M]

Hello everyone,

We noticed that some of the replies which were sent to this mail were not
received due to some server error.
Kindly verify whether your replies are available in archive [1] and if not
please re send the votes. Apologies for the inconvenience caused.

All the replies we have received so far are positive ones and we are
planning to close the voting in few more hours based on it.
If you have any concerns please let us know as soon as possible.

[1] - https://markmail.org/thread/ta4r5yceahm7m5ef

~ The Enterprise Integrator Team ~

On Wed, May 22, 2019 at 5:59 PM Menuka Warushavithana 
wrote:

> Hi all,
>
> I have tested the following and found no issues.
>
>- CXF WS-RM Inbound Protocol
>- WebSocket Inbound Protocol
>
>
> +1 Stable - go ahead and release.
>
>
> Thanks,
> Menuka
>
> On Wed, May 22, 2019 at 6:11 AM Thishani Lucas  wrote:
>
>> Hi all,
>>
>> Tested the following.
>>
>>- XACML authorization with entitlement mediator.
>>- Smooks mediator.
>>- Mediation debugging with Integration Studio.
>>
>> [+] Stable - Go ahead and release.
>>
>> Thanks.
>>
>> On Sun, May 19, 2019 at 2:07 AM Sameera Gunarathne 
>> wrote:
>>
>>> Hi all,
>>>
>>> I tested the following cases.
>>>
>>>- Split aggregate pattern  with Iterate and Aggregate mediators
>>>- Web socket transport
>>>- BPMN process creation and task execution in BPS profile
>>>- BPMN rest APIs
>>>
>>> +1 Stable, Go ahead and release.
>>>
>>> Thanks and Regards,
>>> Sameera.
>>>
>>> On Sat, May 18, 2019 at 2:56 PM Nirothipan Megalingham <
>>> nirothi...@wso2.com> wrote:
>>>
 Hi all,

 I've tested the following in Ubuntu 18.04 and found no blocker issues
 while testing.

- Deploying sample composite applications in ESB server and Micro
Integrator.
- Listing the artifacts deployed in Micro Integrator via CLI.
- Switch Mediator created in Integration Studio and Management
Console.
- Simple Scheduled Tasks.
- ESB as JMS Producer and Consumer with WSO2 MB.

 +1 for the release.

 Thanks
 Nirothipan


 On Sat, May 18, 2019 at 10:56 AM Kesavan Yogarajah 
 wrote:

> Hi All,
>
> I tested the following, and no issues found.
>
>- Salesforce Connector
>- Salesforce custom inbound Endpoint
>- Script mediator
>
>
> [+] Stable - go ahead and release
>
> Thanks
> Kesavan
>
> Kesavan Yogarajah
> Software Engineer
> Mobile :+94 (0) 779 758021
> kesav...@wso2.com
> WSO2, Inc.
> lean . enterprise . middleware
>
>
> On Fri, May 17, 2019 at 11:15 PM Mathuriga Thavarajah <
> mathur...@wso2.com> wrote:
>
>> Hi All,
>>
>> Security Scanning reports (Static and Dynamic) were analyzed and
>> reviewed. Hence +1 from the Platform Security Team for proceeding with 
>> the
>> release.
>>
>> Thanks.
>>
>> Regards,
>> Mathuriga.
>>
>> On Fri, May 17, 2019 at 7:06 PM Chanika Geeganage 
>> wrote:
>>
>>> Hi All,
>>>
>>> I tested following scenarios ( artifacts were created using both
>>> management console and integration studio).
>>> 1. Call Template
>>> 2. Adding a datasource
>>> 3. Generating a dataservice form the datasource
>>> 4. Creating a dataservice and uploading a dataservice
>>> 5. Tested sample dataservices
>>> 6. Odata
>>>
>>> [+] Stable - go ahead and release
>>>
>>> On Thu, May 16, 2019 at 7:33 PM Nirothipan Megalingham <
>>> nirothi...@wso2.com> wrote:
>>>
 Hi all,

 We are pleased to announce the first release candidate of WSO2
 Enterprise Integrator 6.5.0.

 Please find the list of tasks / bug fixes and improvements shipped
 with this release below

- Tasks/bug fixes and improvements in Enterprise Integrator

 
- Tasks/bug fixes and improvements in Micro Integrator

 

 Known Issues

- https://github.com/wso2/product-ei/issues
- https://github.com/wso2/micro-integrator/issues

 The tag to be voted upon:
 https://github.com/wso2/product-ei/tree/v6.5.0-rc1

 Source and binary distributions:
 https://github.com/wso2/product-ei/releases/tag/v6.5.0-rc1

 Please test and vote as follows

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

 You may find the official documentation in:
 https://docs.wso2.com/display/EI6xx

 ~ 

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

[Vihanga Liyanage]

HI All,

Tested below scenarios on IS 5.8.0-RC3 pack using MySQL 5.7 database.

   - Configured secondary JDBC userstore, listed users, added users,
   modified users and deleted users.
   - Add service provider, configured SAML SSO, authenticate with *the
   dispatch *sample web app.
   - Enable SAML2 Artifact binding and authenticate.
   - Add new SP with Open ID OAuth/OpenID Connect Configuration and
   authenticate with *the playground *sample web app. Tested all OAuth
   grand types.

No blocking issues found.

[+] Stable - Go ahead and release

Best regards,
Vihanga.

On Wed, May 22, 2019 at 9:11 PM Kanapriya Kuleswararajan 
wrote:

> Hi All,
> Resend the vote as I couldn't find my name in the archive.
>
> Tested the following and It works fine.
>
> - Basic functionality with EmailOTP (Basic authenticator/Federated
> Authenticator as first step and EmailOTP as the second step)
> - EmailOTP with Email Templates
> - TOTP with basic functionality
> - X509 with basic functionality
> - Tried EmailOTP/TOTP with secondary user stores.
>
> [+1] Stable - go ahead and release
>
>
> Kanapriya Kuleswararajan
> Senior Software Engineer
> Mobile : - 0774894438
> Mail : - kanapr...@wso2.com
> LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/
> WSO2, Inc.
> lean . enterprise . middleware
>
>
>
> On Wed, May 22, 2019 at 7:46 PM Hasanthi Purnima Dissanayake <
> hasan...@wso2.com> wrote:
>
>> Hi All,
>>
>> We had an issue receiving the replies to this thread and seems some of
>> the replies have lost due to this. Hence if you have sent a vote and it is
>> not available in the archive [1] please re-send the vote. All the votes we
>> received are positive once, so we are planing to close the vote with in few
>> hours. If you have any concerns please raise ASAP.
>>
>> [1] https://wso2.markmail.org/thread/xuyn7ilrts2xvdsn
>>
>> Thanks,
>> Hasanthi
>>
>> On Wed, May 22, 2019 at 5:15 PM Hasanthi Purnima Dissanayake <
>> hasan...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> I have tested following features.
>>>
>>>1. OIDC backchannel logout
>>>2. SAML front channel logout.
>>>
>>> No blocking issues found.
>>>
>>> [+] Stable - go ahead and release.
>>>
>>> Thanks,
>>> Hasanthi
>>>
>>>
>>>
>>> On Wed, May 22, 2019 at 8:03 AM Isuranga Perera 
>>> wrote:
>>>
 All:
 I have tested Federated Authentication
 [+] Stable - go ahead and release.

 Best Regards
 Isuranga Perera

 On Sun, May 19, 2019 at 7:30 PM Shanika Wickramasinghe <
 shani...@wso2.com> wrote:

> Hi All,
>
> I have tested the SAML SSO with POST binding and Redirect binding
> flows and no issues found.
>
> +1 Go Ahead and Release
>
>
> Thanks,
>
> Shanika
>
> On Thu, May 16, 2019 at 12:33 PM Hasanthi Purnima Dissanayake <
> hasan...@wso2.com> wrote:
>
>> Hi All,
>>
>> The reason of breaking the RC2 vote is because it is reported an
>> unused commented configuration description in carbon.xml [1]. From RC3
>> release that commented line in the configuration file is removed and no
>> other code level changes done.
>>
>> Further in the Analytics-IS pack, the versions are updated according
>> to the latest released SP pack versions [2].
>>
>> [1] [Dev][VOTE] Release WSO2 Identity Server 5.8.0 RC2
>> [2] [VOTE] Release of WSO2 Stream Processor 4.4.0 RC6
>>
>> Thanks,
>> Hasanthi
>>
>> On Thu, May 16, 2019 at 12:30 PM Hasanthi Purnima Dissanayake <
>> hasan...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> We are pleased to announce the third release candidate of WSO2
>>> Identity Server 5.8.0.
>>>
>>> This release fixes the following issues,
>>>
>>>- 5.8.0-RC3 fixes
>>>
>>>- 5.8.0-RC2 fixes
>>>
>>>- 5.8.0-RC1 fixes
>>>
>>>- 5.8.0-Beta5 fixes
>>>
>>>- 5.8.0-Beta4 fixes
>>>
>>>- 5.8.0-Beta3 fixes
>>>
>>>- 5.8.0-Beta fixes
>>>
>>>- 5.8.0-Alpha5 fixes
>>>
>>>- 5.8.0-Alpha4 fixes
>>>
>>>- 5.8.0-Alpha3 fixes
>>>
>>>- 5.8.0-Alpha2 fixes
>>>
>>>- 5.8.0-Alpha fixes
>>>
>>>- 5.8.0-M26 fixes
>>

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

[Sarubi Thillainathan]

Hi All,

I have tested the following use cases.
1. Username recovery with reCaptcha
2. Password recovery with reCaptcha

   - Email
   - challenge question based

3. All supported SCIM2  /Users, /Groups and /Me endpoints, tested in
primary user-store and JDBC as secondary user store.

[+] Stable - go ahead and release.


On Wed, May 22, 2019 at 9:11 PM Kanapriya Kuleswararajan 
wrote:

> Hi All,
> Resend the vote as I couldn't find my name in the archive.
>
> Tested the following and It works fine.
>
> - Basic functionality with EmailOTP (Basic authenticator/Federated
> Authenticator as first step and EmailOTP as the second step)
> - EmailOTP with Email Templates
> - TOTP with basic functionality
> - X509 with basic functionality
> - Tried EmailOTP/TOTP with secondary user stores.
>
> [+1] Stable - go ahead and release
>
>
> Kanapriya Kuleswararajan
> Senior Software Engineer
> Mobile : - 0774894438
> Mail : - kanapr...@wso2.com
> LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/
> WSO2, Inc.
> lean . enterprise . middleware
>
>
>
> On Wed, May 22, 2019 at 7:46 PM Hasanthi Purnima Dissanayake <
> hasan...@wso2.com> wrote:
>
>> Hi All,
>>
>> We had an issue receiving the replies to this thread and seems some of
>> the replies have lost due to this. Hence if you have sent a vote and it is
>> not available in the archive [1] please re-send the vote. All the votes we
>> received are positive once, so we are planing to close the vote with in few
>> hours. If you have any concerns please raise ASAP.
>>
>> [1] https://wso2.markmail.org/thread/xuyn7ilrts2xvdsn
>>
>> Thanks,
>> Hasanthi
>>
>> On Wed, May 22, 2019 at 5:15 PM Hasanthi Purnima Dissanayake <
>> hasan...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> I have tested following features.
>>>
>>>1. OIDC backchannel logout
>>>2. SAML front channel logout.
>>>
>>> No blocking issues found.
>>>
>>> [+] Stable - go ahead and release.
>>>
>>> Thanks,
>>> Hasanthi
>>>
>>>
>>>
>>> On Wed, May 22, 2019 at 8:03 AM Isuranga Perera 
>>> wrote:
>>>
 All:
 I have tested Federated Authentication
 [+] Stable - go ahead and release.

 Best Regards
 Isuranga Perera

 On Sun, May 19, 2019 at 7:30 PM Shanika Wickramasinghe <
 shani...@wso2.com> wrote:

> Hi All,
>
> I have tested the SAML SSO with POST binding and Redirect binding
> flows and no issues found.
>
> +1 Go Ahead and Release
>
>
> Thanks,
>
> Shanika
>
> On Thu, May 16, 2019 at 12:33 PM Hasanthi Purnima Dissanayake <
> hasan...@wso2.com> wrote:
>
>> Hi All,
>>
>> The reason of breaking the RC2 vote is because it is reported an
>> unused commented configuration description in carbon.xml [1]. From RC3
>> release that commented line in the configuration file is removed and no
>> other code level changes done.
>>
>> Further in the Analytics-IS pack, the versions are updated according
>> to the latest released SP pack versions [2].
>>
>> [1] [Dev][VOTE] Release WSO2 Identity Server 5.8.0 RC2
>> [2] [VOTE] Release of WSO2 Stream Processor 4.4.0 RC6
>>
>> Thanks,
>> Hasanthi
>>
>> On Thu, May 16, 2019 at 12:30 PM Hasanthi Purnima Dissanayake <
>> hasan...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> We are pleased to announce the third release candidate of WSO2
>>> Identity Server 5.8.0.
>>>
>>> This release fixes the following issues,
>>>
>>>- 5.8.0-RC3 fixes
>>>
>>>- 5.8.0-RC2 fixes
>>>
>>>- 5.8.0-RC1 fixes
>>>
>>>- 5.8.0-Beta5 fixes
>>>
>>>- 5.8.0-Beta4 fixes
>>>
>>>- 5.8.0-Beta3 fixes
>>>
>>>- 5.8.0-Beta fixes
>>>
>>>- 5.8.0-Alpha5 fixes
>>>
>>>- 5.8.0-Alpha4 fixes
>>>
>>>- 5.8.0-Alpha3 fixes
>>>
>>>- 5.8.0-Alpha2 fixes
>>>
>>>- 5.8.0-Alpha fixes
>>>
>>>- 5.8.0-M26 fixes
>>>
>>>- 5.8.0-M25 fixes
>>>
>>>- 5.8.0-M24 fixes
>>>

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

[Malithi Edirisinghe]

Hi All,

Tested following flows and no issues found

   - UMA basic flow
   - OIDC hybrid flow

[+] Stable - go ahead and release.

Thanks,
Malithi

On Wed, May 22, 2019 at 9:56 PM Isura Karunaratne  wrote:

> Hi all,
>
> Tested following features and no issues found.
>
>- Self User Registration
>- Password Policy
>- Password History
>- Password Recovery
>- Account Locking
>
> [+] Stable - go ahead and release.
>
> Cheers,
> Isura.
>
> On Wed, May 22, 2019 at 8:07 PM Farasath Ahamed 
> wrote:
>
>> Hi All,
>>
>> Test the below scenarios in IS 5.8.0 RC3 pack.
>>
>>- Token revocation with authorization code reuse
>>- OIDC UserInfo with token sent in the request body and as bearer
>>header
>>- OAuth Application Owner update
>>- Verified no username enumeration attacks possible during password
>>recovery flows.
>>
>>
>> [+] Stable - go ahead and release.
>>
>>
>> Regards,
>> Farasath
>>
>> On Wed, May 22, 2019 at 5:41 PM Hasanthi Purnima Dissanayake <
>> hasan...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> I have tested following features.
>>>
>>>1. OIDC backchannel logout
>>>2. SAML front channel logout.
>>>
>>> No blocking issues found.
>>>
>>> [+] Stable - go ahead and release.
>>>
>>> Thanks,
>>> Hasanthi
>>>
>>>
>>>
>>> On Wed, May 22, 2019 at 8:03 AM Isuranga Perera 
>>> wrote:
>>>
 All:
 I have tested Federated Authentication
 [+] Stable - go ahead and release.

 Best Regards
 Isuranga Perera

 On Sun, May 19, 2019 at 7:30 PM Shanika Wickramasinghe <
 shani...@wso2.com> wrote:

> Hi All,
>
> I have tested the SAML SSO with POST binding and Redirect binding
> flows and no issues found.
>
> +1 Go Ahead and Release
>
>
> Thanks,
>
> Shanika
>
> On Thu, May 16, 2019 at 12:33 PM Hasanthi Purnima Dissanayake <
> hasan...@wso2.com> wrote:
>
>> Hi All,
>>
>> The reason of breaking the RC2 vote is because it is reported an
>> unused commented configuration description in carbon.xml [1]. From RC3
>> release that commented line in the configuration file is removed and no
>> other code level changes done.
>>
>> Further in the Analytics-IS pack, the versions are updated according
>> to the latest released SP pack versions [2].
>>
>> [1] [Dev][VOTE] Release WSO2 Identity Server 5.8.0 RC2
>> [2] [VOTE] Release of WSO2 Stream Processor 4.4.0 RC6
>>
>> Thanks,
>> Hasanthi
>>
>> On Thu, May 16, 2019 at 12:30 PM Hasanthi Purnima Dissanayake <
>> hasan...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> We are pleased to announce the third release candidate of WSO2
>>> Identity Server 5.8.0.
>>>
>>> This release fixes the following issues,
>>>
>>>- 5.8.0-RC3 fixes
>>>
>>>- 5.8.0-RC2 fixes
>>>
>>>- 5.8.0-RC1 fixes
>>>
>>>- 5.8.0-Beta5 fixes
>>>
>>>- 5.8.0-Beta4 fixes
>>>
>>>- 5.8.0-Beta3 fixes
>>>
>>>- 5.8.0-Beta fixes
>>>
>>>- 5.8.0-Alpha5 fixes
>>>
>>>- 5.8.0-Alpha4 fixes
>>>
>>>- 5.8.0-Alpha3 fixes
>>>
>>>- 5.8.0-Alpha2 fixes
>>>
>>>- 5.8.0-Alpha fixes
>>>
>>>- 5.8.0-M26 fixes
>>>
>>>- 5.8.0-M25 fixes
>>>
>>>- 5.8.0-M24 fixes
>>>
>>>- 5.8.0-M6 fixes
>>>
>>>- 5.8.0-M5 fixes
>>>
>>>- 5.8.0-M4 fixes
>>>
>>>- 5.8.0-M3 fixes
>>>
>>>- 5.8.0-M2 fixes
>>>
>>>- 5.8.0-M1 fixes
>>>
>>>
>>>
>>> Source and distribution
>>>
>>> Runtime - https://gith

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

[Malithi Edirisinghe]

Hi All,

Thanks for testing WSO2 Identity Server 5.8.0-RC3.
Since this vote has passed with 20+ +1s and 0 -1s, we’re hereby closing
this vote and proceeding with the WSO2 Identity Server 5.8.0 GA release.

Best Regards,
- WSO2 Identity Server Team -

On Wed, May 22, 2019 at 10:17 PM Thanuja Jayasinghe 
wrote:

> Hi All,
>
> Tested following scenarios,
>
> - Local user account association
> - OAuth2 grat types (code, implicit, password, client credential)
> - SAML2 SSO & SLO
>
> [+] Stable - go ahead and release.
>
> Thanks,
> Thanuja
>
> On Wed, May 22, 2019 at 8:07 PM Farasath Ahamed 
> wrote:
>
>> Hi All,
>>
>> Test the below scenarios in IS 5.8.0 RC3 pack.
>>
>>- Token revocation with authorization code reuse
>>- OIDC UserInfo with token sent in the request body and as bearer
>>header
>>- OAuth Application Owner update
>>- Verified no username enumeration attacks possible during password
>>recovery flows.
>>
>>
>> [+] Stable - go ahead and release.
>>
>>
>> Regards,
>> Farasath
>>
>> On Wed, May 22, 2019 at 5:41 PM Hasanthi Purnima Dissanayake <
>> hasan...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> I have tested following features.
>>>
>>>1. OIDC backchannel logout
>>>2. SAML front channel logout.
>>>
>>> No blocking issues found.
>>>
>>> [+] Stable - go ahead and release.
>>>
>>> Thanks,
>>> Hasanthi
>>>
>>>
>>>
>>> On Wed, May 22, 2019 at 8:03 AM Isuranga Perera 
>>> wrote:
>>>
 All:
 I have tested Federated Authentication
 [+] Stable - go ahead and release.

 Best Regards
 Isuranga Perera

 On Sun, May 19, 2019 at 7:30 PM Shanika Wickramasinghe <
 shani...@wso2.com> wrote:

> Hi All,
>
> I have tested the SAML SSO with POST binding and Redirect binding
> flows and no issues found.
>
> +1 Go Ahead and Release
>
>
> Thanks,
>
> Shanika
>
> On Thu, May 16, 2019 at 12:33 PM Hasanthi Purnima Dissanayake <
> hasan...@wso2.com> wrote:
>
>> Hi All,
>>
>> The reason of breaking the RC2 vote is because it is reported an
>> unused commented configuration description in carbon.xml [1]. From RC3
>> release that commented line in the configuration file is removed and no
>> other code level changes done.
>>
>> Further in the Analytics-IS pack, the versions are updated according
>> to the latest released SP pack versions [2].
>>
>> [1] [Dev][VOTE] Release WSO2 Identity Server 5.8.0 RC2
>> [2] [VOTE] Release of WSO2 Stream Processor 4.4.0 RC6
>>
>> Thanks,
>> Hasanthi
>>
>> On Thu, May 16, 2019 at 12:30 PM Hasanthi Purnima Dissanayake <
>> hasan...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> We are pleased to announce the third release candidate of WSO2
>>> Identity Server 5.8.0.
>>>
>>> This release fixes the following issues,
>>>
>>>- 5.8.0-RC3 fixes
>>>
>>>- 5.8.0-RC2 fixes
>>>
>>>- 5.8.0-RC1 fixes
>>>
>>>- 5.8.0-Beta5 fixes
>>>
>>>- 5.8.0-Beta4 fixes
>>>
>>>- 5.8.0-Beta3 fixes
>>>
>>>- 5.8.0-Beta fixes
>>>
>>>- 5.8.0-Alpha5 fixes
>>>
>>>- 5.8.0-Alpha4 fixes
>>>
>>>- 5.8.0-Alpha3 fixes
>>>
>>>- 5.8.0-Alpha2 fixes
>>>
>>>- 5.8.0-Alpha fixes
>>>
>>>- 5.8.0-M26 fixes
>>>
>>>- 5.8.0-M25 fixes
>>>
>>>- 5.8.0-M24 fixes
>>>
>>>- 5.8.0-M6 fixes
>>>
>>>- 5.8.0-M5 fixes
>>>
>>>- 5.8.0-M4 fixes
>>>
>>>- 5.8.0-M3 fixes
>>>
>>>- 5.8.0-M2 fixes
>>>
>>>- 5.8.0-M1 fixes
>>>
>>

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

[Omindu Rathnaweera]

Hi All,

Did a few basic tests covering the functionalities around OIDC, SAML and
Consent Management.

[+] Stable - go ahead and release

Thanks,
Omindu.

On Wed, May 22, 2019 at 10:17 PM Thanuja Jayasinghe 
wrote:

> Hi All,
>
> Tested following scenarios,
>
> - Local user account association
> - OAuth2 grat types (code, implicit, password, client credential)
> - SAML2 SSO & SLO
>
> [+] Stable - go ahead and release.
>
> Thanks,
> Thanuja
>
> On Wed, May 22, 2019 at 8:07 PM Farasath Ahamed 
> wrote:
>
>> Hi All,
>>
>> Test the below scenarios in IS 5.8.0 RC3 pack.
>>
>>- Token revocation with authorization code reuse
>>- OIDC UserInfo with token sent in the request body and as bearer
>>header
>>- OAuth Application Owner update
>>- Verified no username enumeration attacks possible during password
>>recovery flows.
>>
>>
>> [+] Stable - go ahead and release.
>>
>>
>> Regards,
>> Farasath
>>
>> On Wed, May 22, 2019 at 5:41 PM Hasanthi Purnima Dissanayake <
>> hasan...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> I have tested following features.
>>>
>>>1. OIDC backchannel logout
>>>2. SAML front channel logout.
>>>
>>> No blocking issues found.
>>>
>>> [+] Stable - go ahead and release.
>>>
>>> Thanks,
>>> Hasanthi
>>>
>>>
>>>
>>> On Wed, May 22, 2019 at 8:03 AM Isuranga Perera 
>>> wrote:
>>>
 All:
 I have tested Federated Authentication
 [+] Stable - go ahead and release.

 Best Regards
 Isuranga Perera

 On Sun, May 19, 2019 at 7:30 PM Shanika Wickramasinghe <
 shani...@wso2.com> wrote:

> Hi All,
>
> I have tested the SAML SSO with POST binding and Redirect binding
> flows and no issues found.
>
> +1 Go Ahead and Release
>
>
> Thanks,
>
> Shanika
>
> On Thu, May 16, 2019 at 12:33 PM Hasanthi Purnima Dissanayake <
> hasan...@wso2.com> wrote:
>
>> Hi All,
>>
>> The reason of breaking the RC2 vote is because it is reported an
>> unused commented configuration description in carbon.xml [1]. From RC3
>> release that commented line in the configuration file is removed and no
>> other code level changes done.
>>
>> Further in the Analytics-IS pack, the versions are updated according
>> to the latest released SP pack versions [2].
>>
>> [1] [Dev][VOTE] Release WSO2 Identity Server 5.8.0 RC2
>> [2] [VOTE] Release of WSO2 Stream Processor 4.4.0 RC6
>>
>> Thanks,
>> Hasanthi
>>
>> On Thu, May 16, 2019 at 12:30 PM Hasanthi Purnima Dissanayake <
>> hasan...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> We are pleased to announce the third release candidate of WSO2
>>> Identity Server 5.8.0.
>>>
>>> This release fixes the following issues,
>>>
>>>- 5.8.0-RC3 fixes
>>>
>>>- 5.8.0-RC2 fixes
>>>
>>>- 5.8.0-RC1 fixes
>>>
>>>- 5.8.0-Beta5 fixes
>>>
>>>- 5.8.0-Beta4 fixes
>>>
>>>- 5.8.0-Beta3 fixes
>>>
>>>- 5.8.0-Beta fixes
>>>
>>>- 5.8.0-Alpha5 fixes
>>>
>>>- 5.8.0-Alpha4 fixes
>>>
>>>- 5.8.0-Alpha3 fixes
>>>
>>>- 5.8.0-Alpha2 fixes
>>>
>>>- 5.8.0-Alpha fixes
>>>
>>>- 5.8.0-M26 fixes
>>>
>>>- 5.8.0-M25 fixes
>>>
>>>- 5.8.0-M24 fixes
>>>
>>>- 5.8.0-M6 fixes
>>>
>>>- 5.8.0-M5 fixes
>>>
>>>- 5.8.0-M4 fixes
>>>
>>>- 5.8.0-M3 fixes
>>>
>>>- 5.8.0-M2 fixes
>>>
>>>- 5.8.0-M1 fixes
>>>
>>>
>>>
>>> Source and distribution
>>>
>>> Runtime - https://github.com/wso2/

Re: [Architecture] Open Policy Agent Authorization handler for WSO2 IS

[Shammi Jayasinghe]

Hi Nirubikka,

With this handler implementation, Are you planing to implement the UI for
configuring policy as we have for xacml in [1] as well?
What is the IS version we are planing add this?

[1] https://docs.wso2.com/display/IS570/Creating+a+XACML+Policy
Thanks
shammi

On Wed, May 15, 2019 at 10:50 PM Nilasini Thirunavukkarasu <
nilas...@wso2.com> wrote:

> Hi,
>
> After analyzing online resources[1][2] and offline discussion with @Maduranga
> Siriwardena  could able to get the answers for the
> questions I have asked.
>
>- OPA is flexible, easy to use and maintainable so people tend to use OPA
>to write and make decisions hence we need to provide the capability to
>use OPA if someone needs.
>- At the same time, some people still will be using XACML hence we
>will be keeping both XACML and OPA.
>
> [1] https://www.infoq.com/news/2019/04/open-policy-agent-cncf
> [2]
> https://www.openpolicyagent.org/docs/latest/comparison-to-other-systems
>
> Thanks,
> Nila.
>
>
>
> On Wed, May 15, 2019 at 11:46 AM Nilasini Thirunavukkarasu <
> nilas...@wso2.com> wrote:
>
>> Hi Nirubikaa,
>>
>> On Wed, May 15, 2019 at 11:32 AM Nirubikaa Ravikumar 
>> wrote:
>>
>>> Hi all,
>>>
>>>
>>>
>>> I am working on implementing an Open Policy Agent(OPA) authorization
>>> handler for WSO2 Identity Server.
>>>
>>>
>>> OPA is a lightweight general-purpose policy engine. Policies in OPA are
>>> written in a high-level declarative language. You can find more information
>>> about OPA from [1].
>>>
>>>
>>> The main Idea of this Authorization handler is to authorize a user based
>>> on the policy which is stored at the OPA server, similar to what we already
>>> do with XACML.
>>>
>>
>> According to the shared diagram, AFAIU OPA server will evaluate the
>> policy and sends the decision to IS. But we already have a XACML engine to
>> do the same job. In that case, could you please explain more on what is the
>> specific reason for implementing an OPA even though we already have XACML
>> engine to evaluate the policies?. Once we implement the OPA are we planning
>> to deprecate XAML engine?
>>
>> Thanks,
>> Nila.
>>
>>
>>> [1] https://www.openpolicyagent.org/docs/latest
>>>
>>>
>>>
>>> Please find the flow Diagram attached to this email.
>>>
>>>
>>>
>>>
>>> Thanks,
>>>
>>>
>>> --
>>> R.Nirubikaa
>>> Software Engineering Intern | WSO2
>>> M: O779108852
>>>
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "IAM team" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to iam-group+unsubscr...@wso2.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/a/wso2.com/d/msgid/iam-group/CA%2BP04X9vN_8m-ZELn8wVpxK8ZdZXjsqKeGdGMozcYCcaKLnQ4A%40mail.gmail.com
>>> 
>>> .
>>>
>>
>>
>> --
>> Nilasini Thirunavukkarasu
>> Senior Software Engineer - WSO2
>>
>> Email : nilas...@wso2.com
>> Mobile : +94775241823
>> Web : http://wso2.com/
>>
>>
>> 
>>
>
>
> --
> Nilasini Thirunavukkarasu
> Senior Software Engineer - WSO2
>
> Email : nilas...@wso2.com
> Mobile : +94775241823
> Web : http://wso2.com/
>
>
> 
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>


-- 
Best Regards,

*  Shammi Jayasinghe*


*Senior Technical Lead*
*WSO2, Inc.*
*+1-812-391-7730*
*+1-812-327-3505*

*http://shammijayasinghe.blogspot.com
*
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [APIM][Monetization] Monetization Model For WSO2 API Manager

[Shammi Jayasinghe]

Hi,
How we are going to handle failure cases with this plan.

eg:
- for the monthly plan, If the subscriber has not paid or can not be
charged from the CC, Is stripe will send back the call to API M to block
that subscription?
- If the subscriber paid later, how we are going to re-activate

- When it comes to distributed deployments with many nodes with multiple
timezones, EU/APAC/ US,  Are we aggregating the counts per local timezone?
- Hope this call to the count table be asynchronous , Are we implementing
this call as a handler in response path or what is the plan?

Thanks
Shammi


On Wed, May 15, 2019 at 7:21 AM Frank Leymann  wrote:

> Would a discount pricing model make sense? E.g. after x requests you get a
> discount of y%?
>
> And what about adding a QoS aspect: if x requests failed within y
> duration, you get a discount of z% for D duration?
>
> Best regards,
> Frank
>
>
>
>
> Am Mi., 15. Mai 2019 um 08:21 Uhr schrieb Chamin Dias :
>
>> Hi all,
>>
>> Based on the recent discussions we had, we will be going to implement the
>> following features from the products POV. Intention of this email is to
>> give an update on some of the important points.
>>
>> *A) Model : Charge a fixed price for a given time*
>>
>> *1. What we need in the product : *
>> Ability to define the fixed price, frequency and duration for a tier
>> Eg : $25 (price) per 1 (frequency) month (duration)
>>
>> Note : This can be extended as "one time payment" if needed. That means,
>> if we specify something like, "$25 (price) per 100 (frequency) years
>> (duration)" - it will charge $25 per 100 years. Practically a subscription
>> won't last that much of time so this can be considered as one time payment
>> for a tier.
>>
>> *2. What we need in the billing engine : *
>> Ability to define pricing plans with parameters (price, frequency and
>> duration)
>>
>> *3. Benefit / User experience : *
>> Admins will define tiers with using the dashboard.
>> API providers can attach a tier with fixed price (for a given time).
>> Subscribers will pay a fixed amount (per week, month - specified in the
>> tier).
>>
>>
>> *B) Model : Pay as you use*
>>
>> *1. What we need in the product : *
>> i) Ability to define the price per request
>> ii). Aggregate usage daily (via a scheduled / manual task)
>>
>> *2. What we need in the billing engine :*
>> Ability to define pricing plans with 'pay as you use' mode and aggregate
>> or set usage and charge subscribers for the usage.
>>
>> *3. Benefit / User experience : *
>> API providers can attach a tier with 'pay as you use' type. Then, usage
>> will be aggregated daily / or set for each subscriber. At the end of each
>> month, subscriber will be charged for the aggregated usage.
>> API provider will be able to see the revenue from each user of their API.
>>
>> Thanks.
>>
>> On Mon, Apr 8, 2019 at 3:10 PM Chamin Dias  wrote:
>>
>>> Hi Cyril,
>>>
>>> As for the initial implementation, we plan to provide this integration
>>> with stripe but eventually we hope to provide necessary interfaces to
>>> extend. For now, we focus on delivering a workable solution (APIM + Stripe)
>>> for a normal usage based billing scenario.
>>>
>>> Thanks.
>>>
>>> On Fri, Apr 5, 2019 at 3:53 PM Silmy Hasan  wrote:
>>>
 Hi Rukshan,

 Please my answer to your concern below

 *I think we can reuse the existing data. Even though we define
 recording policy, all the possible data is stored in the analytics DBs
 regardless of the recording policy. So we should be able to correlate this
 recording policy with stat data and filter out required data from the
 Billing engine.*

 As discussed offline , I dont think that we can use only the existing
 data without modifying or creating a new Aggregation. If we assume we
 define the recording policy based on the response code , we do not store
 the response code anywhere in Request count Aggregation. So providing the
 successful count based on the response code is impossible without altering
 or creating a new aggregation.

 but we can decide whether we are going to add this to an existing
 aggregation or create a new one.  If we try to  add the above policy to the
 existing aggregations we will have to modify the queries that read the data
 from the aggregation to populate graphs.  Also we will always have to
 modify the queries  , whenever there is a change in the policy (based on
 some user requirement). Also it will compel to store the above data
 irrelevant of whether the monetization is enabled or not , hence i believe
 creating a separate aggregation(create tables internally) can ease lot of
 things in future

 Thanks,
 Silmy.



 On Fri, Apr 5, 2019 at 2:51 PM Rukshan Premathunga 
 wrote:

>
>
> On Fri, Apr 5, 2019 at 2:46 PM Silmy Hasan  wrote:
>
>> Hi Bhathiya,
>>
>> Please find my answers for your concerns,
>>
>>>