Re: [Dev] [VOTE] Release WSO2 Data Analytics Server 3.2.0 RC1

[SajithAR Ariyarathna]

Hi All,

We are closing this vote, we will announce RC2 release soon.

Thanks.

On Thu, Mar 15, 2018 at 11:18 AM, Anusha Jayasundara 
wrote:

> -1 ,
>
> Missing client-truststore.jks file in several samples directories
> including smart-home and apim-stats
>
>
>
> On Thu, Mar 15, 2018 at 3:12 AM, Sajith Perera  wrote:
>
>> Hi Devs,
>>
>> We are pleased to announce the release candidate of WSO2 Data Analytics
>> Server 3.2.0.
>>
>> This is the Release Candidate version 1 of the WSO2 Data Analytics Server
>> 3.2.0
>>
>> Please download, test the product and vote. The vote will be open for 72
>> hours or as needed.
>>
>> Known issues: https://github.com/wso2/product-das/issues
>>
>> Source and binary distribution files: https://github.com/wso2/produc
>> t-das/releases/tag/v3.2.0-RC1
>>
>> The tag to be voted upon: https://github.com/wso2/produc
>> t-das/tree/v3.2.0-RC1
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> ~ The WSO2 Analytics Team ~
>>
>> Thanks.
>> --
>> 
>> Sajith Dimal
>> Software Engineer
>> Email : saji...@wso2.com
>> Mobile : +94783101496
>> WSO2 Inc. | http://wso2.com
>> lean.enterprise.middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Anusha Jayasundara*
> Software Engineer | WSO2
>
> Email : anus...@wso2.com
> Mobile : +94772601160 <+94%2077%20260%201160>
> Web : http://wso2.com
> Lean.Enterprise.Middleware
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sajith Janaprasad Ariyarathna
Senior Software Engineer; WSO2, Inc.;  http://wso2.com/

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

Re: [Dev] Difference between primary and secondary use stores

[Lahiru Sandaruwan]

Hi Randy,

Please find the answers inline,

On Wed, Mar 14, 2018 at 9:45 PM, Randy Adams 
wrote:

> Hi devs,
>
> I have some confusion on user store types in wso2 products. Please give
> some assistance.
>
> What is the difference between primary and secondary user stores in wso2
> products?
>

​Primary userstore​

WSO2 products must have at least one user store. This is the main user
store and it is shared among all the tenants. Please find the more info
from [1]. If you want to learn about tenancy in WSO2 products, read [2]
Also, admin user of the super tenant(default tenent of WSO2 products),
which is defined in [WSO2_Product_Home]/repository/conf/user-mgt.xml will
reside in primary userstore.
Read more about system administrator user at [3].
>From [1],
"This is the main user store that is shared among all the tenants in the
system. Only one user store should be configured as the primary user store"

Secondary userstores

Secondary user stores are helpful when your organization has different
sources of users due to departments, company mergers/ acquisitions etc. So
if you have different tenants, you mount the secondary user stores for each
tenant separately.
Find more details from [1]. Following quote is copied from there for your
reference.
"Any number of secondary user stores can be easily set up for your system
and these user stores are specific to the created tenant, and they are not
shared among multiple tenants."


> What is the exact requirement to have two different types of user stores
> as this? Why isn't it just "user stores" generally?
>

Primary needs to be identified separately for above said functionalities.
​

> What are the different tasks done by these two categories?
>

​Both types have all the functionalities other than above said differences.
I have included IAM team to add to the details provided

[1] https://docs.wso2.com/display/IS541/Configuring+User+Stores
[2] https://docs.wso2.com/display/IS541/Creating+and+Managing+Tenants
[3] https://docs.wso2.com/display/IS541/Configuring+the+System+Administrator

​Thanks.​

>
> Regards,
> Randy
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
--

Lahiru Sandaruwan
WSO2 Inc., http://wso2.com

lean.enterprise.middleware

m: +1 901 530 2379 <+1%20901-530-2379>
e: lahi...@wso2.com b: https://medium.com/@lahirugmg
in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Data Analytics Server 3.2.0 RC1

[Anusha Jayasundara]

-1 ,

Missing client-truststore.jks file in several samples directories including
smart-home and apim-stats



On Thu, Mar 15, 2018 at 3:12 AM, Sajith Perera  wrote:

> Hi Devs,
>
> We are pleased to announce the release candidate of WSO2 Data Analytics
> Server 3.2.0.
>
> This is the Release Candidate version 1 of the WSO2 Data Analytics Server
> 3.2.0
>
> Please download, test the product and vote. The vote will be open for 72
> hours or as needed.
>
> Known issues: https://github.com/wso2/product-das/issues
>
> Source and binary distribution files: https://github.com/wso2/
> product-das/releases/tag/v3.2.0-RC1
>
> The tag to be voted upon: https://github.com/wso2/
> product-das/tree/v3.2.0-RC1
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> ~ The WSO2 Analytics Team ~
>
> Thanks.
> --
> 
> Sajith Dimal
> Software Engineer
> Email : saji...@wso2.com
> Mobile : +94783101496
> WSO2 Inc. | http://wso2.com
> lean.enterprise.middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Anusha Jayasundara*
Software Engineer | WSO2

Email : anus...@wso2.com
Mobile : +94772601160
Web : http://wso2.com
Lean.Enterprise.Middleware

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

Re: [Dev] [Architecture] [VOTE] Release WSO2 Identity Server 5.5.0 RC2

[Denuwanthi De Silva]

Hi,


Tested following scenarios with oauth2 token encryption enabled.


1.client credential grant type.
2.Unauthorized client (Invoke token endpoint with client id of a differnt
grant type)
3.impicit grant type
4.password grant type
5.refresh token grant type
6.authorization code grant type
7.Invoke userinfo endpoint with the token retrieved via authorization code
grant type
8.revoke the token generated from authorization code grant type.

+1 to go ahead and release.


Thanks,



On Thu, Mar 15, 2018 at 10:45 AM, Pushpalanka Jayawardhana 
wrote:

> Hi All,
>
> Tested below scenarios on the RC2 pack,
>
>
>- OIDC Hybrid flow with 'code id_token' response type.
>   - Flow is working fine after copying below configuration in
>   repository/conf/identity/identity.xml file.
>
> 
>>code id_token
>>org.wso2.carbon.identity.
>> oauth2.authz.handlers.HybridResponseTypeHandler> ResponseTypeHandlerImplClass>
>> 
>
>
>- Attaching purposes to PII claims via UI.
>- Get OIDC consent page populated with claims to be shared.
>
> Since no blocking issues found, voting to go ahead and release.
> +1
>
> On Thu, Mar 15, 2018 at 9:59 AM, Dinali Dabarera  wrote:
>
>> Hi All,
>>
>> I tested the Tested Below scenario on the IS 5.5.0-RC2 pack.
>>
>>- DCR for in carbon supper and tenant domain.
>>- Authorization code grant flow using play ground
>>- What happened when an un-ticked flow tried.
>>- Introspection
>>
>>
>> +1 to go ahead with the release
>>
>> On Thu, Mar 15, 2018 at 9:38 AM, Nipuni Bhagya  wrote:
>>
>>> Hi all,
>>>
>>> I tested the IS 5.5.0-RC2 pack with IAM- Quick Start Guide which covers
>>> the following scenarios.
>>>
>>>
>>>- Configuring Single-Sign-On with SAML2
>>>- Configuring Single-Sign-On with OIDC
>>>- Configuring Multi-Factor Authentication (with Twitter as the
>>>second authentication factor.)
>>>- Configuring Twitter as a Federated Authenticator
>>>- Setting up Self-Signup
>>>- Creating a workflow
>>>
>>> +1 to go ahead and release.
>>>
>>>
>>> On Thu, Mar 15, 2018 at 8:16 AM, Nuwandi Wickramasinghe <
>>> nuwan...@wso2.com> wrote:
>>>
 Hi,

 Tested Below scenario on the IS 5.5.0-RC2 pack.

- User creation in primary/secondary user stores.
- Saml service provider creation manually, with metadata file and
with url.
- Entitlement policy creation and publishing.
- Service provider access control using entitlement policy.

 +1 to go ahead and release.

 On Thu, Mar 15, 2018 at 5:19 AM, Darshana Gunawardana <
 darsh...@wso2.com> wrote:

> Hi all,
>
> We are pleased to announce the second release candidate of WSO2
> Identity Server 5.5.0.
>
> This release fixes the following issues,
>
>-
>- 5.5.0-RC2 fixes
>
> 
>- 5.5.0-RC1 fixes
>
> 
>- 5.5.0-Beta fixes
>
> 
>- 5.5.0-Alpha3 fixes
>
> 
>- 5.5.0-Alpha2 fixes
>
> 
>- 5.5.0-Alpha fixes
>
> 
>- 5.5.0-M4 fixes
>
> 
>- 5.5.0-M3 fixes
>
> 
>- 5.5.0-M2 fixes
>
> 
>- 5.5.0-M1 fixes
>
> 
>
>
> Source and distribution
>
> Runtime - https://github.com/wso2/product-is/releases/v5.5.0-rc2
> Analytics - https://github.com/wso2/anal
> ytics-is/releases/v5.5.0-rc2
>
>
> 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 -
>
> --
> Regards,
>
>
> *Darshana Gunawardana*Technical Lead
> WSO2 Inc.; http://wso2.com
>
> *E-mail: darsh...@wso2.com *
> *Mobile: +94718566859 <+94%2071%20856%206859>*Lean . Enterprise .
> Middleware
>



 --

 Best Regards,

 Nuwandi Wickramasinghe

 Senior Software Engineer

 WSO2 Inc.

Re: [Dev] [Architecture] [VOTE] Release WSO2 Identity Server 5.5.0 RC2

[Pushpalanka Jayawardhana]

Hi All,

Tested below scenarios on the RC2 pack,


   - OIDC Hybrid flow with 'code id_token' response type.
  - Flow is working fine after copying below configuration in
  repository/conf/identity/identity.xml file.


>code id_token
>
>  
> org.wso2.carbon.identity.oauth2.authz.handlers.HybridResponseTypeHandler
> 


   - Attaching purposes to PII claims via UI.
   - Get OIDC consent page populated with claims to be shared.

Since no blocking issues found, voting to go ahead and release.
+1

On Thu, Mar 15, 2018 at 9:59 AM, Dinali Dabarera  wrote:

> Hi All,
>
> I tested the Tested Below scenario on the IS 5.5.0-RC2 pack.
>
>- DCR for in carbon supper and tenant domain.
>- Authorization code grant flow using play ground
>- What happened when an un-ticked flow tried.
>- Introspection
>
>
> +1 to go ahead with the release
>
> On Thu, Mar 15, 2018 at 9:38 AM, Nipuni Bhagya  wrote:
>
>> Hi all,
>>
>> I tested the IS 5.5.0-RC2 pack with IAM- Quick Start Guide which covers
>> the following scenarios.
>>
>>
>>- Configuring Single-Sign-On with SAML2
>>- Configuring Single-Sign-On with OIDC
>>- Configuring Multi-Factor Authentication (with Twitter as the second
>>authentication factor.)
>>- Configuring Twitter as a Federated Authenticator
>>- Setting up Self-Signup
>>- Creating a workflow
>>
>> +1 to go ahead and release.
>>
>>
>> On Thu, Mar 15, 2018 at 8:16 AM, Nuwandi Wickramasinghe <
>> nuwan...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> Tested Below scenario on the IS 5.5.0-RC2 pack.
>>>
>>>- User creation in primary/secondary user stores.
>>>- Saml service provider creation manually, with metadata file and
>>>with url.
>>>- Entitlement policy creation and publishing.
>>>- Service provider access control using entitlement policy.
>>>
>>> +1 to go ahead and release.
>>>
>>> On Thu, Mar 15, 2018 at 5:19 AM, Darshana Gunawardana >> > wrote:
>>>
 Hi all,

 We are pleased to announce the second release candidate of WSO2
 Identity Server 5.5.0.

 This release fixes the following issues,

-
- 5.5.0-RC2 fixes

 
- 5.5.0-RC1 fixes

 
- 5.5.0-Beta fixes

 
- 5.5.0-Alpha3 fixes

 
- 5.5.0-Alpha2 fixes

 
- 5.5.0-Alpha fixes

 
- 5.5.0-M4 fixes

 
- 5.5.0-M3 fixes

 
- 5.5.0-M2 fixes

 
- 5.5.0-M1 fixes

 


 Source and distribution

 Runtime - https://github.com/wso2/product-is/releases/v5.5.0-rc2
 Analytics - https://github.com/wso2/anal
 ytics-is/releases/v5.5.0-rc2


 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 -

 --
 Regards,


 *Darshana Gunawardana*Technical Lead
 WSO2 Inc.; http://wso2.com

 *E-mail: darsh...@wso2.com *
 *Mobile: +94718566859 <+94%2071%20856%206859>*Lean . Enterprise .
 Middleware

>>>
>>>
>>>
>>> --
>>>
>>> Best Regards,
>>>
>>> Nuwandi Wickramasinghe
>>>
>>> Senior Software Engineer
>>>
>>> WSO2 Inc.
>>>
>>> Web : http://wso2.com
>>>
>>> Mobile : 0719214873 <071%20921%204873>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>>
>>
>> *Kind Regards,Nipuni Bhagya*
>>
>> *Software Engineering Intern*
>> *WSO2*
>>
>>
>>
>> *Mobile : +94 0779028904 <+94%2077%20767%201807>*
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> *Dinali Rosemin Dabarera*
> Software Engineer
> WSO2 Lanka (pvt) Ltd.
> Web: http://wso2.com/
> Email : gdrdabar...@gmail.com
> LinkedIn 
> Mobile: +94770198933 

Re: [Dev] [ESB 4.8.1] Setting empty JSON array from XSLT mediator

[Lahiru Sandaruwan]

Hi Senduran,

Already tried. Nothing comes out of XSLT with that(even in XML format).

Thanks.

On Wed, Mar 14, 2018 at 9:55 PM, Senduran  wrote:

> Hi Lahiru,
>
> Can you try the following in your XSLT
>
> 
> tokens
> 
>
> Regards
> Senduran
>
> On Thu, Mar 15, 2018 at 3:40 AM, Lahiru Sandaruwan 
> wrote:
>
>> Devs,
>>
>> I'm trying $subject using ESB 4.8.1 and I can only set the payload from
>> XSLT. Let me explain an example below.
>>
>> I'm expecting the JSON result as,
>> *{*
>> * "name": "lahiru",*
>> * "tokens": []*
>> *}*
>>
>> Tried setting following from XSLT,
>> *...*
>>
>> **
>> **
>> **
>> *...*
>>
>> It outputs XML,
>>
>> **
>>
>> *lahiru*
>>
>> **
>> **
>>
>> **
>>
>> And it is converted to following which is not the disired,
>> *{*
>> * "name": "lahiru",*
>> * "tokens": [*
>>
>> *""*
>>
>> *]*
>>
>> *}*
>>
>> If I could set XML node as ** from XSLT, it would
>> work. But it seems there is no way to set such node.
>>
>> Any idea on how I can get this done?
>>
>> Thanks.
>>
>> --
>> --
>>
>> Lahiru Sandaruwan
>> WSO2 Inc., http://wso2.com
>>
>> lean.enterprise.middleware
>>
>> m: +1 901 530 2379 <+1%20901-530-2379>
>> e: lahi...@wso2.com b: https://medium.com/@lahirugmg
>> in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
--

Lahiru Sandaruwan
WSO2 Inc., http://wso2.com

lean.enterprise.middleware

m: +1 901 530 2379
e: lahi...@wso2.com b: https://medium.com/@lahirugmg
in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 Identity Server 5.5.0 RC2

[Dinali Dabarera]

Hi All,

I tested the Tested Below scenario on the IS 5.5.0-RC2 pack.

   - DCR for in carbon supper and tenant domain.
   - Authorization code grant flow using play ground
   - What happened when an un-ticked flow tried.
   - Introspection


+1 to go ahead with the release

On Thu, Mar 15, 2018 at 9:38 AM, Nipuni Bhagya  wrote:

> Hi all,
>
> I tested the IS 5.5.0-RC2 pack with IAM- Quick Start Guide which covers
> the following scenarios.
>
>
>- Configuring Single-Sign-On with SAML2
>- Configuring Single-Sign-On with OIDC
>- Configuring Multi-Factor Authentication (with Twitter as the second
>authentication factor.)
>- Configuring Twitter as a Federated Authenticator
>- Setting up Self-Signup
>- Creating a workflow
>
> +1 to go ahead and release.
>
>
> On Thu, Mar 15, 2018 at 8:16 AM, Nuwandi Wickramasinghe  > wrote:
>
>> Hi,
>>
>> Tested Below scenario on the IS 5.5.0-RC2 pack.
>>
>>- User creation in primary/secondary user stores.
>>- Saml service provider creation manually, with metadata file and
>>with url.
>>- Entitlement policy creation and publishing.
>>- Service provider access control using entitlement policy.
>>
>> +1 to go ahead and release.
>>
>> On Thu, Mar 15, 2018 at 5:19 AM, Darshana Gunawardana 
>> wrote:
>>
>>> Hi all,
>>>
>>> We are pleased to announce the second release candidate of WSO2 Identity
>>> Server 5.5.0.
>>>
>>> This release fixes the following issues,
>>>
>>>-
>>>- 5.5.0-RC2 fixes
>>>
>>> 
>>>- 5.5.0-RC1 fixes
>>>
>>> 
>>>- 5.5.0-Beta fixes
>>>
>>> 
>>>- 5.5.0-Alpha3 fixes
>>>
>>> 
>>>- 5.5.0-Alpha2 fixes
>>>
>>> 
>>>- 5.5.0-Alpha fixes
>>>
>>> 
>>>- 5.5.0-M4 fixes
>>>
>>> 
>>>- 5.5.0-M3 fixes
>>>
>>> 
>>>- 5.5.0-M2 fixes
>>>
>>> 
>>>- 5.5.0-M1 fixes
>>>
>>> 
>>>
>>>
>>> Source and distribution
>>>
>>> Runtime - https://github.com/wso2/product-is/releases/v5.5.0-rc2
>>> Analytics - https://github.com/wso2/analytics-is/releases/v5.5.0-rc2
>>>
>>>
>>> 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 -
>>>
>>> --
>>> Regards,
>>>
>>>
>>> *Darshana Gunawardana*Technical Lead
>>> WSO2 Inc.; http://wso2.com
>>>
>>> *E-mail: darsh...@wso2.com *
>>> *Mobile: +94718566859 <+94%2071%20856%206859>*Lean . Enterprise .
>>> Middleware
>>>
>>
>>
>>
>> --
>>
>> Best Regards,
>>
>> Nuwandi Wickramasinghe
>>
>> Senior Software Engineer
>>
>> WSO2 Inc.
>>
>> Web : http://wso2.com
>>
>> Mobile : 0719214873
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
>
>
> *Kind Regards,Nipuni Bhagya*
>
> *Software Engineering Intern*
> *WSO2*
>
>
>
> *Mobile : +94 0779028904 <+94%2077%20767%201807>*
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
*Dinali Rosemin Dabarera*
Software Engineer
WSO2 Lanka (pvt) Ltd.
Web: http://wso2.com/
Email : gdrdabar...@gmail.com
LinkedIn 
Mobile: +94770198933





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

Re: [Dev] [Architecture] [VOTE] Release WSO2 Stream Processor 4.1.0 RC1

[SajithAR Ariyarathna]

Hi All,

We are calling off this vote. We will do a RC2 release soon.

Thanks.

On Thu, Mar 15, 2018 at 8:54 AM, Sriskandarajah Suhothayan 
wrote:

> -1
> In Mac, the graphics of the editor event flow is not rendering correctly.
>
> Please check the attached image.
>
> On Thu, Mar 15, 2018 at 12:46 AM, Damith Wickramasinghe 
> wrote:
>
>> - sup dev
>> + dev
>>
>> On Thu, Mar 15, 2018 at 12:05 AM, Damith Wickramasinghe > > wrote:
>>
>>> Hi Devs,
>>>
>>> We are pleased to announce the release candidate of WSO2 Stream
>>> Processor 4.1.0.
>>>
>>> This is the Release Candidate version 1 of the WSO2 Stream Processor 4.1
>>> .0
>>>
>>> Please download, test the product and vote. Vote will be open for 72
>>> hours or as needed.
>>>
>>> Known issues: https://github.com/wso2/product-sp/issues
>>>
>>> Source and binary distribution files: https://github.com/wso2/produc
>>> t-sp/releases/tag/v4.1.0-RC1
>>>
>>> The tag to be voted upon: https://github.com/wso2/product-sp/tree/v4.1.0
>>> -RC1
>>>
>>> Please vote as follows.
>>> [+] Stable - go ahead and release
>>> [-] Broken - do not release (explain why)
>>>
>>> ~ The WSO2 Analytics Team ~
>>> Thanks.
>>>
>>>
>>> --
>>> Senior Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> 
>>> lean.enterprise.middleware
>>>
>>> mobile: *+94728671315 <+94%2072%20867%201315>*
>>>
>>>
>>
>>
>> --
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> 
>> lean.enterprise.middleware
>>
>> mobile: *+94728671315 <072%20867%201315>*
>>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
>
> *S. Suhothayan*
> Director
> *WSO2 Inc. *
> http://wso2.com  
>
>
> *cell: (+94) 779 756 757 <+94%2077%20975%206757> | blog:
> http://suhothayan.blogspot.com/ twitter:
> http://twitter.com/suhothayan  | linked-in:
> http://lk.linkedin.com/in/suhothayan *
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Sajith Janaprasad Ariyarathna
Senior Software Engineer; WSO2, Inc.;  http://wso2.com/

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

Re: [Dev] Access to the WSO2 BPS registry from a Activiti TaskListener

[Vinod Kavinda]

Hi Thomas,
Inside the listener, you do not have the direct assess to the registry. You
will have to write a Wso2 registry client in order to access the registry
resources. Look for different types of clients you can implement. [1] is
one such sample.

[1] - https://docs.wso2.com/display/Governance460/WS-API+Sample

Thanks,
Vinod

On Thu, Mar 8, 2018 at 8:42 PM, Thomas LEGRAND  wrote:

> Hello,
>
> I implemented a TaskListener used by some user task in my process when
> they are completed. However, I need to access to some configuration
> properties that I would like to add in the BPS registry. Is there a way to
> access to the registry from a TaskListener?
>
> Regards,
>
> Thomas
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Vinod Kavinda
Senior Software Engineer
*WSO2 Inc. - lean . enterprise . middleware .*
Mobile : +94 (0) 712 415544
Blog : http://soatechflicks.blogspot.com/
[image: http://wso2.com/signature]

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

Re: [Dev] [Architecture] [VOTE] Release WSO2 IoT Server 3.3.0 RC1

[Charitha Goonetilleke]

Hi Devs,

I have tested following scenarios with RC1.

   - Android Functionalities
  - Enroll Android agent [Success]
  - Send ring, notification operations [Success]
  - View device location [Success]
  - View device applications [Success]
  - Remote session [Success]
   - Device type API
  - Create device type [Success]
  - Send operation to device
 - HTTP [Success]
 - MQTT [Fail]
  - Publish device event [Fail]

[-] Broken - do not release since some of API based device type
functionalities are not working.

Thanks & regards,
/charithag

On Thu, Mar 15, 2018 at 4:20 AM, Geeth Munasinghe  wrote:

> Hi all,
>
> We are pleased to announce the release candidate of WSO2 IoT Server 3.3.0.
>
> This is the Release Candidate version 1 of the WSO2 IoT Server 3.3.0.
>
> Please download, test the product and vote. The vote will be open for 72
> hours or as needed.
>
> This release includes following new features
>
>1. DEP Support (Apple device enrollment program)
>2. GDPR Compliance
>
> Known issues: https://github.com/wso2/product-iots/issues
> 
>
> Source and Binary Distribution files: https://github.com/
> wso2/product-iots/releases/tag/v3.3.0-rc1
>
> The tag to be voted upon: https://github.com/wso2/
> product-iots/tree/v3.3.0-rc1
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
>
> Thanks
> Geeth
> --
> *Geeth Munasinghe*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: ge...@wso2.com
> phone:(+94) 777911226 <+94%2077%20791%201226>
>
> 
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
*Charitha Goonetilleke*
Senior Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 77 751 3669 <%2B94777513669>
Twitter:@CharithaWs , fb: charithag
, linkedin: charithag



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

Re: [Dev] [VOTE] Release WSO2 Identity Server 5.5.0 RC2

[Nipuni Bhagya]

Hi all,

I tested the IS 5.5.0-RC2 pack with IAM- Quick Start Guide which covers the
following scenarios.


   - Configuring Single-Sign-On with SAML2
   - Configuring Single-Sign-On with OIDC
   - Configuring Multi-Factor Authentication (with Twitter as the second
   authentication factor.)
   - Configuring Twitter as a Federated Authenticator
   - Setting up Self-Signup
   - Creating a workflow

+1 to go ahead and release.


On Thu, Mar 15, 2018 at 8:16 AM, Nuwandi Wickramasinghe 
wrote:

> Hi,
>
> Tested Below scenario on the IS 5.5.0-RC2 pack.
>
>- User creation in primary/secondary user stores.
>- Saml service provider creation manually, with metadata file and with
>url.
>- Entitlement policy creation and publishing.
>- Service provider access control using entitlement policy.
>
> +1 to go ahead and release.
>
> On Thu, Mar 15, 2018 at 5:19 AM, Darshana Gunawardana 
> wrote:
>
>> Hi all,
>>
>> We are pleased to announce the second release candidate of WSO2 Identity
>> Server 5.5.0.
>>
>> This release fixes the following issues,
>>
>>-
>>- 5.5.0-RC2 fixes
>>
>> 
>>- 5.5.0-RC1 fixes
>>
>> 
>>- 5.5.0-Beta fixes
>>
>> 
>>- 5.5.0-Alpha3 fixes
>>
>> 
>>- 5.5.0-Alpha2 fixes
>>
>> 
>>- 5.5.0-Alpha fixes
>>
>> 
>>- 5.5.0-M4 fixes
>>
>> 
>>- 5.5.0-M3 fixes
>>
>> 
>>- 5.5.0-M2 fixes
>>
>> 
>>- 5.5.0-M1 fixes
>>
>> 
>>
>>
>> Source and distribution
>>
>> Runtime - https://github.com/wso2/product-is/releases/v5.5.0-rc2
>> Analytics - https://github.com/wso2/analytics-is/releases/v5.5.0-rc2
>>
>>
>> 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 -
>>
>> --
>> Regards,
>>
>>
>> *Darshana Gunawardana*Technical Lead
>> WSO2 Inc.; http://wso2.com
>>
>> *E-mail: darsh...@wso2.com *
>> *Mobile: +94718566859 <+94%2071%20856%206859>*Lean . Enterprise .
>> Middleware
>>
>
>
>
> --
>
> Best Regards,
>
> Nuwandi Wickramasinghe
>
> Senior Software Engineer
>
> WSO2 Inc.
>
> Web : http://wso2.com
>
> Mobile : 0719214873
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 



*Kind Regards,Nipuni Bhagya*

*Software Engineering Intern*
*WSO2*



*Mobile : +94 0779028904 <+94%2077%20767%201807>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 Stream Processor 4.1.0 RC1

[Sriskandarajah Suhothayan]

-1
In Mac, the graphics of the editor event flow is not rendering correctly.

Please check the attached image.

On Thu, Mar 15, 2018 at 12:46 AM, Damith Wickramasinghe 
wrote:

> - sup dev
> + dev
>
> On Thu, Mar 15, 2018 at 12:05 AM, Damith Wickramasinghe 
> wrote:
>
>> Hi Devs,
>>
>> We are pleased to announce the release candidate of WSO2 Stream Processor
>> 4.1.0.
>>
>> This is the Release Candidate version 1 of the WSO2 Stream Processor 4.1.
>> 0
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>>
>> Known issues: https://github.com/wso2/product-sp/issues
>>
>> Source and binary distribution files: https://github.com/wso2/produc
>> t-sp/releases/tag/v4.1.0-RC1
>>
>> The tag to be voted upon: https://github.com/wso2/product-sp/tree/v4.1.0-
>> RC1
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> ~ The WSO2 Analytics Team ~
>> Thanks.
>>
>>
>> --
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> 
>> lean.enterprise.middleware
>>
>> mobile: *+94728671315 <+94%2072%20867%201315>*
>>
>>
>
>
> --
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> 
> lean.enterprise.middleware
>
> mobile: *+94728671315 <072%20867%201315>*
>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*S. Suhothayan*
Director
*WSO2 Inc. *
http://wso2.com  


*cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/
twitter: http://twitter.com/suhothayan
 | linked-in:
http://lk.linkedin.com/in/suhothayan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB 4.8.1] Setting empty JSON array from XSLT mediator

[Senduran]

Hi Lahiru,

Can you try the following in your XSLT


tokens


Regards
Senduran

On Thu, Mar 15, 2018 at 3:40 AM, Lahiru Sandaruwan  wrote:

> Devs,
>
> I'm trying $subject using ESB 4.8.1 and I can only set the payload from
> XSLT. Let me explain an example below.
>
> I'm expecting the JSON result as,
> *{*
> * "name": "lahiru",*
> * "tokens": []*
> *}*
>
> Tried setting following from XSLT,
> *...*
>
> **
> **
> **
> *...*
>
> It outputs XML,
>
> **
>
> *lahiru*
>
> **
> **
>
> **
>
> And it is converted to following which is not the disired,
> *{*
> * "name": "lahiru",*
> * "tokens": [*
>
> *""*
>
> *]*
>
> *}*
>
> If I could set XML node as ** from XSLT, it would
> work. But it seems there is no way to set such node.
>
> Any idea on how I can get this done?
>
> Thanks.
>
> --
> --
>
> Lahiru Sandaruwan
> WSO2 Inc., http://wso2.com
>
> lean.enterprise.middleware
>
> m: +1 901 530 2379 <+1%20901-530-2379>
> e: lahi...@wso2.com b: https://medium.com/@lahirugmg
> in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Identity Server 5.5.0 RC2

[Nuwandi Wickramasinghe]

Hi,

Tested Below scenario on the IS 5.5.0-RC2 pack.

   - User creation in primary/secondary user stores.
   - Saml service provider creation manually, with metadata file and with
   url.
   - Entitlement policy creation and publishing.
   - Service provider access control using entitlement policy.

+1 to go ahead and release.

On Thu, Mar 15, 2018 at 5:19 AM, Darshana Gunawardana 
wrote:

> Hi all,
>
> We are pleased to announce the second release candidate of WSO2 Identity
> Server 5.5.0.
>
> This release fixes the following issues,
>
>-
>- 5.5.0-RC2 fixes
>
> 
>- 5.5.0-RC1 fixes
>
> 
>- 5.5.0-Beta fixes
>
> 
>- 5.5.0-Alpha3 fixes
>
> 
>- 5.5.0-Alpha2 fixes
>
> 
>- 5.5.0-Alpha fixes
>
> 
>- 5.5.0-M4 fixes
>
> 
>- 5.5.0-M3 fixes
>
> 
>- 5.5.0-M2 fixes
>
> 
>- 5.5.0-M1 fixes
>
> 
>
>
> Source and distribution
>
> Runtime - https://github.com/wso2/product-is/releases/v5.5.0-rc2
> Analytics - https://github.com/wso2/analytics-is/releases/v5.5.0-rc2
>
>
> 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 -
>
> --
> Regards,
>
>
> *Darshana Gunawardana*Technical Lead
> WSO2 Inc.; http://wso2.com
>
> *E-mail: darsh...@wso2.com *
> *Mobile: +94718566859 <+94%2071%20856%206859>*Lean . Enterprise .
> Middleware
>



-- 

Best Regards,

Nuwandi Wickramasinghe

Senior Software Engineer

WSO2 Inc.

Web : http://wso2.com

Mobile : 0719214873
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue with EI 6.1.1 update 22 and 24.

[Nirothipan Mehalingam]

Hi Jorge,

On Thu, Mar 15, 2018 at 12:07 AM, Jorge  wrote:

> Thanks Madhawa.
>
> It will be available in the update 25?
>

We will  releasing an 6.2.0 RC with these changes soon.

Thanks
Nirothipan

>
> Regards,
>Jorge.
>
> 2018-03-14 14:35 GMT-04:00 Madhawa Gunasekara :
>
>> Hi Jorge,
>>
>> We have fixed this regression issue, It will be available in upcoming
>> release.
>>
>> Thanks,
>> Madhawa
>>
>> On Mar 14, 2018 11:16 PM, "Jorge"  wrote:
>>
>>> Hi all.
>>>
>>> If I have a data service with a resources like this one:
>>>
>>> 
>>> 
>>> 
>>> 
>>> 
>>>
>>>
>>> When I call it I get this error:
>>>
>>> TID: [-1234] [] [2018-03-12 00:01:13,570] ERROR {
>>> org.apache.axis2.json.gson.GsonXMLStreamReader} -  Value type miss
>>> match, Expected value type - 'null', but found - 'STRING' {
>>> org.apache.axis2.json.gson.GsonXMLStreamReader}
>>> TID: [-1234] [] [2018-03-12 00:01:13,584] ERROR
>>> {org.apache.synapse.transport.passthru.ServerWorker} -  Error
>>> processing POST request for : /services/DataAccountService/insertClient.
>>> Error detail: Value type miss match, Expected value type - 'null', but
>>> found - 'STRING'.  {org.apache.synapse.transport.passthru.ServerWorker}
>>> java.lang.IllegalArgumentException: Value type miss match, Expected
>>> value type - 'null', but found - 'STRING'
>>> at org.apache.axis2.json.gson.GsonXMLStreamReader.nextValue(Gso
>>> nXMLStreamReader.java:737)
>>> at org.apache.axis2.json.gson.GsonXMLStreamReader.readValue(Gso
>>> nXMLStreamReader.java:626)
>>> at org.apache.axis2.json.gson.GsonXMLStreamReader.stateTransiti
>>> on(GsonXMLStreamReader.java:532)
>>> at org.apache.axis2.json.gson.GsonXMLStreamReader.next(GsonXMLS
>>> treamReader.java:178)
>>> at org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(St
>>> AXOMBuilder.java:681)
>>> at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBu
>>> ilder.java:214)
>>> at org.apache.axiom.om.impl.llom.OMSerializableImpl.build(OMSer
>>> ializableImpl.java:78)
>>> at org.apache.axiom.om.impl.llom.OMElementImpl.build(OMElementI
>>> mpl.java:722)
>>> at org.apache.axiom.om.impl.llom.OMElementImpl.detach(OMElement
>>> Impl.java:700)
>>> at org.apache.axiom.om.impl.llom.OMNodeImpl.setParent(OMNodeImp
>>> l.java:105)
>>> at org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMEleme
>>> ntImpl.java:296)
>>> at org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMEleme
>>> ntImpl.java:212)
>>> at org.apache.axiom.soap.impl.llom.SOAPBodyImpl.addChild(SOAPBo
>>> dyImpl.java:231)
>>> at org.apache.axis2.json.gson.JSONMessageHandler.invoke(JSONMes
>>> sageHandler.java:84)
>>> at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
>>> at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
>>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
>>> at org.apache.synapse.transport.passthru.ServerWorker.processNo
>>> nEntityEnclosingRESTHandler(ServerWorker.java:331)
>>> at org.apache.synapse.transport.passthru.ServerWorker.processEn
>>> tityEnclosingRequest(ServerWorker.java:377)
>>> at org.apache.synapse.transport.passthru.ServerWorker.run(Serve
>>> rWorker.java:149)
>>> at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.r
>>> un(NativeWorkerPool.java:172)
>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>>> Executor.java:1142)
>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>>> lExecutor.java:617)
>>> at java.lang.Thread.run(Thread.java:745)
>>>
>>> The same dataservice work fine with DSS 3.5.1 and with the first EI
>>> 6.1.1.
>>>
>>> Any idea?
>>>
>>> Regards,
>>> Jorge.
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>


-- 


*M.Nirothipan*
Software Engineer
*Mobile : +94 77 2172692*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Difference between primary and secondary use stores

[Randy Adams]

Hi devs,

I have some confusion on user store types in wso2 products. Please give
some assistance.

What is the difference between primary and secondary user stores in wso2
products?
What is the exact requirement to have two different types of user stores as
this? Why isn't it just "user stores" generally?
What are the different tasks done by these two categories?

Regards,
Randy
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 Identity Server 5.5.0 RC1

[Pushpalanka Jayawardhana]

Hi,

Thanks for the information Darshana. Didn't know it was decided to be
rectified in an RC2.
Thanks for the fix.

On Thu, Mar 15, 2018 at 1:39 AM, Omindu Rathnaweera  wrote:

> Hi Lanka,
>
> This issue is now fixed in the latest oauth version (v5.6.63) and will be
> available with RC2.
>
> Regards,
> Omindu.
>
>
> On Wed, Mar 14, 2018 at 10:32 PM, Darshana Gunawardana 
> wrote:
>
>> Hi Lanka,
>>
>> As you already know, we are working on rectifying this NPE in the RC2.
>>
>> Thanks,
>>
>> On Wed, Mar 14, 2018 at 10:25 PM, Pushpalanka Jayawardhana <
>> la...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> On Wed, Mar 14, 2018 at 10:14 PM, Pushpalanka Jayawardhana <
>>> la...@wso2.com> wrote:
>>>


 On Wed, Mar 14, 2018 at 10:09 PM, Pushpalanka Jayawardhana <
 la...@wso2.com> wrote:

> Hi All,
>
> Tested OIDC hybrid flow with "code idtoken" response type. This is
> breaking with "Invalid response type" error message.
> Could do a bit of debugging and it seems that at [1], it failing to
> identify the existing key for "code idtoken" type.
>
> In the HashTable returned at
> OAuthServerConfiguration.getInstance().getSupportedResponseTypeValidators()
>   execution, "code idtoken" key has the hashCode of '-1819461976' while
> input key 'code idtoken' produce the hashcode of '-732188021'. In plain
> Java code, if we generate the hashCode for 'code idtoken' it also 
> generates
> this. This result in not identifying the sending response type properly.
> Appreciate if this can be further investigated.
>
> [1] - https://github.com/wso2-extensions/identity-inbound-auth-o
> auth/blob/5.6.x/components/org.wso2.carbon.identity.oauth/sr
> c/main/java/org/wso2/carbon/identity/oauth2/model/CarbonOAut
> hAuthzRequest.java#L49
>

 Please ignore this, just realised it should be id_token. Sorry for the
 noise.

>>> Even with this fix the flow is failing with below error,
>>>
>>> java.lang.NullPointerException
>>> 
>>> org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.getIdTokenFromRedirectURL(OAuth2AuthzEndpoint.java:2321)
>>> 
>>> org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.storeSidClaim(OAuth2AuthzEndpoint.java:2225)
>>> 
>>> org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.manageOIDCSessionState(OAuth2AuthzEndpoint.java:2050)
>>> 
>>> org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.handleSuccessfulAuthentication(OAuth2AuthzEndpoint.java:607)
>>> 
>>> org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.handleAuthenticationResponse(OAuth2AuthzEndpoint.java:574)
>>> 
>>> org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.authorize(OAuth2AuthzEndpoint.java:199)
>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> 
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>> 
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> java.lang.reflect.Method.invoke(Method.java:498)
>>> 
>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:188)
>>> 
>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:104)
>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:204)
>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:101)
>>> 
>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
>>> 
>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:94)
>>> 
>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
>>> 
>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>> 
>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:249)
>>> 
>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:248)
>>> 
>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:222)
>>> 
>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:153)
>>> 
>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:171)
>>> 
>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:289)
>>> 
>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:214)
>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:624)
>>> 
>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:265)
>>> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>>> 
>>> 

Re: [Dev] [Architecture] [IAM] eIDAS profile support for SAML

[Harsha Thirimanna]

On Mon, 12 Mar 2018, 13:48 Johann Nallathamby,  wrote:

>
>
> On Mon, Mar 12, 2018 at 10:58 AM, Indunil Upeksha Rathnayake <
> indu...@wso2.com> wrote:
>
>> Hi,
>>
>> In order to support eIDAS profile in IS, as per the 4 eIDAS
>> specifications in [1], there are a set of requirements to be considered
>> including message format, cryptographic requirements etc. Those
>> requirements has been summarized in [2].
>>
>> This is regarding the handling and inclusion of attributes into exchanged
>> messages in eIDAS network. As per the eIDAS SAML attribute profile
>> specification, requesting user attributes MUST be carried out dynamically
>> by including them in a . There are a set of mandatory
>> and optional attributes according to the eIDAS minimum data sets for
>> natural and legal persons (i.e. Natural person is one who can be
>> identified, directly or indirectly, in particular by reference to an
>> identifier such as a name [3]. A legal person is any human being, firm, or
>> government agency that is recognized as having legal rights and
>> obligations, such as having the ability to enter into contracts, to sue,
>> and to be sued [4]).
>>
>> The eIDAS attribute profile support has been currently implemented as
>> follows.
>>
>>1. Include eIDAS attribute profile support in travelocity sample for
>>testing purposes.
>>2. Process the eIDAS attributes in authentication request and send to
>>the requested attributes to framework.
>>3. Introduced a new dialect for "http://eidas.europa.eu/attributes;
>>and configure it in the SP Claim Configuration as the SP Claim mapping
>>Dialect. Include support for multiple SP dialects considering the support
>>for multiple SAML attribute profiles as eIDAS.
>>
>> +1 for this. This is something we planned to have in IS 5.3.0, but
> couldn't complete due to time constraints.
>
>>
>>1.
>>2. In order to get the user claims which are mapped to the SP
>>dialect, in the framework side filter out based on the SP dialect to local
>>claim mappings, if SP claim dialect is configured.
>>
>> How would you choose which dialect to use in the runtime, if one SP can
> have multiple dialects? Remember in our implementation claim is not unique.
> Dialect + claim is unique. So if we don't have the dialect in the
> authentication request, it might be not straightforward to map claims
> between dialects.
>

Yes , this will not possible as Johan said.

Because of internal data structure and the implementation, there can be
same claim Uri in multiple dialect.
But theoretically claim Uri is kind of a name space and dialect is just
grouping of multiple claims. So the namespace should be unique in any
place. Don't we need to enforce that in our documentation even we support
it internally to have same claims in multiple dialect. Is that prcticle to
have such a same claim in different dialect ?



>>1. Process the response retrieved from the framework and send the
>>response to eIDAS network, in appropriate format.
>>
>>
>>
>> Appreciate your comments and suggestions on above approach and please
>> find the following concerns.
>>
>>- With the requested attributes in the authentication request, as per
>>the specification, we may send the AttributeConsumingServiceIndex as well.
>>Currently we have only the basic attribute profile support in SAML. So 
>> when
>>filtering out the requested claims, we need to send both the requested
>>claims in SP configuration and the claims in the request, if
>>AttributeConsumingServiceIndex is retrieved. WDYT?
>>
>> I would rather prefer to have it like the following.
> 1. If configured claim set is null and service provider is requesting
> attributes, send those attributes.
> 2. If at least one claim has been configured in service provider, send the
> intersection of configured claims and requested claims.
>
> This will give us a way to control requested claims if needed. But also
> not force the admins to always configure requested claims for each service
> provider. I don't see any purpose in providing two ways (configuration and
> request) to send back claims to the service provider, unless it is used to
> control access.
>
>>
>>-
>>
>>
>>- As per the current implementation for eIDAS support, first we give
>>priority to the SP configured claims set, if it's not available consider
>>the requested claims in the request. With the oauth request object 
>> feature,
>>the logic for filtering out the requested claims is somewhat different
>>(Requested claims should be configured in SP claims configuration, and 
>> only
>>sending the requested claims in request which are configured in SP). So I
>>think we need to come up with a common solution, if we moving the 
>> requested
>>claim filtering to framework. Shall we use this approach as the common?
>>
>> Common solution could be as explained above.
>
> Regards,
> Johann.
>
>>
>>-
>>
>>
>> 

[Dev] [VOTE] Release WSO2 Identity Server 5.5.0 RC2

[Darshana Gunawardana]

Hi all,

We are pleased to announce the second release candidate of WSO2 Identity
Server 5.5.0.

This release fixes the following issues,

   -
   - 5.5.0-RC2 fixes
   

   - 5.5.0-RC1 fixes
   

   - 5.5.0-Beta fixes
   

   - 5.5.0-Alpha3 fixes
   

   - 5.5.0-Alpha2 fixes
   

   - 5.5.0-Alpha fixes
   

   - 5.5.0-M4 fixes
   

   - 5.5.0-M3 fixes
   

   - 5.5.0-M2 fixes
   

   - 5.5.0-M1 fixes
   



Source and distribution

Runtime - https://github.com/wso2/product-is/releases/v5.5.0-rc2
Analytics - https://github.com/wso2/analytics-is/releases/v5.5.0-rc2


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 -

-- 
Regards,


*Darshana Gunawardana*Technical Lead
WSO2 Inc.; http://wso2.com

*E-mail: darsh...@wso2.com *
*Mobile: +94718566859*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 IoT Server 3.3.0 RC1

[Geeth Munasinghe]

Hi all,

We are pleased to announce the release candidate of WSO2 IoT Server 3.3.0.

This is the Release Candidate version 1 of the WSO2 IoT Server 3.3.0.

Please download, test the product and vote. The vote will be open for 72
hours or as needed.

This release includes following new features

   1. DEP Support (Apple device enrollment program)
   2. GDPR Compliance

Known issues: https://github.com/wso2/product-iots/issues


Source and Binary Distribution files:
https://github.com/wso2/product-iots/releases/tag/v3.3.0-rc1

The tag to be voted upon:
https://github.com/wso2/product-iots/tree/v3.3.0-rc1

Please vote as follows.
[+] Stable - go ahead and release
[-] Broken - do not release (explain why)


Thanks
Geeth
-- 
*Geeth Munasinghe*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: ge...@wso2.com
phone:(+94) 777911226


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

[Dev] [ESB 4.8.1] Setting empty JSON array from XSLT mediator

[Lahiru Sandaruwan]

Devs,

I'm trying $subject using ESB 4.8.1 and I can only set the payload from
XSLT. Let me explain an example below.

I'm expecting the JSON result as,
*{*
* "name": "lahiru",*
* "tokens": []*
*}*

Tried setting following from XSLT,
*...*

**
**
**
*...*

It outputs XML,

**

*lahiru*

**
**

**

And it is converted to following which is not the disired,
*{*
* "name": "lahiru",*
* "tokens": [*

*""*

*]*

*}*

If I could set XML node as ** from XSLT, it would
work. But it seems there is no way to set such node.

Any idea on how I can get this done?

Thanks.

-- 
--

Lahiru Sandaruwan
WSO2 Inc., http://wso2.com

lean.enterprise.middleware

m: +1 901 530 2379
e: lahi...@wso2.com b: https://medium.com/@lahirugmg
in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 Data Analytics Server 3.2.0 RC1

[Sajith Perera]

Hi Devs,

We are pleased to announce the release candidate of WSO2 Data Analytics
Server 3.2.0.

This is the Release Candidate version 1 of the WSO2 Data Analytics Server
3.2.0

Please download, test the product and vote. The vote will be open for 72
hours or as needed.

Known issues: https://github.com/wso2/product-das/issues

Source and binary distribution files:
https://github.com/wso2/product-das/releases/tag/v3.2.0-RC1

The tag to be voted upon:
https://github.com/wso2/product-das/tree/v3.2.0-RC1

Please vote as follows.
[+] Stable - go ahead and release
[-] Broken - do not release (explain why)

~ The WSO2 Analytics Team ~

Thanks.
-- 

Sajith Dimal
Software Engineer
Email : saji...@wso2.com
Mobile : +94783101496
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Throttling Policy in a JMS Listener

[Júnior]

Hi,

I am trying to use the Throttle mediator in a proxy that is listening to a
JMS Queue.

I would to limit the number of messages it process in a time interval. And
the rejected ones would be stored in a messageStore to be processed later.

When consuming the messages from queue, it seems the policy is not
activated but when I call the proxy from SOAPUI, I see the policy working.

Does this work for a jms listener?

Follow my policy:



http://schemas.xmlsoap.org/ws/2004/09/policy; xmlns:wsu="
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
">
http://www.wso2.org/products/wso2commons/throttle;>

2

other




5

1
2000



















http://localhost:8280/services/ChannelAQ"/>







Thanks,
-- 
Francisco Ribeiro
*SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 Identity Server 5.5.0 RC1

[Omindu Rathnaweera]

Hi Lanka,

This issue is now fixed in the latest oauth version (v5.6.63) and will be
available with RC2.

Regards,
Omindu.


On Wed, Mar 14, 2018 at 10:32 PM, Darshana Gunawardana 
wrote:

> Hi Lanka,
>
> As you already know, we are working on rectifying this NPE in the RC2.
>
> Thanks,
>
> On Wed, Mar 14, 2018 at 10:25 PM, Pushpalanka Jayawardhana  > wrote:
>
>> Hi,
>>
>> On Wed, Mar 14, 2018 at 10:14 PM, Pushpalanka Jayawardhana <
>> la...@wso2.com> wrote:
>>
>>>
>>>
>>> On Wed, Mar 14, 2018 at 10:09 PM, Pushpalanka Jayawardhana <
>>> la...@wso2.com> wrote:
>>>
 Hi All,

 Tested OIDC hybrid flow with "code idtoken" response type. This is
 breaking with "Invalid response type" error message.
 Could do a bit of debugging and it seems that at [1], it failing to
 identify the existing key for "code idtoken" type.

 In the HashTable returned at
 OAuthServerConfiguration.getInstance().getSupportedResponseTypeValidators()
   execution, "code idtoken" key has the hashCode of '-1819461976' while
 input key 'code idtoken' produce the hashcode of '-732188021'. In plain
 Java code, if we generate the hashCode for 'code idtoken' it also generates
 this. This result in not identifying the sending response type properly.
 Appreciate if this can be further investigated.

 [1] - https://github.com/wso2-extensions/identity-inbound-auth-o
 auth/blob/5.6.x/components/org.wso2.carbon.identity.oauth/sr
 c/main/java/org/wso2/carbon/identity/oauth2/model/CarbonOAut
 hAuthzRequest.java#L49

>>>
>>> Please ignore this, just realised it should be id_token. Sorry for the
>>> noise.
>>>
>> Even with this fix the flow is failing with below error,
>>
>> java.lang.NullPointerException
>>  
>> org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.getIdTokenFromRedirectURL(OAuth2AuthzEndpoint.java:2321)
>>  
>> org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.storeSidClaim(OAuth2AuthzEndpoint.java:2225)
>>  
>> org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.manageOIDCSessionState(OAuth2AuthzEndpoint.java:2050)
>>  
>> org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.handleSuccessfulAuthentication(OAuth2AuthzEndpoint.java:607)
>>  
>> org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.handleAuthenticationResponse(OAuth2AuthzEndpoint.java:574)
>>  
>> org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.authorize(OAuth2AuthzEndpoint.java:199)
>>  sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>  
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>  
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>  java.lang.reflect.Method.invoke(Method.java:498)
>>  
>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:188)
>>  
>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:104)
>>  org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:204)
>>  org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:101)
>>  
>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
>>  
>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:94)
>>  
>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
>>  
>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>  
>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:249)
>>  
>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:248)
>>  
>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:222)
>>  
>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:153)
>>  
>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:171)
>>  
>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:289)
>>  
>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:214)
>>  javax.servlet.http.HttpServlet.service(HttpServlet.java:624)
>>  
>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:265)
>>  org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>>  
>> org.wso2.carbon.webapp.mgt.filter.AuthorizationHeaderFilter.doFilter(AuthorizationHeaderFilter.java:85)
>>  
>> org.wso2.carbon.ui.filters.cache.ContentTypeBasedCachePreventionFilter.doFilter(ContentTypeBasedCachePreventionFilter.java:53)
>>  
>> org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(HttpHeaderSecurityFilter.java:124)

Re: [Dev] [VOTE] Release WSO2 Stream Processor 4.1.0 RC1

[Damith Wickramasinghe]

- sup dev
+ dev

On Thu, Mar 15, 2018 at 12:05 AM, Damith Wickramasinghe 
wrote:

> Hi Devs,
>
> We are pleased to announce the release candidate of WSO2 Stream Processor
> 4.1.0.
>
> This is the Release Candidate version 1 of the WSO2 Stream Processor 4.1.0
>
> Please download, test the product and vote. Vote will be open for 72 hours
> or as needed.
>
> Known issues: https://github.com/wso2/product-sp/issues
>
> Source and binary distribution files: https://github.com/wso2/produc
> t-sp/releases/tag/v4.1.0-RC1
>
> The tag to be voted upon: https://github.com/wso2/product-sp/tree/v4.1.0-
> RC1
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> ~ The WSO2 Analytics Team ~
> Thanks.
>
>
> --
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> 
> lean.enterprise.middleware
>
> mobile: *+94728671315 <+94%2072%20867%201315>*
>
>


-- 
Senior Software Engineer
WSO2 Inc.; http://wso2.com

lean.enterprise.middleware

mobile: *+94728671315*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Processing Big/Huge/Large files in wso2 using vfs.Facing issues

[Madhawa Gunasekara]

Hi Aditya,

The best way is to use the smooks mediator to process huge XML payloads.
Here is the sample for the smooks mediator. [1]

[1]
https://docs.wso2.com/display/ESB490/Sample+658%3A+Huge+XML+Message+Processing+with+Smooks+Mediator

Thanks,
Madhawa

On Wed, Mar 14, 2018 at 11:19 PM, aditya shivankar <
shivankar.adit...@gmail.com> wrote:

> Respected Sir,
>
> Removed the logger, but still not able to process large files.
> Requirement is to process files of size upto GB's .
> Please Guide.
>
> With Regards,
> Aditya
>
> On Wed, Mar 14, 2018 at 8:08 PM, Ruwan Abeykoon  wrote:
>
>> Hi Adithya,
>> Can you try this without the log mediator.
>> Log mediator is usually tries to decode the payload. We call that a
>> content aware mediator. The content aware mediators has the issue decoding
>> large payloads.
>>
>> Cheers,
>> Ruwan
>>
>> On Wed, Mar 14, 2018 at 6:43 PM, aditya shivankar <
>> shivankar.adit...@gmail.com> wrote:
>>
>>> Respected Sir,
>>>
>>> Forgot to mention ,Sometimes I am getting OutOfMemoryError as well
>>>
>>> java.lang.OutOfMemoryError: Java heap space
>>> Dumping heap to C:/wso2ei-6.1.1/wso2ei-6.1.1/repository/logs/heap-dump.hprof
>>> ...
>>> Unable to create C:/wso2ei-6.1.1/wso2ei-6.1.1/r
>>> epository/logs/heap-dump.hprof: File exists
>>> [2018-03-14 17:16:01,228] [EI-Core] ERROR - NativeWorkerPool Uncaught
>>> exception
>>> java.lang.OutOfMemoryError: Java heap space
>>> at java.util.Arrays.copyOf(Unknown Source)
>>> at java.lang.AbstractStringBuilder.ensureCapacityInternal(Unknown
>>> Source)
>>> at java.lang.AbstractStringBuilder.append(Unknown Source)
>>> at java.lang.StringBuffer.append(Unknown Source)
>>> at org.apache.log4j.helpers.PatternParser$LiteralPatternConvert
>>> er.format(PatternParser.java:419)
>>>
>>> With Regards,
>>> Aditya
>>>
>>> On Wed, Mar 14, 2018 at 4:46 PM, aditya shivankar <
>>> shivankar.adit...@gmail.com> wrote:
>>>
 added the missing attachment from previous mail

 On Wed, Mar 14, 2018 at 4:44 PM, aditya shivankar <
 shivankar.adit...@gmail.com> wrote:

> Respected Sir/Madam,
>
> I am able to achieve below file processing using vfs, and datamapper.
> But when trying to process files more than size of 8 MB or more the flow 
> is
> failing with out of memory. Please guide
>
> step 1. I am using vfs to read one xml file from one location.
> step 2. Then using datamapper to convert the xml file to csv.
> step 3. Then writing the converted output to another location.
>
>
> 
> http://ws.apache.org/ns/synapse;>
> 
> 
> 
> 
> 
>  type="STRING" value="true"/>
>  type="STRING" value=""/>
>  inputSchema="gov:datamapper/xmlToCsv1_inputSchema.json"
> inputType="XML" outputSchema="gov:datamapper/xmlToCsv1_outputSchema.json"
> outputType="CSV"/>
>  name="transport.vfs.ReplyFileName" scope="transport" type="STRING"/>
>  value="true"/>
>  value="application/csv"/>
>  scope="transport"/>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 50ms
> f
> ile:///C:/Flatfile/input
> application/xml
> MOVE
> file:///C:/Flatfile/failure
> MOVE
> .*\.xml
> disable
> file:///C:/Flatfile/orgFilesProcessedSuccessfully
> 
>
>
> sometimes it is not able to delete .lock files from input folder.
> sometimes timeout error.
>
> etc..
>
> Sample input attached.
>
> With regards,
> Aditya
>


>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Madhawa Gunasekara*
Senior Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 719411002 <+94+719411002>
blog: *http://madhawa-gunasekara.blogspot.com
*
linkedin: *http://lk.linkedin.com/in/mgunasekara
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue with EI 6.1.1 update 22 and 24.

[Jorge]

Thanks Madhawa.

It will be available in the update 25?

Regards,
   Jorge.

2018-03-14 14:35 GMT-04:00 Madhawa Gunasekara :

> Hi Jorge,
>
> We have fixed this regression issue, It will be available in upcoming
> release.
>
> Thanks,
> Madhawa
>
> On Mar 14, 2018 11:16 PM, "Jorge"  wrote:
>
>> Hi all.
>>
>> If I have a data service with a resources like this one:
>>
>> 
>> 
>> 
>> 
>> 
>>
>>
>> When I call it I get this error:
>>
>> TID: [-1234] [] [2018-03-12 00:01:13,570] ERROR {
>> org.apache.axis2.json.gson.GsonXMLStreamReader} -  Value type miss
>> match, Expected value type - 'null', but found - 'STRING' {
>> org.apache.axis2.json.gson.GsonXMLStreamReader}
>> TID: [-1234] [] [2018-03-12 00:01:13,584] ERROR
>> {org.apache.synapse.transport.passthru.ServerWorker} -  Error processing
>> POST request for : /services/DataAccountService/insertClient. Error
>> detail: Value type miss match, Expected value type - 'null', but found -
>> 'STRING'.  {org.apache.synapse.transport.passthru.ServerWorker}
>> java.lang.IllegalArgumentException: Value type miss match, Expected
>> value type - 'null', but found - 'STRING'
>> at org.apache.axis2.json.gson.GsonXMLStreamReader.nextValue(Gso
>> nXMLStreamReader.java:737)
>> at org.apache.axis2.json.gson.GsonXMLStreamReader.readValue(Gso
>> nXMLStreamReader.java:626)
>> at org.apache.axis2.json.gson.GsonXMLStreamReader.stateTransiti
>> on(GsonXMLStreamReader.java:532)
>> at org.apache.axis2.json.gson.GsonXMLStreamReader.next(GsonXMLS
>> treamReader.java:178)
>> at org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(
>> StAXOMBuilder.java:681)
>> at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBu
>> ilder.java:214)
>> at org.apache.axiom.om.impl.llom.OMSerializableImpl.build(OMSer
>> ializableImpl.java:78)
>> at org.apache.axiom.om.impl.llom.OMElementImpl.build(OMElementI
>> mpl.java:722)
>> at org.apache.axiom.om.impl.llom.OMElementImpl.detach(OMElement
>> Impl.java:700)
>> at org.apache.axiom.om.impl.llom.OMNodeImpl.setParent(OMNodeImp
>> l.java:105)
>> at org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMEleme
>> ntImpl.java:296)
>> at org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMEleme
>> ntImpl.java:212)
>> at org.apache.axiom.soap.impl.llom.SOAPBodyImpl.addChild(SOAPBo
>> dyImpl.java:231)
>> at org.apache.axis2.json.gson.JSONMessageHandler.invoke(JSONMes
>> sageHandler.java:84)
>> at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
>> at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
>> at org.apache.synapse.transport.passthru.ServerWorker.processNo
>> nEntityEnclosingRESTHandler(ServerWorker.java:331)
>> at org.apache.synapse.transport.passthru.ServerWorker.processEn
>> tityEnclosingRequest(ServerWorker.java:377)
>> at org.apache.synapse.transport.passthru.ServerWorker.run(Serve
>> rWorker.java:149)
>> at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.
>> run(NativeWorkerPool.java:172)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>> Executor.java:1142)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>> lExecutor.java:617)
>> at java.lang.Thread.run(Thread.java:745)
>>
>> The same dataservice work fine with DSS 3.5.1 and with the first EI 6.1.1.
>>
>> Any idea?
>>
>> Regards,
>> Jorge.
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue with EI 6.1.1 update 22 and 24.

[Madhawa Gunasekara]

Hi Jorge,

We have fixed this regression issue, It will be available in upcoming
release.

Thanks,
Madhawa

On Mar 14, 2018 11:16 PM, "Jorge"  wrote:

> Hi all.
>
> If I have a data service with a resources like this one:
>
> 
> 
> 
> 
> 
>
>
> When I call it I get this error:
>
> TID: [-1234] [] [2018-03-12 00:01:13,570] ERROR
> {org.apache.axis2.json.gson.GsonXMLStreamReader} -  Value type miss
> match, Expected value type - 'null', but found - 'STRING'
> {org.apache.axis2.json.gson.GsonXMLStreamReader}
> TID: [-1234] [] [2018-03-12 00:01:13,584] ERROR
> {org.apache.synapse.transport.passthru.ServerWorker} -  Error processing
> POST request for : /services/DataAccountService/insertClient. Error
> detail: Value type miss match, Expected value type - 'null', but found -
> 'STRING'.  {org.apache.synapse.transport.passthru.ServerWorker}
> java.lang.IllegalArgumentException: Value type miss match, Expected value
> type - 'null', but found - 'STRING'
> at org.apache.axis2.json.gson.GsonXMLStreamReader.nextValue(
> GsonXMLStreamReader.java:737)
> at org.apache.axis2.json.gson.GsonXMLStreamReader.readValue(
> GsonXMLStreamReader.java:626)
> at org.apache.axis2.json.gson.GsonXMLStreamReader.stateTransition(
> GsonXMLStreamReader.java:532)
> at org.apache.axis2.json.gson.GsonXMLStreamReader.next(
> GsonXMLStreamReader.java:178)
> at org.apache.axiom.om.impl.builder.StAXOMBuilder.
> parserNext(StAXOMBuilder.java:681)
> at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(
> StAXOMBuilder.java:214)
> at org.apache.axiom.om.impl.llom.OMSerializableImpl.build(
> OMSerializableImpl.java:78)
> at org.apache.axiom.om.impl.llom.OMElementImpl.build(
> OMElementImpl.java:722)
> at org.apache.axiom.om.impl.llom.OMElementImpl.detach(
> OMElementImpl.java:700)
> at org.apache.axiom.om.impl.llom.OMNodeImpl.setParent(OMNodeImpl.java:105)
> at org.apache.axiom.om.impl.llom.OMElementImpl.addChild(
> OMElementImpl.java:296)
> at org.apache.axiom.om.impl.llom.OMElementImpl.addChild(
> OMElementImpl.java:212)
> at org.apache.axiom.soap.impl.llom.SOAPBodyImpl.addChild(
> SOAPBodyImpl.java:231)
> at org.apache.axis2.json.gson.JSONMessageHandler.invoke(
> JSONMessageHandler.java:84)
> at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
> at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
> at org.apache.synapse.transport.passthru.ServerWorker.
> processNonEntityEnclosingRESTHandler(ServerWorker.java:331)
> at org.apache.synapse.transport.passthru.ServerWorker.
> processEntityEnclosingRequest(ServerWorker.java:377)
> at org.apache.synapse.transport.passthru.ServerWorker.run(
> ServerWorker.java:149)
> at org.apache.axis2.transport.base.threads.NativeWorkerPool$
> 1.run(NativeWorkerPool.java:172)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
>
> The same dataservice work fine with DSS 3.5.1 and with the first EI 6.1.1.
>
> Any idea?
>
> Regards,
> Jorge.
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Processing Big/Huge/Large files in wso2 using vfs.Facing issues

[aditya shivankar]

Respected Sir,

Removed the logger, but still not able to process large files.
Requirement is to process files of size upto GB's .
Please Guide.

With Regards,
Aditya

On Wed, Mar 14, 2018 at 8:08 PM, Ruwan Abeykoon  wrote:

> Hi Adithya,
> Can you try this without the log mediator.
> Log mediator is usually tries to decode the payload. We call that a
> content aware mediator. The content aware mediators has the issue decoding
> large payloads.
>
> Cheers,
> Ruwan
>
> On Wed, Mar 14, 2018 at 6:43 PM, aditya shivankar <
> shivankar.adit...@gmail.com> wrote:
>
>> Respected Sir,
>>
>> Forgot to mention ,Sometimes I am getting OutOfMemoryError as well
>>
>> java.lang.OutOfMemoryError: Java heap space
>> Dumping heap to C:/wso2ei-6.1.1/wso2ei-6.1.1/repository/logs/heap-dump.hprof
>> ...
>> Unable to create C:/wso2ei-6.1.1/wso2ei-6.1.1/r
>> epository/logs/heap-dump.hprof: File exists
>> [2018-03-14 17:16:01,228] [EI-Core] ERROR - NativeWorkerPool Uncaught
>> exception
>> java.lang.OutOfMemoryError: Java heap space
>> at java.util.Arrays.copyOf(Unknown Source)
>> at java.lang.AbstractStringBuilder.ensureCapacityInternal(Unknown Source)
>> at java.lang.AbstractStringBuilder.append(Unknown Source)
>> at java.lang.StringBuffer.append(Unknown Source)
>> at org.apache.log4j.helpers.PatternParser$LiteralPatternConvert
>> er.format(PatternParser.java:419)
>>
>> With Regards,
>> Aditya
>>
>> On Wed, Mar 14, 2018 at 4:46 PM, aditya shivankar <
>> shivankar.adit...@gmail.com> wrote:
>>
>>> added the missing attachment from previous mail
>>>
>>> On Wed, Mar 14, 2018 at 4:44 PM, aditya shivankar <
>>> shivankar.adit...@gmail.com> wrote:
>>>
 Respected Sir/Madam,

 I am able to achieve below file processing using vfs, and datamapper.
 But when trying to process files more than size of 8 MB or more the flow is
 failing with out of memory. Please guide

 step 1. I am using vfs to read one xml file from one location.
 step 2. Then using datamapper to convert the xml file to csv.
 step 3. Then writing the converted output to another location.


 
 http://ws.apache.org/ns/synapse;>
 
 
 
 
 
 >>> type="STRING" value="true"/>
 >>> type="STRING" value=""/>
 >>> inputSchema="gov:datamapper/xmlToCsv1_inputSchema.json"
 inputType="XML" outputSchema="gov:datamapper/xmlToCsv1_outputSchema.json"
 outputType="CSV"/>
 >>> name="transport.vfs.ReplyFileName" scope="transport" type="STRING"/>
 >>> value="true"/>
 >>> value="application/csv"/>
 >>> scope="transport"/>
 
 
 
 
 
 
 
 
 
 50ms
 f
 ile:///C:/Flatfile/input
 application/xml
 MOVE
 file:///C:/Flatfile/failure
 MOVE
 .*\.xml
 disable
 file:///C:/Flatfile/orgFilesProcessedSuccessfully
 


 sometimes it is not able to delete .lock files from input folder.
 sometimes timeout error.

 etc..

 Sample input attached.

 With regards,
 Aditya

>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Issue with EI 6.1.1 update 22 and 24.

[Jorge]

Hi all.

If I have a data service with a resources like this one:








When I call it I get this error:

TID: [-1234] [] [2018-03-12 00:01:13,570] ERROR
{org.apache.axis2.json.gson.GsonXMLStreamReader} -  Value type miss match,
Expected value type - 'null', but found - 'STRING'
{org.apache.axis2.json.gson.GsonXMLStreamReader}
TID: [-1234] [] [2018-03-12 00:01:13,584] ERROR
{org.apache.synapse.transport.passthru.ServerWorker} -  Error processing
POST request for : /services/DataAccountService/insertClient. Error detail:
Value type miss match, Expected value type - 'null', but found - 'STRING'.
{org.apache.synapse.transport.passthru.ServerWorker}
java.lang.IllegalArgumentException: Value type miss match, Expected value
type - 'null', but found - 'STRING'
at
org.apache.axis2.json.gson.GsonXMLStreamReader.nextValue(GsonXMLStreamReader.java:737)
at
org.apache.axis2.json.gson.GsonXMLStreamReader.readValue(GsonXMLStreamReader.java:626)
at
org.apache.axis2.json.gson.GsonXMLStreamReader.stateTransition(GsonXMLStreamReader.java:532)
at
org.apache.axis2.json.gson.GsonXMLStreamReader.next(GsonXMLStreamReader.java:178)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
at
org.apache.axiom.om.impl.llom.OMSerializableImpl.build(OMSerializableImpl.java:78)
at org.apache.axiom.om.impl.llom.OMElementImpl.build(OMElementImpl.java:722)
at
org.apache.axiom.om.impl.llom.OMElementImpl.detach(OMElementImpl.java:700)
at org.apache.axiom.om.impl.llom.OMNodeImpl.setParent(OMNodeImpl.java:105)
at
org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:296)
at
org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:212)
at
org.apache.axiom.soap.impl.llom.SOAPBodyImpl.addChild(SOAPBodyImpl.java:231)
at
org.apache.axis2.json.gson.JSONMessageHandler.invoke(JSONMessageHandler.java:84)
at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
at
org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:331)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:377)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:149)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

The same dataservice work fine with DSS 3.5.1 and with the first EI 6.1.1.

Any idea?

Regards,
Jorge.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 Identity Server 5.5.0 RC1

[Darshana Gunawardana]

Hi Lanka,

As you already know, we are working on rectifying this NPE in the RC2.

Thanks,

On Wed, Mar 14, 2018 at 10:25 PM, Pushpalanka Jayawardhana 
wrote:

> Hi,
>
> On Wed, Mar 14, 2018 at 10:14 PM, Pushpalanka Jayawardhana  > wrote:
>
>>
>>
>> On Wed, Mar 14, 2018 at 10:09 PM, Pushpalanka Jayawardhana <
>> la...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> Tested OIDC hybrid flow with "code idtoken" response type. This is
>>> breaking with "Invalid response type" error message.
>>> Could do a bit of debugging and it seems that at [1], it failing to
>>> identify the existing key for "code idtoken" type.
>>>
>>> In the HashTable returned at
>>> OAuthServerConfiguration.getInstance().getSupportedResponseTypeValidators()
>>>   execution, "code idtoken" key has the hashCode of '-1819461976' while
>>> input key 'code idtoken' produce the hashcode of '-732188021'. In plain
>>> Java code, if we generate the hashCode for 'code idtoken' it also generates
>>> this. This result in not identifying the sending response type properly.
>>> Appreciate if this can be further investigated.
>>>
>>> [1] - https://github.com/wso2-extensions/identity-inbound-auth-o
>>> auth/blob/5.6.x/components/org.wso2.carbon.identity.oauth/
>>> src/main/java/org/wso2/carbon/identity/oauth2/model/CarbonOA
>>> uthAuthzRequest.java#L49
>>>
>>
>> Please ignore this, just realised it should be id_token. Sorry for the
>> noise.
>>
> Even with this fix the flow is failing with below error,
>
> java.lang.NullPointerException
>   
> org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.getIdTokenFromRedirectURL(OAuth2AuthzEndpoint.java:2321)
>   
> org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.storeSidClaim(OAuth2AuthzEndpoint.java:2225)
>   
> org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.manageOIDCSessionState(OAuth2AuthzEndpoint.java:2050)
>   
> org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.handleSuccessfulAuthentication(OAuth2AuthzEndpoint.java:607)
>   
> org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.handleAuthenticationResponse(OAuth2AuthzEndpoint.java:574)
>   
> org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.authorize(OAuth2AuthzEndpoint.java:199)
>   sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   java.lang.reflect.Method.invoke(Method.java:498)
>   
> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:188)
>   
> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:104)
>   org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:204)
>   org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:101)
>   
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
>   
> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:94)
>   
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
>   
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>   
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:249)
>   
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:248)
>   
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:222)
>   
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:153)
>   
> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:171)
>   
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:289)
>   
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:214)
>   javax.servlet.http.HttpServlet.service(HttpServlet.java:624)
>   
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:265)
>   org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>   
> org.wso2.carbon.webapp.mgt.filter.AuthorizationHeaderFilter.doFilter(AuthorizationHeaderFilter.java:85)
>   
> org.wso2.carbon.ui.filters.cache.ContentTypeBasedCachePreventionFilter.doFilter(ContentTypeBasedCachePreventionFilter.java:53)
>   
> org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(HttpHeaderSecurityFilter.java:124)
>
>
> This is only when the user login is performed in the flow. If the
> authorization request is sent in a browser where user is already loggedin,
> the issue is not occurring and flow works fine.
>
>>
>>> ​
>>>
>>> On Wed, Mar 14, 2018 at 7:52 PM, Sagara Gunathunga 

Re: [Dev] [Architecture] [VOTE] Release WSO2 Identity Server 5.5.0 RC1

[Pushpalanka Jayawardhana]

Hi,

On Wed, Mar 14, 2018 at 10:14 PM, Pushpalanka Jayawardhana 
wrote:

>
>
> On Wed, Mar 14, 2018 at 10:09 PM, Pushpalanka Jayawardhana  > wrote:
>
>> Hi All,
>>
>> Tested OIDC hybrid flow with "code idtoken" response type. This is
>> breaking with "Invalid response type" error message.
>> Could do a bit of debugging and it seems that at [1], it failing to
>> identify the existing key for "code idtoken" type.
>>
>> In the HashTable returned at
>> OAuthServerConfiguration.getInstance().getSupportedResponseTypeValidators()
>>   execution, "code idtoken" key has the hashCode of '-1819461976' while
>> input key 'code idtoken' produce the hashcode of '-732188021'. In plain
>> Java code, if we generate the hashCode for 'code idtoken' it also generates
>> this. This result in not identifying the sending response type properly.
>> Appreciate if this can be further investigated.
>>
>> [1] - https://github.com/wso2-extensions/identity-inbound-auth-
>> oauth/blob/5.6.x/components/org.wso2.carbon.identity.
>> oauth/src/main/java/org/wso2/carbon/identity/oauth2/model/C
>> arbonOAuthAuthzRequest.java#L49
>>
>
> Please ignore this, just realised it should be id_token. Sorry for the
> noise.
>
Even with this fix the flow is failing with below error,

java.lang.NullPointerException

org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.getIdTokenFromRedirectURL(OAuth2AuthzEndpoint.java:2321)

org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.storeSidClaim(OAuth2AuthzEndpoint.java:2225)

org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.manageOIDCSessionState(OAuth2AuthzEndpoint.java:2050)

org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.handleSuccessfulAuthentication(OAuth2AuthzEndpoint.java:607)

org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.handleAuthenticationResponse(OAuth2AuthzEndpoint.java:574)

org.wso2.carbon.identity.oauth.endpoint.authz.OAuth2AuthzEndpoint.authorize(OAuth2AuthzEndpoint.java:199)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:498)

org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:188)

org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:104)
org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:204)
org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:101)

org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)

org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:94)

org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)

org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)

org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:249)

org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:248)

org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:222)

org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:153)

org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:171)

org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:289)

org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:214)
javax.servlet.http.HttpServlet.service(HttpServlet.java:624)

org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:265)
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)

org.wso2.carbon.webapp.mgt.filter.AuthorizationHeaderFilter.doFilter(AuthorizationHeaderFilter.java:85)

org.wso2.carbon.ui.filters.cache.ContentTypeBasedCachePreventionFilter.doFilter(ContentTypeBasedCachePreventionFilter.java:53)

org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(HttpHeaderSecurityFilter.java:124)


This is only when the user login is performed in the flow. If the
authorization request is sent in a browser where user is already loggedin,
the issue is not occurring and flow works fine.

>
>> ​
>>
>> On Wed, Mar 14, 2018 at 7:52 PM, Sagara Gunathunga 
>> wrote:
>>
>>>
>>>
>>> On Wed, Mar 14, 2018 at 7:46 PM, Jayanga Kaushalya 
>>> wrote:
>>>
 Hi Sagara,

 Yes I have suggested other teams also to follow the IS convention in
 [1]. APIM team told me offline that they already changed. Hope 

Re: [Dev] [Architecture] [VOTE] Release WSO2 Identity Server 5.5.0 RC1

[Pushpalanka Jayawardhana]

On Wed, Mar 14, 2018 at 10:09 PM, Pushpalanka Jayawardhana 
wrote:

> Hi All,
>
> Tested OIDC hybrid flow with "code idtoken" response type. This is
> breaking with "Invalid response type" error message.
> Could do a bit of debugging and it seems that at [1], it failing to
> identify the existing key for "code idtoken" type.
>
> In the HashTable returned at
> OAuthServerConfiguration.getInstance().getSupportedResponseTypeValidators()
>   execution, "code idtoken" key has the hashCode of '-1819461976' while
> input key 'code idtoken' produce the hashcode of '-732188021'. In plain
> Java code, if we generate the hashCode for 'code idtoken' it also generates
> this. This result in not identifying the sending response type properly.
> Appreciate if this can be further investigated.
>
> [1] - https://github.com/wso2-extensions/identity-inbound-
> auth-oauth/blob/5.6.x/components/org.wso2.carbon.
> identity.oauth/src/main/java/org/wso2/carbon/identity/oauth2/model/
> CarbonOAuthAuthzRequest.java#L49
>

Please ignore this, just realised it should be id_token. Sorry for the
noise.

>
> ​
>
> On Wed, Mar 14, 2018 at 7:52 PM, Sagara Gunathunga 
> wrote:
>
>>
>>
>> On Wed, Mar 14, 2018 at 7:46 PM, Jayanga Kaushalya 
>> wrote:
>>
>>> Hi Sagara,
>>>
>>> Yes I have suggested other teams also to follow the IS convention in
>>> [1]. APIM team told me offline that they already changed. Hope others will
>>> do the same.
>>>
>>
>> Great.
>>
>> Thanks !
>>
>>>
>>> [1] [GDPR] Anonymization Tool default configurations/references are
>>> differed over the Products
>>>
>>> Thanks!
>>>
>>> *Jayanga Kaushalya*
>>> Senior Software Engineer
>>> Mobile: +94777860160 <+94%2077%20786%200160>
>>> WSO2 Inc. | http://wso2.com
>>> lean.enterprise.middleware
>>>
>>>
>>>
>>> On Wed, Mar 14, 2018 at 7:37 PM, Sagara Gunathunga 
>>> wrote:
>>>


 On Wed, Mar 14, 2018 at 7:27 PM, Sathya Bandara 
 wrote:

> Hi all,
>
> We are calling-off this vote as we have found an issue,
>
>- for user-mgt ui component in EI product
>- in Windows environment
>
> Since we want to align same component versions among EI & IS, we will
> fix this and update versions in IS as well. Additionally we will fix the
> issue in README.txt along with this.
>
 Ruwan/Jayanga, shall we also look into the suggestion made by Lanka in
 the "GDPR compliance for WSO2 products" thread ?

 Thanks !

> We will do a RC2 and call for a vote soon.
>
> [1] https://github.com/wso2/product-ei/issues/2004
>
> On Wed, Mar 14, 2018 at 6:29 PM, Nilasini Thirunavukkarasu <
> nilas...@wso2.com> wrote:
>
>> Hi,
>>
>> I have tested the following flows in mysql.
>>
>>- User management, role management (Primary + Secondary user
>>store)
>>- OIDC flow (password grant, authorization code)(Primary +
>>Secondary user store)
>>- consent management with SAML SSO for primary and secondary
>>users.
>>- SAML assertion encryption and response signing.
>>
>>
>> I have tested the following flow with h2
>>
>>- federated scenario with two IS
>>
>> +1 to go ahead and release
>>
>>
>> Thanks,
>> Nila.
>>
>>
>> On Wed, Mar 14, 2018 at 6:15 PM, Darshana Gunawardana <
>> darsh...@wso2.com> wrote:
>>
>>> Hi Dilini,
>>>
>>> We will fix this, if we noted any blocker for RC1 release.. If not,
>>> let's continue on the vote considering this is a known issue..
>>>
>>> Thanks,
>>>
>>> On Wed, Mar 14, 2018 at 6:05 PM, Dilini Gunatilake >> > wrote:
>>>
 Hi,

 The README .txt contains references to old documentation and few
 other issues which is reported in [1]. Better if we can fix those. 
 WDUT?

 [1] https://github.com/wso2/product-is/issues/2945

 Regards,
 Dilini



 On Wed, Mar 14, 2018 at 5:23 PM, Farasath Ahamed <
 farasa...@wso2.com> wrote:

>
> Tested Below scenario on the IS 5.5.0-RC1 pack with MSSQL database
>
>- Create an OAuth app using Dynamic Client Registration
>endpoint
>- Configured mandatory claims for the service provider
>- Tested OIDC Implicit flow with user consent management
>enabled
>- Verified that the user claims sent in the id_token are
>filtered based on user consent.
>
> +1 to go ahead and release
>
>
> On Wed, Mar 14, 2018 at 11:16 AM, Sathya Bandara 
> wrote:
>
>> Hi all,
>>
>> We are pleased to announce the first release candidate of WSO2
>> Identity Server 5.5.0.

Re: [Dev] [Architecture] [VOTE] Release WSO2 Identity Server 5.5.0 RC1

[Pushpalanka Jayawardhana]

Hi All,

Tested OIDC hybrid flow with "code idtoken" response type. This is breaking
with "Invalid response type" error message.
Could do a bit of debugging and it seems that at [1], it failing to
identify the existing key for "code idtoken" type.

In the HashTable returned at
OAuthServerConfiguration.getInstance().getSupportedResponseTypeValidators()
  execution, "code idtoken" key has the hashCode of '-1819461976' while
input key 'code idtoken' produce the hashcode of '-732188021'. In plain
Java code, if we generate the hashCode for 'code idtoken' it also generates
this. This result in not identifying the sending response type properly.
Appreciate if this can be further investigated.

[1] -
https://github.com/wso2-extensions/identity-inbound-auth-oauth/blob/5.6.x/components/org.wso2.carbon.identity.oauth/src/main/java/org/wso2/carbon/identity/oauth2/model/CarbonOAuthAuthzRequest.java#L49

​

On Wed, Mar 14, 2018 at 7:52 PM, Sagara Gunathunga  wrote:

>
>
> On Wed, Mar 14, 2018 at 7:46 PM, Jayanga Kaushalya 
> wrote:
>
>> Hi Sagara,
>>
>> Yes I have suggested other teams also to follow the IS convention in [1].
>> APIM team told me offline that they already changed. Hope others will do
>> the same.
>>
>
> Great.
>
> Thanks !
>
>>
>> [1] [GDPR] Anonymization Tool default configurations/references are
>> differed over the Products
>>
>> Thanks!
>>
>> *Jayanga Kaushalya*
>> Senior Software Engineer
>> Mobile: +94777860160 <+94%2077%20786%200160>
>> WSO2 Inc. | http://wso2.com
>> lean.enterprise.middleware
>>
>>
>>
>> On Wed, Mar 14, 2018 at 7:37 PM, Sagara Gunathunga 
>> wrote:
>>
>>>
>>>
>>> On Wed, Mar 14, 2018 at 7:27 PM, Sathya Bandara  wrote:
>>>
 Hi all,

 We are calling-off this vote as we have found an issue,

- for user-mgt ui component in EI product
- in Windows environment

 Since we want to align same component versions among EI & IS, we will
 fix this and update versions in IS as well. Additionally we will fix the
 issue in README.txt along with this.

>>> Ruwan/Jayanga, shall we also look into the suggestion made by Lanka in
>>> the "GDPR compliance for WSO2 products" thread ?
>>>
>>> Thanks !
>>>
 We will do a RC2 and call for a vote soon.

 [1] https://github.com/wso2/product-ei/issues/2004

 On Wed, Mar 14, 2018 at 6:29 PM, Nilasini Thirunavukkarasu <
 nilas...@wso2.com> wrote:

> Hi,
>
> I have tested the following flows in mysql.
>
>- User management, role management (Primary + Secondary user store)
>- OIDC flow (password grant, authorization code)(Primary +
>Secondary user store)
>- consent management with SAML SSO for primary and secondary users.
>- SAML assertion encryption and response signing.
>
>
> I have tested the following flow with h2
>
>- federated scenario with two IS
>
> +1 to go ahead and release
>
>
> Thanks,
> Nila.
>
>
> On Wed, Mar 14, 2018 at 6:15 PM, Darshana Gunawardana <
> darsh...@wso2.com> wrote:
>
>> Hi Dilini,
>>
>> We will fix this, if we noted any blocker for RC1 release.. If not,
>> let's continue on the vote considering this is a known issue..
>>
>> Thanks,
>>
>> On Wed, Mar 14, 2018 at 6:05 PM, Dilini Gunatilake 
>> wrote:
>>
>>> Hi,
>>>
>>> The README .txt contains references to old documentation and few
>>> other issues which is reported in [1]. Better if we can fix those. WDUT?
>>>
>>> [1] https://github.com/wso2/product-is/issues/2945
>>>
>>> Regards,
>>> Dilini
>>>
>>>
>>>
>>> On Wed, Mar 14, 2018 at 5:23 PM, Farasath Ahamed >> > wrote:
>>>

 Tested Below scenario on the IS 5.5.0-RC1 pack with MSSQL database

- Create an OAuth app using Dynamic Client Registration endpoint
- Configured mandatory claims for the service provider
- Tested OIDC Implicit flow with user consent management enabled
- Verified that the user claims sent in the id_token are
filtered based on user consent.

 +1 to go ahead and release


 On Wed, Mar 14, 2018 at 11:16 AM, Sathya Bandara 
 wrote:

> Hi all,
>
> We are pleased to announce the first release candidate of WSO2
> Identity Server 5.5.0.
>
> This is the first release candidate (RC) of the WSO2 Identity
> Server 5.5.0 release.
>
>
> This release fixes the following issues
>
>- 5.5.0-RC1 fixes
>
> 
>- 5.5.0-Beta fixes
>
> 

Re: [Dev] Processing Big/Huge/Large files in wso2 using vfs.Facing issues

[Ruwan Abeykoon]

Hi Adithya,
Can you try this without the log mediator.
Log mediator is usually tries to decode the payload. We call that a content
aware mediator. The content aware mediators has the issue decoding large
payloads.

Cheers,
Ruwan

On Wed, Mar 14, 2018 at 6:43 PM, aditya shivankar <
shivankar.adit...@gmail.com> wrote:

> Respected Sir,
>
> Forgot to mention ,Sometimes I am getting OutOfMemoryError as well
>
> java.lang.OutOfMemoryError: Java heap space
> Dumping heap to C:/wso2ei-6.1.1/wso2ei-6.1.1/repository/logs/heap-dump.hprof
> ...
> Unable to create C:/wso2ei-6.1.1/wso2ei-6.1.1/repository/logs/heap-dump.hprof:
> File exists
> [2018-03-14 17:16:01,228] [EI-Core] ERROR - NativeWorkerPool Uncaught
> exception
> java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Unknown Source)
> at java.lang.AbstractStringBuilder.ensureCapacityInternal(Unknown Source)
> at java.lang.AbstractStringBuilder.append(Unknown Source)
> at java.lang.StringBuffer.append(Unknown Source)
> at org.apache.log4j.helpers.PatternParser$LiteralPatternConverter.
> format(PatternParser.java:419)
>
> With Regards,
> Aditya
>
> On Wed, Mar 14, 2018 at 4:46 PM, aditya shivankar <
> shivankar.adit...@gmail.com> wrote:
>
>> added the missing attachment from previous mail
>>
>> On Wed, Mar 14, 2018 at 4:44 PM, aditya shivankar <
>> shivankar.adit...@gmail.com> wrote:
>>
>>> Respected Sir/Madam,
>>>
>>> I am able to achieve below file processing using vfs, and datamapper.
>>> But when trying to process files more than size of 8 MB or more the flow is
>>> failing with out of memory. Please guide
>>>
>>> step 1. I am using vfs to read one xml file from one location.
>>> step 2. Then using datamapper to convert the xml file to csv.
>>> step 3. Then writing the converted output to another location.
>>>
>>>
>>> 
>>> http://ws.apache.org/ns/synapse;>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> >> type="STRING" value="true"/>
>>> >> type="STRING" value=""/>
>>> >> inputSchema="gov:datamapper/xmlToCsv1_inputSchema.json" inputType="XML"
>>> outputSchema="gov:datamapper/xmlToCsv1_outputSchema.json"
>>> outputType="CSV"/>
>>> >> name="transport.vfs.ReplyFileName" scope="transport" type="STRING"/>
>>> >> value="true"/>
>>> >> value="application/csv"/>
>>> >> scope="transport"/>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 50ms
>>> f
>>> ile:///C:/Flatfile/input
>>> application/xml
>>> MOVE
>>> file:///C:/Flatfile/failure
>>> MOVE
>>> .*\.xml
>>> disable
>>> file:///C:/Flatfile/orgFilesProcessedSuccessfully
>>> 
>>>
>>>
>>> sometimes it is not able to delete .lock files from input folder.
>>> sometimes timeout error.
>>>
>>> etc..
>>>
>>> Sample input attached.
>>>
>>> With regards,
>>> Aditya
>>>
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 Identity Server 5.5.0 RC1

[Sagara Gunathunga]

On Wed, Mar 14, 2018 at 7:46 PM, Jayanga Kaushalya 
wrote:

> Hi Sagara,
>
> Yes I have suggested other teams also to follow the IS convention in [1].
> APIM team told me offline that they already changed. Hope others will do
> the same.
>

Great.

Thanks !

>
> [1] [GDPR] Anonymization Tool default configurations/references are
> differed over the Products
>
> Thanks!
>
> *Jayanga Kaushalya*
> Senior Software Engineer
> Mobile: +94777860160 <+94%2077%20786%200160>
> WSO2 Inc. | http://wso2.com
> lean.enterprise.middleware
>
>
>
> On Wed, Mar 14, 2018 at 7:37 PM, Sagara Gunathunga 
> wrote:
>
>>
>>
>> On Wed, Mar 14, 2018 at 7:27 PM, Sathya Bandara  wrote:
>>
>>> Hi all,
>>>
>>> We are calling-off this vote as we have found an issue,
>>>
>>>- for user-mgt ui component in EI product
>>>- in Windows environment
>>>
>>> Since we want to align same component versions among EI & IS, we will
>>> fix this and update versions in IS as well. Additionally we will fix the
>>> issue in README.txt along with this.
>>>
>> Ruwan/Jayanga, shall we also look into the suggestion made by Lanka in
>> the "GDPR compliance for WSO2 products" thread ?
>>
>> Thanks !
>>
>>> We will do a RC2 and call for a vote soon.
>>>
>>> [1] https://github.com/wso2/product-ei/issues/2004
>>>
>>> On Wed, Mar 14, 2018 at 6:29 PM, Nilasini Thirunavukkarasu <
>>> nilas...@wso2.com> wrote:
>>>
 Hi,

 I have tested the following flows in mysql.

- User management, role management (Primary + Secondary user store)
- OIDC flow (password grant, authorization code)(Primary +
Secondary user store)
- consent management with SAML SSO for primary and secondary users.
- SAML assertion encryption and response signing.


 I have tested the following flow with h2

- federated scenario with two IS

 +1 to go ahead and release


 Thanks,
 Nila.


 On Wed, Mar 14, 2018 at 6:15 PM, Darshana Gunawardana <
 darsh...@wso2.com> wrote:

> Hi Dilini,
>
> We will fix this, if we noted any blocker for RC1 release.. If not,
> let's continue on the vote considering this is a known issue..
>
> Thanks,
>
> On Wed, Mar 14, 2018 at 6:05 PM, Dilini Gunatilake 
> wrote:
>
>> Hi,
>>
>> The README .txt contains references to old documentation and few
>> other issues which is reported in [1]. Better if we can fix those. WDUT?
>>
>> [1] https://github.com/wso2/product-is/issues/2945
>>
>> Regards,
>> Dilini
>>
>>
>>
>> On Wed, Mar 14, 2018 at 5:23 PM, Farasath Ahamed 
>> wrote:
>>
>>>
>>> Tested Below scenario on the IS 5.5.0-RC1 pack with MSSQL database
>>>
>>>- Create an OAuth app using Dynamic Client Registration endpoint
>>>- Configured mandatory claims for the service provider
>>>- Tested OIDC Implicit flow with user consent management enabled
>>>- Verified that the user claims sent in the id_token are
>>>filtered based on user consent.
>>>
>>> +1 to go ahead and release
>>>
>>>
>>> On Wed, Mar 14, 2018 at 11:16 AM, Sathya Bandara 
>>> wrote:
>>>
 Hi all,

 We are pleased to announce the first release candidate of WSO2
 Identity Server 5.5.0.

 This is the first release candidate (RC) of the WSO2 Identity
 Server 5.5.0 release.


 This release fixes the following issues

- 5.5.0-RC1 fixes

 
- 5.5.0-Beta fixes

 
- 5.5.0-Alpha3 fixes

 
- 5.5.0-Alpha2 fixes

 
- 5.5.0-Alpha fixes

 
- 5.5.0-M4 fixes

 
- 5.5.0-M3 fixes

 
- 5.5.0-M2 fixes

 
- 5.5.0-M1 fixes

 


 Source and distribution

 Runtime - https://github.com/wso2/produc
 

Re: [Dev] [Architecture] [VOTE] Release WSO2 Identity Server 5.5.0 RC1

[Sagara Gunathunga]

On Wed, Mar 14, 2018 at 7:46 PM, Jayanga Kaushalya 
wrote:

> Hi Sagara,
>
> Yes I have suggested other teams also to follow the IS convention in [1].
> APIM team told me offline that they already changed. Hope others will do
> the same.
>

Great.

Thanks !

>
> [1] [GDPR] Anonymization Tool default configurations/references are
> differed over the Products
>
> Thanks!
>
> *Jayanga Kaushalya*
> Senior Software Engineer
> Mobile: +94777860160 <+94%2077%20786%200160>
> WSO2 Inc. | http://wso2.com
> lean.enterprise.middleware
>
>
>
> On Wed, Mar 14, 2018 at 7:37 PM, Sagara Gunathunga 
> wrote:
>
>>
>>
>> On Wed, Mar 14, 2018 at 7:27 PM, Sathya Bandara  wrote:
>>
>>> Hi all,
>>>
>>> We are calling-off this vote as we have found an issue,
>>>
>>>- for user-mgt ui component in EI product
>>>- in Windows environment
>>>
>>> Since we want to align same component versions among EI & IS, we will
>>> fix this and update versions in IS as well. Additionally we will fix the
>>> issue in README.txt along with this.
>>>
>> Ruwan/Jayanga, shall we also look into the suggestion made by Lanka in
>> the "GDPR compliance for WSO2 products" thread ?
>>
>> Thanks !
>>
>>> We will do a RC2 and call for a vote soon.
>>>
>>> [1] https://github.com/wso2/product-ei/issues/2004
>>>
>>> On Wed, Mar 14, 2018 at 6:29 PM, Nilasini Thirunavukkarasu <
>>> nilas...@wso2.com> wrote:
>>>
 Hi,

 I have tested the following flows in mysql.

- User management, role management (Primary + Secondary user store)
- OIDC flow (password grant, authorization code)(Primary +
Secondary user store)
- consent management with SAML SSO for primary and secondary users.
- SAML assertion encryption and response signing.


 I have tested the following flow with h2

- federated scenario with two IS

 +1 to go ahead and release


 Thanks,
 Nila.


 On Wed, Mar 14, 2018 at 6:15 PM, Darshana Gunawardana <
 darsh...@wso2.com> wrote:

> Hi Dilini,
>
> We will fix this, if we noted any blocker for RC1 release.. If not,
> let's continue on the vote considering this is a known issue..
>
> Thanks,
>
> On Wed, Mar 14, 2018 at 6:05 PM, Dilini Gunatilake 
> wrote:
>
>> Hi,
>>
>> The README .txt contains references to old documentation and few
>> other issues which is reported in [1]. Better if we can fix those. WDUT?
>>
>> [1] https://github.com/wso2/product-is/issues/2945
>>
>> Regards,
>> Dilini
>>
>>
>>
>> On Wed, Mar 14, 2018 at 5:23 PM, Farasath Ahamed 
>> wrote:
>>
>>>
>>> Tested Below scenario on the IS 5.5.0-RC1 pack with MSSQL database
>>>
>>>- Create an OAuth app using Dynamic Client Registration endpoint
>>>- Configured mandatory claims for the service provider
>>>- Tested OIDC Implicit flow with user consent management enabled
>>>- Verified that the user claims sent in the id_token are
>>>filtered based on user consent.
>>>
>>> +1 to go ahead and release
>>>
>>>
>>> On Wed, Mar 14, 2018 at 11:16 AM, Sathya Bandara 
>>> wrote:
>>>
 Hi all,

 We are pleased to announce the first release candidate of WSO2
 Identity Server 5.5.0.

 This is the first release candidate (RC) of the WSO2 Identity
 Server 5.5.0 release.


 This release fixes the following issues

- 5.5.0-RC1 fixes

 
- 5.5.0-Beta fixes

 
- 5.5.0-Alpha3 fixes

 
- 5.5.0-Alpha2 fixes

 
- 5.5.0-Alpha fixes

 
- 5.5.0-M4 fixes

 
- 5.5.0-M3 fixes

 
- 5.5.0-M2 fixes

 
- 5.5.0-M1 fixes

 


 Source and distribution

 Runtime - https://github.com/wso2/produc
 

Re: [Dev] [Architecture] [VOTE] Release WSO2 Identity Server 5.5.0 RC1

[Jayanga Kaushalya]

Hi Sagara,

Yes I have suggested other teams also to follow the IS convention in [1].
APIM team told me offline that they already changed. Hope others will do
the same.

[1] [GDPR] Anonymization Tool default configurations/references are
differed over the Products

Thanks!

*Jayanga Kaushalya*
Senior Software Engineer
Mobile: +94777860160
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware



On Wed, Mar 14, 2018 at 7:37 PM, Sagara Gunathunga  wrote:

>
>
> On Wed, Mar 14, 2018 at 7:27 PM, Sathya Bandara  wrote:
>
>> Hi all,
>>
>> We are calling-off this vote as we have found an issue,
>>
>>- for user-mgt ui component in EI product
>>- in Windows environment
>>
>> Since we want to align same component versions among EI & IS, we will fix
>> this and update versions in IS as well. Additionally we will fix the issue
>> in README.txt along with this.
>>
> Ruwan/Jayanga, shall we also look into the suggestion made by Lanka in the
> "GDPR compliance for WSO2 products" thread ?
>
> Thanks !
>
>> We will do a RC2 and call for a vote soon.
>>
>> [1] https://github.com/wso2/product-ei/issues/2004
>>
>> On Wed, Mar 14, 2018 at 6:29 PM, Nilasini Thirunavukkarasu <
>> nilas...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> I have tested the following flows in mysql.
>>>
>>>- User management, role management (Primary + Secondary user store)
>>>- OIDC flow (password grant, authorization code)(Primary + Secondary
>>>user store)
>>>- consent management with SAML SSO for primary and secondary users.
>>>- SAML assertion encryption and response signing.
>>>
>>>
>>> I have tested the following flow with h2
>>>
>>>- federated scenario with two IS
>>>
>>> +1 to go ahead and release
>>>
>>>
>>> Thanks,
>>> Nila.
>>>
>>>
>>> On Wed, Mar 14, 2018 at 6:15 PM, Darshana Gunawardana >> > wrote:
>>>
 Hi Dilini,

 We will fix this, if we noted any blocker for RC1 release.. If not,
 let's continue on the vote considering this is a known issue..

 Thanks,

 On Wed, Mar 14, 2018 at 6:05 PM, Dilini Gunatilake 
 wrote:

> Hi,
>
> The README .txt contains references to old documentation and few other
> issues which is reported in [1]. Better if we can fix those. WDUT?
>
> [1] https://github.com/wso2/product-is/issues/2945
>
> Regards,
> Dilini
>
>
>
> On Wed, Mar 14, 2018 at 5:23 PM, Farasath Ahamed 
> wrote:
>
>>
>> Tested Below scenario on the IS 5.5.0-RC1 pack with MSSQL database
>>
>>- Create an OAuth app using Dynamic Client Registration endpoint
>>- Configured mandatory claims for the service provider
>>- Tested OIDC Implicit flow with user consent management enabled
>>- Verified that the user claims sent in the id_token are filtered
>>based on user consent.
>>
>> +1 to go ahead and release
>>
>>
>> On Wed, Mar 14, 2018 at 11:16 AM, Sathya Bandara 
>> wrote:
>>
>>> Hi all,
>>>
>>> We are pleased to announce the first release candidate of WSO2
>>> Identity Server 5.5.0.
>>>
>>> This is the first release candidate (RC) of the WSO2 Identity Server
>>> 5.5.0 release.
>>>
>>>
>>> This release fixes the following issues
>>>
>>>- 5.5.0-RC1 fixes
>>>
>>> 
>>>- 5.5.0-Beta fixes
>>>
>>> 
>>>- 5.5.0-Alpha3 fixes
>>>
>>> 
>>>- 5.5.0-Alpha2 fixes
>>>
>>> 
>>>- 5.5.0-Alpha fixes
>>>
>>> 
>>>- 5.5.0-M4 fixes
>>>
>>> 
>>>- 5.5.0-M3 fixes
>>>
>>> 
>>>- 5.5.0-M2 fixes
>>>
>>> 
>>>- 5.5.0-M1 fixes
>>>
>>> 
>>>
>>>
>>> Source and distribution
>>>
>>> Runtime - https://github.com/wso2/produc
>>> t-is/releases/tag/v5.5.0-rc1
>>> Analytics - https://github.com/wso2/analyt
>>> ics-is/releases/tag/v5.5.0-rc1
>>>
>>>
>>> Please download, test the product and vote.
>>>
>>> [+] Stable - go ahead and release
>>> [-] Broken - do not release (explain why)
>>>

Re: [Dev] [Architecture] [VOTE] Release WSO2 Identity Server 5.5.0 RC1

[Sagara Gunathunga]

On Wed, Mar 14, 2018 at 7:27 PM, Sathya Bandara  wrote:

> Hi all,
>
> We are calling-off this vote as we have found an issue,
>
>- for user-mgt ui component in EI product
>- in Windows environment
>
> Since we want to align same component versions among EI & IS, we will fix
> this and update versions in IS as well. Additionally we will fix the issue
> in README.txt along with this.
>
Ruwan/Jayanga, shall we also look into the suggestion made by Lanka in the
"GDPR compliance for WSO2 products" thread ?

Thanks !

> We will do a RC2 and call for a vote soon.
>
> [1] https://github.com/wso2/product-ei/issues/2004
>
> On Wed, Mar 14, 2018 at 6:29 PM, Nilasini Thirunavukkarasu <
> nilas...@wso2.com> wrote:
>
>> Hi,
>>
>> I have tested the following flows in mysql.
>>
>>- User management, role management (Primary + Secondary user store)
>>- OIDC flow (password grant, authorization code)(Primary + Secondary
>>user store)
>>- consent management with SAML SSO for primary and secondary users.
>>- SAML assertion encryption and response signing.
>>
>>
>> I have tested the following flow with h2
>>
>>- federated scenario with two IS
>>
>> +1 to go ahead and release
>>
>>
>> Thanks,
>> Nila.
>>
>>
>> On Wed, Mar 14, 2018 at 6:15 PM, Darshana Gunawardana 
>> wrote:
>>
>>> Hi Dilini,
>>>
>>> We will fix this, if we noted any blocker for RC1 release.. If not,
>>> let's continue on the vote considering this is a known issue..
>>>
>>> Thanks,
>>>
>>> On Wed, Mar 14, 2018 at 6:05 PM, Dilini Gunatilake 
>>> wrote:
>>>
 Hi,

 The README .txt contains references to old documentation and few other
 issues which is reported in [1]. Better if we can fix those. WDUT?

 [1] https://github.com/wso2/product-is/issues/2945

 Regards,
 Dilini



 On Wed, Mar 14, 2018 at 5:23 PM, Farasath Ahamed 
 wrote:

>
> Tested Below scenario on the IS 5.5.0-RC1 pack with MSSQL database
>
>- Create an OAuth app using Dynamic Client Registration endpoint
>- Configured mandatory claims for the service provider
>- Tested OIDC Implicit flow with user consent management enabled
>- Verified that the user claims sent in the id_token are filtered
>based on user consent.
>
> +1 to go ahead and release
>
>
> On Wed, Mar 14, 2018 at 11:16 AM, Sathya Bandara 
> wrote:
>
>> Hi all,
>>
>> We are pleased to announce the first release candidate of WSO2
>> Identity Server 5.5.0.
>>
>> This is the first release candidate (RC) of the WSO2 Identity Server
>> 5.5.0 release.
>>
>>
>> This release fixes the following issues
>>
>>- 5.5.0-RC1 fixes
>>
>> 
>>- 5.5.0-Beta fixes
>>
>> 
>>- 5.5.0-Alpha3 fixes
>>
>> 
>>- 5.5.0-Alpha2 fixes
>>
>> 
>>- 5.5.0-Alpha fixes
>>
>> 
>>- 5.5.0-M4 fixes
>>
>> 
>>- 5.5.0-M3 fixes
>>
>> 
>>- 5.5.0-M2 fixes
>>
>> 
>>- 5.5.0-M1 fixes
>>
>> 
>>
>>
>> Source and distribution
>>
>> Runtime - https://github.com/wso2/produc
>> t-is/releases/tag/v5.5.0-rc1
>> Analytics - https://github.com/wso2/analyt
>> ics-is/releases/tag/v5.5.0-rc1
>>
>>
>> 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 -
>>
>> --
>> Sathya Bandara
>> Software Engineer
>> WSO2 Inc. http://wso2.com
>> Mobile: (+94) 715 360 421 <+94%2071%20411%205032>
>>
>> <+94%2071%20411%205032>
>>
>
>
>
> --
> Farasath Ahamed
> Senior Software Engineer, WSO2 Inc.; http://wso2.com
> Mobile: +94777603866
> Blog: blog.farazath.com
> Twitter: @farazath619 
> 
>
>
>
>
> ___
> Architecture 

Re: [Dev] [Architecture] [VOTE] Release WSO2 Identity Server 5.5.0 RC1

[Sathya Bandara]

Hi all,

We are calling-off this vote as we have found an issue,

   - for user-mgt ui component in EI product
   - in Windows environment

Since we want to align same component versions among EI & IS, we will fix
this and update versions in IS as well. Additionally we will fix the issue
in README.txt along with this.
We will do a RC2 and call for a vote soon.

[1] https://github.com/wso2/product-ei/issues/2004

On Wed, Mar 14, 2018 at 6:29 PM, Nilasini Thirunavukkarasu <
nilas...@wso2.com> wrote:

> Hi,
>
> I have tested the following flows in mysql.
>
>- User management, role management (Primary + Secondary user store)
>- OIDC flow (password grant, authorization code)(Primary + Secondary
>user store)
>- consent management with SAML SSO for primary and secondary users.
>- SAML assertion encryption and response signing.
>
>
> I have tested the following flow with h2
>
>- federated scenario with two IS
>
> +1 to go ahead and release
>
>
> Thanks,
> Nila.
>
>
> On Wed, Mar 14, 2018 at 6:15 PM, Darshana Gunawardana 
> wrote:
>
>> Hi Dilini,
>>
>> We will fix this, if we noted any blocker for RC1 release.. If not, let's
>> continue on the vote considering this is a known issue..
>>
>> Thanks,
>>
>> On Wed, Mar 14, 2018 at 6:05 PM, Dilini Gunatilake 
>> wrote:
>>
>>> Hi,
>>>
>>> The README .txt contains references to old documentation and few other
>>> issues which is reported in [1]. Better if we can fix those. WDUT?
>>>
>>> [1] https://github.com/wso2/product-is/issues/2945
>>>
>>> Regards,
>>> Dilini
>>>
>>>
>>>
>>> On Wed, Mar 14, 2018 at 5:23 PM, Farasath Ahamed 
>>> wrote:
>>>

 Tested Below scenario on the IS 5.5.0-RC1 pack with MSSQL database

- Create an OAuth app using Dynamic Client Registration endpoint
- Configured mandatory claims for the service provider
- Tested OIDC Implicit flow with user consent management enabled
- Verified that the user claims sent in the id_token are filtered
based on user consent.

 +1 to go ahead and release


 On Wed, Mar 14, 2018 at 11:16 AM, Sathya Bandara 
 wrote:

> Hi all,
>
> We are pleased to announce the first release candidate of WSO2
> Identity Server 5.5.0.
>
> This is the first release candidate (RC) of the WSO2 Identity Server
> 5.5.0 release.
>
>
> This release fixes the following issues
>
>- 5.5.0-RC1 fixes
>
> 
>- 5.5.0-Beta fixes
>
> 
>- 5.5.0-Alpha3 fixes
>
> 
>- 5.5.0-Alpha2 fixes
>
> 
>- 5.5.0-Alpha fixes
>
> 
>- 5.5.0-M4 fixes
>
> 
>- 5.5.0-M3 fixes
>
> 
>- 5.5.0-M2 fixes
>
> 
>- 5.5.0-M1 fixes
>
> 
>
>
> Source and distribution
>
> Runtime - https://github.com/wso2/produc
> t-is/releases/tag/v5.5.0-rc1
> Analytics - https://github.com/wso2/analyt
> ics-is/releases/tag/v5.5.0-rc1
>
>
> 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 -
>
> --
> Sathya Bandara
> Software Engineer
> WSO2 Inc. http://wso2.com
> Mobile: (+94) 715 360 421 <+94%2071%20411%205032>
>
> <+94%2071%20411%205032>
>



 --
 Farasath Ahamed
 Senior Software Engineer, WSO2 Inc.; http://wso2.com
 Mobile: +94777603866
 Blog: blog.farazath.com
 Twitter: @farazath619 
 




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


>>>
>>>
>>> --
>>>
>>> *Dilini GunatilakeSoftware Engineer - QA Team*
>>> Mobile : +94771162518 <+94%2077%20116%202518>
>>> dili...@wso2.com
>>>
>>>
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> 

Re: [Dev] Processing Big/Huge/Large files in wso2 using vfs.Facing issues

[aditya shivankar]

Respected Sir,

Forgot to mention ,Sometimes I am getting OutOfMemoryError as well

java.lang.OutOfMemoryError: Java heap space
Dumping heap to
C:/wso2ei-6.1.1/wso2ei-6.1.1/repository/logs/heap-dump.hprof ...
Unable to create
C:/wso2ei-6.1.1/wso2ei-6.1.1/repository/logs/heap-dump.hprof: File exists
[2018-03-14 17:16:01,228] [EI-Core] ERROR - NativeWorkerPool Uncaught
exception
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Unknown Source)
at java.lang.AbstractStringBuilder.ensureCapacityInternal(Unknown Source)
at java.lang.AbstractStringBuilder.append(Unknown Source)
at java.lang.StringBuffer.append(Unknown Source)
at
org.apache.log4j.helpers.PatternParser$LiteralPatternConverter.format(PatternParser.java:419)

With Regards,
Aditya

On Wed, Mar 14, 2018 at 4:46 PM, aditya shivankar <
shivankar.adit...@gmail.com> wrote:

> added the missing attachment from previous mail
>
> On Wed, Mar 14, 2018 at 4:44 PM, aditya shivankar <
> shivankar.adit...@gmail.com> wrote:
>
>> Respected Sir/Madam,
>>
>> I am able to achieve below file processing using vfs, and datamapper. But
>> when trying to process files more than size of 8 MB or more the flow is
>> failing with out of memory. Please guide
>>
>> step 1. I am using vfs to read one xml file from one location.
>> step 2. Then using datamapper to convert the xml file to csv.
>> step 3. Then writing the converted output to another location.
>>
>>
>> 
>> http://ws.apache.org/ns/synapse;>
>> 
>> 
>> 
>> 
>> 
>> > type="STRING" value="true"/>
>> > value=""/>
>> > inputSchema="gov:datamapper/xmlToCsv1_inputSchema.json" inputType="XML"
>> outputSchema="gov:datamapper/xmlToCsv1_outputSchema.json"
>> outputType="CSV"/>
>> > name="transport.vfs.ReplyFileName" scope="transport" type="STRING"/>
>> > value="true"/>
>> > value="application/csv"/>
>> > scope="transport"/>
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 50ms
>> f
>> ile:///C:/Flatfile/input
>> application/xml
>> MOVE
>> file:///C:/Flatfile/
>> failure
>> MOVE
>> .*\.xml
>> disable
>> file:///C:/Flatfile/orgFilesProcessedSuccessfully
>> 
>>
>>
>> sometimes it is not able to delete .lock files from input folder.
>> sometimes timeout error.
>>
>> etc..
>>
>> Sample input attached.
>>
>> With regards,
>> Aditya
>>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 Identity Server 5.5.0 RC1

[Nilasini Thirunavukkarasu]

Hi,

I have tested the following flows in mysql.

   - User management, role management (Primary + Secondary user store)
   - OIDC flow (password grant, authorization code)(Primary + Secondary
   user store)
   - consent management with SAML SSO for primary and secondary users.
   - SAML assertion encryption and response signing.


I have tested the following flow with h2

   - federated scenario with two IS

+1 to go ahead and release


Thanks,
Nila.


On Wed, Mar 14, 2018 at 6:15 PM, Darshana Gunawardana 
wrote:

> Hi Dilini,
>
> We will fix this, if we noted any blocker for RC1 release.. If not, let's
> continue on the vote considering this is a known issue..
>
> Thanks,
>
> On Wed, Mar 14, 2018 at 6:05 PM, Dilini Gunatilake 
> wrote:
>
>> Hi,
>>
>> The README .txt contains references to old documentation and few other
>> issues which is reported in [1]. Better if we can fix those. WDUT?
>>
>> [1] https://github.com/wso2/product-is/issues/2945
>>
>> Regards,
>> Dilini
>>
>>
>>
>> On Wed, Mar 14, 2018 at 5:23 PM, Farasath Ahamed 
>> wrote:
>>
>>>
>>> Tested Below scenario on the IS 5.5.0-RC1 pack with MSSQL database
>>>
>>>- Create an OAuth app using Dynamic Client Registration endpoint
>>>- Configured mandatory claims for the service provider
>>>- Tested OIDC Implicit flow with user consent management enabled
>>>- Verified that the user claims sent in the id_token are filtered
>>>based on user consent.
>>>
>>> +1 to go ahead and release
>>>
>>>
>>> On Wed, Mar 14, 2018 at 11:16 AM, Sathya Bandara 
>>> wrote:
>>>
 Hi all,

 We are pleased to announce the first release candidate of WSO2 Identity
 Server 5.5.0.

 This is the first release candidate (RC) of the WSO2 Identity Server
 5.5.0 release.


 This release fixes the following issues

- 5.5.0-RC1 fixes

 
- 5.5.0-Beta fixes

 
- 5.5.0-Alpha3 fixes

 
- 5.5.0-Alpha2 fixes

 
- 5.5.0-Alpha fixes

 
- 5.5.0-M4 fixes

 
- 5.5.0-M3 fixes

 
- 5.5.0-M2 fixes

 
- 5.5.0-M1 fixes

 


 Source and distribution

 Runtime - https://github.com/wso2/produc
 t-is/releases/tag/v5.5.0-rc1
 Analytics - https://github.com/wso2/analyt
 ics-is/releases/tag/v5.5.0-rc1


 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 -

 --
 Sathya Bandara
 Software Engineer
 WSO2 Inc. http://wso2.com
 Mobile: (+94) 715 360 421 <+94%2071%20411%205032>

 <+94%2071%20411%205032>

>>>
>>>
>>>
>>> --
>>> Farasath Ahamed
>>> Senior Software Engineer, WSO2 Inc.; http://wso2.com
>>> Mobile: +94777603866
>>> Blog: blog.farazath.com
>>> Twitter: @farazath619 
>>> 
>>>
>>>
>>>
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>>
>> *Dilini GunatilakeSoftware Engineer - QA Team*
>> Mobile : +94771162518 <+94%2077%20116%202518>
>> dili...@wso2.com
>>
>>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Regards,
>
>
> *Darshana Gunawardana*Technical Lead
> WSO2 Inc.; http://wso2.com
>
> *E-mail: darsh...@wso2.com *
> *Mobile: +94718566859 <+94%2071%20856%206859>*Lean . Enterprise .
> Middleware
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Nilasini Thirunavukkarasu
Software Engineer - WSO2

Email : nilas...@wso2.com
Mobile : +94775241823
Web : http://wso2.com/



___
Dev mailing list

Re: [Dev] [Architecture] [VOTE] Release WSO2 Identity Server 5.5.0 RC1

[Darshana Gunawardana]

Hi Dilini,

We will fix this, if we noted any blocker for RC1 release.. If not, let's
continue on the vote considering this is a known issue..

Thanks,

On Wed, Mar 14, 2018 at 6:05 PM, Dilini Gunatilake  wrote:

> Hi,
>
> The README .txt contains references to old documentation and few other
> issues which is reported in [1]. Better if we can fix those. WDUT?
>
> [1] https://github.com/wso2/product-is/issues/2945
>
> Regards,
> Dilini
>
>
>
> On Wed, Mar 14, 2018 at 5:23 PM, Farasath Ahamed 
> wrote:
>
>>
>> Tested Below scenario on the IS 5.5.0-RC1 pack with MSSQL database
>>
>>- Create an OAuth app using Dynamic Client Registration endpoint
>>- Configured mandatory claims for the service provider
>>- Tested OIDC Implicit flow with user consent management enabled
>>- Verified that the user claims sent in the id_token are filtered
>>based on user consent.
>>
>> +1 to go ahead and release
>>
>>
>> On Wed, Mar 14, 2018 at 11:16 AM, Sathya Bandara  wrote:
>>
>>> Hi all,
>>>
>>> We are pleased to announce the first release candidate of WSO2 Identity
>>> Server 5.5.0.
>>>
>>> This is the first release candidate (RC) of the WSO2 Identity Server
>>> 5.5.0 release.
>>>
>>>
>>> This release fixes the following issues
>>>
>>>- 5.5.0-RC1 fixes
>>>
>>> 
>>>- 5.5.0-Beta fixes
>>>
>>> 
>>>- 5.5.0-Alpha3 fixes
>>>
>>> 
>>>- 5.5.0-Alpha2 fixes
>>>
>>> 
>>>- 5.5.0-Alpha fixes
>>>
>>> 
>>>- 5.5.0-M4 fixes
>>>
>>> 
>>>- 5.5.0-M3 fixes
>>>
>>> 
>>>- 5.5.0-M2 fixes
>>>
>>> 
>>>- 5.5.0-M1 fixes
>>>
>>> 
>>>
>>>
>>> Source and distribution
>>>
>>> Runtime - https://github.com/wso2/product-is/releases/tag/v5.5.0-rc1
>>> Analytics - https://github.com/wso2/analyt
>>> ics-is/releases/tag/v5.5.0-rc1
>>>
>>>
>>> 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 -
>>>
>>> --
>>> Sathya Bandara
>>> Software Engineer
>>> WSO2 Inc. http://wso2.com
>>> Mobile: (+94) 715 360 421 <+94%2071%20411%205032>
>>>
>>> <+94%2071%20411%205032>
>>>
>>
>>
>>
>> --
>> Farasath Ahamed
>> Senior Software Engineer, WSO2 Inc.; http://wso2.com
>> Mobile: +94777603866
>> Blog: blog.farazath.com
>> Twitter: @farazath619 
>> 
>>
>>
>>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
>
> *Dilini GunatilakeSoftware Engineer - QA Team*
> Mobile : +94771162518 <+94%2077%20116%202518>
> dili...@wso2.com
>
>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Regards,


*Darshana Gunawardana*Technical Lead
WSO2 Inc.; http://wso2.com

*E-mail: darsh...@wso2.com *
*Mobile: +94718566859*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 Identity Server 5.5.0 RC1

[Dilini Gunatilake]

Hi,

The README .txt contains references to old documentation and few other
issues which is reported in [1]. Better if we can fix those. WDUT?

[1] https://github.com/wso2/product-is/issues/2945

Regards,
Dilini



On Wed, Mar 14, 2018 at 5:23 PM, Farasath Ahamed  wrote:

>
> Tested Below scenario on the IS 5.5.0-RC1 pack with MSSQL database
>
>- Create an OAuth app using Dynamic Client Registration endpoint
>- Configured mandatory claims for the service provider
>- Tested OIDC Implicit flow with user consent management enabled
>- Verified that the user claims sent in the id_token are filtered
>based on user consent.
>
> +1 to go ahead and release
>
>
> On Wed, Mar 14, 2018 at 11:16 AM, Sathya Bandara  wrote:
>
>> Hi all,
>>
>> We are pleased to announce the first release candidate of WSO2 Identity
>> Server 5.5.0.
>>
>> This is the first release candidate (RC) of the WSO2 Identity Server
>> 5.5.0 release.
>>
>>
>> This release fixes the following issues
>>
>>- 5.5.0-RC1 fixes
>>
>> 
>>- 5.5.0-Beta fixes
>>
>> 
>>- 5.5.0-Alpha3 fixes
>>
>> 
>>- 5.5.0-Alpha2 fixes
>>
>> 
>>- 5.5.0-Alpha fixes
>>
>> 
>>- 5.5.0-M4 fixes
>>
>> 
>>- 5.5.0-M3 fixes
>>
>> 
>>- 5.5.0-M2 fixes
>>
>> 
>>- 5.5.0-M1 fixes
>>
>> 
>>
>>
>> Source and distribution
>>
>> Runtime - https://github.com/wso2/product-is/releases/tag/v5.5.0-rc1
>> Analytics - https://github.com/wso2/analyt
>> ics-is/releases/tag/v5.5.0-rc1
>>
>>
>> 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 -
>>
>> --
>> Sathya Bandara
>> Software Engineer
>> WSO2 Inc. http://wso2.com
>> Mobile: (+94) 715 360 421 <+94%2071%20411%205032>
>>
>> <+94%2071%20411%205032>
>>
>
>
>
> --
> Farasath Ahamed
> Senior Software Engineer, WSO2 Inc.; http://wso2.com
> Mobile: +94777603866
> Blog: blog.farazath.com
> Twitter: @farazath619 
> 
>
>
>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*Dilini GunatilakeSoftware Engineer - QA Team*
Mobile : +94771162518 <+94%2077%20116%202518>
dili...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Identity server installation

[Isura Karunaratne]

Hi Asanka,


   - Go to the
   https://wso2.com/identity-and-access-management/previous-releases
   - Select IS 5.0.0
   - Click on the Service Pack to download the  IS 5.0.0 SP1

Thanks
Isura.

On Tue, Mar 6, 2018 at 8:12 PM, Asanka Anthony 
wrote:

> Where we can download the WSO2 Identity Server 5.0.0 SP1 pack?please advice
>
> Thanks
> Anthony
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Isura Dilhara Karunaratne*
Associate Technical Lead | WSO2
Email: is...@wso2.com
Mob : +94 772 254 810
Blog : http://isurad.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Identity Server 5.5.0 RC1

[Farasath Ahamed]

Tested Below scenario on the IS 5.5.0-RC1 pack with MSSQL database

   - Create an OAuth app using Dynamic Client Registration endpoint
   - Configured mandatory claims for the service provider
   - Tested OIDC Implicit flow with user consent management enabled
   - Verified that the user claims sent in the id_token are filtered based
   on user consent.

+1 to go ahead and release


On Wed, Mar 14, 2018 at 11:16 AM, Sathya Bandara  wrote:

> Hi all,
>
> We are pleased to announce the first release candidate of WSO2 Identity
> Server 5.5.0.
>
> This is the first release candidate (RC) of the WSO2 Identity Server 5.5.0
> release.
>
>
> This release fixes the following issues
>
>- 5.5.0-RC1 fixes
>
> 
>- 5.5.0-Beta fixes
>
> 
>- 5.5.0-Alpha3 fixes
>
> 
>- 5.5.0-Alpha2 fixes
>
> 
>- 5.5.0-Alpha fixes
>
> 
>- 5.5.0-M4 fixes
>
> 
>- 5.5.0-M3 fixes
>
> 
>- 5.5.0-M2 fixes
>
> 
>- 5.5.0-M1 fixes
>
> 
>
>
> Source and distribution
>
> Runtime - https://github.com/wso2/product-is/releases/tag/v5.5.0-rc1
> Analytics - https://github.com/wso2/analytics-is/releases/tag/v5.
> 5.0-rc1
>
>
> 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 -
>
> --
> Sathya Bandara
> Software Engineer
> WSO2 Inc. http://wso2.com
> Mobile: (+94) 715 360 421 <+94%2071%20411%205032>
>
> <+94%2071%20411%205032>
>



-- 
Farasath Ahamed
Senior Software Engineer, WSO2 Inc.; http://wso2.com
Mobile: +94777603866
Blog: blog.farazath.com
Twitter: @farazath619 

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

[Dev] Processing Big/Huge/Large files in wso2 using vfs.Facing issues

[aditya shivankar]

Respected Sir/Madam,

I am able to achieve below file processing using vfs, and datamapper. But
when trying to process files more than size of 8 MB or more the flow is
failing with out of memory. Please guide

step 1. I am using vfs to read one xml file from one location.
step 2. Then using datamapper to convert the xml file to csv.
step 3. Then writing the converted output to another location.



http://ws.apache.org/ns/synapse;>





















50ms
file:///C:/Flatfile/input
application/xml
MOVE
file:///C:/Flatfile/failure
MOVE
.*\.xml
disable
file:///C:/Flatfile/orgFilesProcessedSuccessfully



sometimes it is not able to delete .lock files from input folder.
sometimes timeout error.

etc..

Sample input attached.

With regards,
Aditya
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 DAS Analytics

[KasunG Gajasinghe]

Please check this one.. [1] Each wso2 product has a user-mgt.xml. So, you
can add your userstore into that file. This duplicates the userstore
configuration.

Other option is to enable single-sign-on, and use an identity provider like
WSO2 IS for that purpose.

[1] https://docs.wso2.com/display/IS541/Configuring+the+Primary+User+Store

On Wed, Mar 14, 2018 at 3:12 PM, Pendekal Sanketh <
pendekal.sank...@bridgesgi.com> wrote:

> Thank you,
>
>  If there's any tutorial for that please do share.
> --
> *From:* KasunG Gajasinghe 
> *Sent:* Wednesday, March 14, 2018 3:11:05 PM
> *To:* Pendekal Sanketh
>
> *Cc:* WSO2 Developers' List
> *Subject:* Re: [Dev] WSO2 DAS Analytics
>
>
> Yes, you can share the userstores across any WSO2 Carbon products.
>
> On Wed, Mar 14, 2018 at 2:58 PM, Pendekal Sanketh <
> pendekal.sank...@bridgesgi.com> wrote:
>
>  I need to know if we can share the user store between WSO2 DAS and
> WSO2 EI?
> --
> *From:* Pendekal Sanketh
> *Sent:* Thursday, March 8, 2018 3:18:38 PM
> *To:* kas...@wso2.com
> *Cc:* WSO2 Developers' List
>
> *Subject:* Re: [Dev] WSO2 DAS Analytics
>
>
> Thank you.
>
>
> And on last thing I need to know if we can share the user store between
> DAS and EI?
>
>
>
> --
> *From:* KasunG Gajasinghe 
> *Sent:* Thursday, March 8, 2018 3:09 PM
> *To:* Gihan Anuruddha
> *Cc:* Yohanna Fernando; Pendekal Sanketh; WSO2 Developers' List
> *Subject:* Re: [Dev] WSO2 DAS Analytics
>
> Hi Pendekal,
>
> Usage Plan Information only taken into consideration if you do a
> on-premise Stratos Cloud deployment. This is not the case for you.
> Therefore, you can disregard that part of the configuration. I think the
> usage plan should have been called something like 'default'.
>
>
> On Thu, Mar 8, 2018 at 2:36 PM, Gihan Anuruddha  wrote:
>
> EI analytics do not support any customization. You need to use DAS for all
> the customization use cases.
>
> On Mon, Mar 5, 2018 at 2:47 PM, Yohanna Fernando  wrote:
>
> Hi Sanketh,
>
> I have forwarded your query to dev@wso2.org.
>
> Thanks,
>
> Yohanna
>
>
>
> On Thu, Mar 1, 2018 at 11:10 PM, Pendekal Sanketh <
> pendekal.sank...@bridgesgi.com> wrote:
>
> Hey,
>
> I have been going through WSO2 das analytics session. I found an tab
> for 'mutlitenancy' in DAS console. Under this section I found Usage Plan
> Information which had only DEMO option, are there any other plans
> available? If so, please notify me about it.
>
> And in EI analytics console, I found it's not possible to simulate events
> outside EI,i.e, I was unable to send the payload info to my custom created
> datasource and I was unable to generate my custom widget in EI analytics
> console dashboard. I would like to know why is that and what would be
> possible solution?
>
>
> Thank you,
>
> Regards
>
> Sanketh
> --
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> It may also be privileged or otherwise protected by work product immunity
> or other legal rules. If you have received it by mistake, please let us
> know by e-mail reply and delete it from your system; you may not copy this
> message or disclose its contents to anyone.
>
>
>
>
> --
> Yohanna Fernando
> Training & Certification
> WSO2 Inc.
> http://wso2.com
>
> E-mail: yoha...@wso2.com
> Cell: +94779021159 <077%20902%201159>
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
>
>
> --
> W.G. Gihan Anuruddha
> Associate Technical Lead | WSO2, Inc.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
>
>
> --
>
> *Kasun Gajasinghe *Associate Technical Lead, WSO2 Inc.
> email: kasung AT spamfree wso2.com
> linked-in: http://lk.linkedin.com/in/gajasinghe
> 
> Kasun Gajasinghe - Associate Technical Lead - Identity & Access Management
> - WSO2 | LinkedIn 
> lk.linkedin.com
> View Kasun Gajasinghe’s professional profile on LinkedIn. LinkedIn is the
> world's largest business network, helping professionals like Kasun
> Gajasinghe discover inside connections to recommended job candidates,
> industry experts, and business partners.
>
>
> blog: http://kasunbg.org
> phone: +1 650-745-4499 <+1%20650-745-4499>, 77 678 0813
>
> --
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> It may also be privileged or otherwise protected by work product immunity
> or other legal rules. If you have received it by mistake, please let us
> know by e-mail reply and delete 

Re: [Dev] WSO2 DAS Analytics

[KasunG Gajasinghe]

Yes, you can share the userstores across any WSO2 Carbon products.

On Wed, Mar 14, 2018 at 2:58 PM, Pendekal Sanketh <
pendekal.sank...@bridgesgi.com> wrote:

>  I need to know if we can share the user store between WSO2 DAS and
> WSO2 EI?
> --
> *From:* Pendekal Sanketh
> *Sent:* Thursday, March 8, 2018 3:18:38 PM
> *To:* kas...@wso2.com
> *Cc:* WSO2 Developers' List
>
> *Subject:* Re: [Dev] WSO2 DAS Analytics
>
>
> Thank you.
>
>
> And on last thing I need to know if we can share the user store between
> DAS and EI?
>
>
>
> --
> *From:* KasunG Gajasinghe 
> *Sent:* Thursday, March 8, 2018 3:09 PM
> *To:* Gihan Anuruddha
> *Cc:* Yohanna Fernando; Pendekal Sanketh; WSO2 Developers' List
> *Subject:* Re: [Dev] WSO2 DAS Analytics
>
> Hi Pendekal,
>
> Usage Plan Information only taken into consideration if you do a
> on-premise Stratos Cloud deployment. This is not the case for you.
> Therefore, you can disregard that part of the configuration. I think the
> usage plan should have been called something like 'default'.
>
>
> On Thu, Mar 8, 2018 at 2:36 PM, Gihan Anuruddha  wrote:
>
> EI analytics do not support any customization. You need to use DAS for all
> the customization use cases.
>
> On Mon, Mar 5, 2018 at 2:47 PM, Yohanna Fernando  wrote:
>
> Hi Sanketh,
>
> I have forwarded your query to dev@wso2.org.
>
> Thanks,
>
> Yohanna
>
>
>
> On Thu, Mar 1, 2018 at 11:10 PM, Pendekal Sanketh <
> pendekal.sank...@bridgesgi.com> wrote:
>
> Hey,
>
> I have been going through WSO2 das analytics session. I found an tab
> for 'mutlitenancy' in DAS console. Under this section I found Usage Plan
> Information which had only DEMO option, are there any other plans
> available? If so, please notify me about it.
>
> And in EI analytics console, I found it's not possible to simulate events
> outside EI,i.e, I was unable to send the payload info to my custom created
> datasource and I was unable to generate my custom widget in EI analytics
> console dashboard. I would like to know why is that and what would be
> possible solution?
>
>
> Thank you,
>
> Regards
>
> Sanketh
> --
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> It may also be privileged or otherwise protected by work product immunity
> or other legal rules. If you have received it by mistake, please let us
> know by e-mail reply and delete it from your system; you may not copy this
> message or disclose its contents to anyone.
>
>
>
>
> --
> Yohanna Fernando
> Training & Certification
> WSO2 Inc.
> http://wso2.com
>
> E-mail: yoha...@wso2.com
> Cell: +94779021159 <077%20902%201159>
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
>
>
> --
> W.G. Gihan Anuruddha
> Associate Technical Lead | WSO2, Inc.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
>
>
> --
>
> *Kasun Gajasinghe *Associate Technical Lead, WSO2 Inc.
> email: kasung AT spamfree wso2.com
> linked-in: http://lk.linkedin.com/in/gajasinghe
> 
> Kasun Gajasinghe - Associate Technical Lead - Identity & Access Management
> - WSO2 | LinkedIn 
> lk.linkedin.com
> View Kasun Gajasinghe’s professional profile on LinkedIn. LinkedIn is the
> world's largest business network, helping professionals like Kasun
> Gajasinghe discover inside connections to recommended job candidates,
> industry experts, and business partners.
>
>
> blog: http://kasunbg.org
> phone: +1 650-745-4499 <+1%20650-745-4499>, 77 678 0813
>
> --
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> It may also be privileged or otherwise protected by work product immunity
> or other legal rules. If you have received it by mistake, please let us
> know by e-mail reply and delete it from your system; you may not copy this
> message or disclose its contents to anyone.
>



-- 

*Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
phone: +1 650-745-4499, 77 678 0813
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev