Re: [Dev] [AppM] SAML response signature validation in tenants

[Kalpa Welivitigoda]

Hi Rushmin,

You can find the SSO implementation in AS 6.0.0 from
https://github.com/wso2/product-as/tree/master/modules/webapp-security

On Fri, Aug 19, 2016 at 10:25 AM, Johann Nallathamby 
wrote:

> This is what we have the SSO agent for.
>
> @Rushmin, did you check the SSOAgent code? This was improved recently also
> and is used in AS 6.0. The goal of the implementation was to make it a
> library to be used everywhere in the platform. Can you please check on
> that? If there are any limitations we need to fix that library and try to
> use it everywhere we need it.
>
> Please check with Kernel team where to get this and use this.
>
> On Fri, Aug 19, 2016 at 9:56 AM, Ishara Karunarathna 
> wrote:
>
>> Hi,
>>
>> On Fri, Aug 19, 2016 at 9:47 AM, Darshana Gunawardana 
>> wrote:
>>
>>>
>>>
>>> On Thu, Aug 18, 2016 at 4:43 PM, Rushmin Fernando 
>>> wrote:
>>>

 In current App Manager the service providers of tenants are getting
 created in the super tenant space.

 We are in the process of creating the service providers in the relevant
 tenants.

 In the app manager gateway, we use SAML SSO to authenticate the users,
 and the aforementioned service providers are used.

 When it comes to validating the the SAML response signature, I can see
 that we can re-use
 *org.wso2.carbon.identity.sso.saml.util.SAMLSSOUtil::getX509CredentialImplForTenant()*

 As per the code, it uses the tenant key store to get the certificates.
 And we can get the certificate by using the tenant name as the alias

 @IS team, do you see any issues with re-using this code in our gateway ?

>>>
>>> Using this util makes gateway -which is a client side(sp) component-
>>> depends on the SAML component -which is server side(idp) component-
>>>
>>> IMO, its not nice to have that dependency. Once example is, this
>>> dependency will expose you a samlsso (idp) endpoint from the gateway. And
>>> also gateway profile would need to have saml components and makes you to
>>> have whole framework related dependencies as well.
>>>
>>> Thinking about client side (sp) components which already doing this
>>> there are two components we have in wso2 platform.
>>> 1. Carbon SAML authenticator : https://github.com/wso2-exte
>>> nsions/identity-carbon-auth-saml2
>>> 2. AS SSO valve : https://github.com/wso2/carb
>>> on-deployment/blob/4.7.x/components/webapp-mgt/org.wso2.carb
>>> on.webapp.mgt/src/main/java/org/wso2/carbon/webapp/mgt/sso/
>>> SAMLSignatureValidatorImpl.java
>>>
>>> Better to use utls from those two components, if we have such methods.
>>> Most suitable component for gateway is #2, since carbon authenticator don't
>>> have usage in gateway.
>>>
>>> I guess it's even worthy initiate separate component to handle all these
>>> saml utils, given that we have isolated components across the platform and
>>> we have to fix huge number of components if we identified a core issue.
>>>
>> +1 with darshans idea. And later better to have some common set of
>> libraries to handle this kind of scenarios.
>>
>>>
>>> Thanks,
>>>
>>>
 @Amila, in a cloud story do we need to configure the key aliases for
 each tenant or can we live with the default alias (which is the tenant
 domain name) ?



 --
 *Best Regards*

 *Rushmin Fernando*
 *Technical Lead*

 WSO2 Inc.  - Lean . Enterprise . Middleware

 mobile : +94772891266



>>>
>>>
>>> --
>>> Regards,
>>>
>>>
>>> *Darshana Gunawardana*Associate Technical Lead
>>> WSO2 Inc.; http://wso2.com
>>>
>>> *E-mail: darsh...@wso2.com *
>>> *Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware
>>>
>>
>>
>>
>> --
>> Ishara Karunarathna
>> Associate Technical Lead
>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>
>> email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
>> +94717996791
>>
>>
>>
>
>
> --
> Thanks & Regards,
>
> *Johann Dilantha Nallathamby*
> Technical Lead & Product Lead of WSO2 Identity Server
> Governance Technologies Team
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - *+9476950*
> Blog - *http://nallaa.wordpress.com *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards,

Kalpa Welivitigoda
Senior Software Engineer, WSO2 Inc. http://wso2.com
Email: kal...@wso2.com
Mobile: +94776509215

[image: http://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Final Evaluation] Proposal 21: [IS] Document Based NoSQL Support for WSO2 Identity Server Database

[Chamila Wijayarathna]

Hi Asantha,

If you have used any new features of org.json which is not available in
that old version, I think you will have to create an orbit with new
org.json version.

And I think it (either new or old version) need to be packed in your
feature, so it can be installed into any carbon based product.

Thanks!

On Fri, Aug 19, 2016 at 3:17 PM, Asantha Thilina 
wrote:

> Hi Chamila,
>
> ok thanks for the comment then i will change the version of my dependency
> and test it
>
> Thanks,
> Asantha
>
> On Fri, Aug 19, 2016 at 1:13 AM, Chamila Wijayarathna <
> cdwijayarat...@gmail.com> wrote:
>
>> Hi Asantha, Tharindu,
>>
>> I think IS already packs json, but the version is 20140107 which comes
>> from wso2 orbit bundle [1]. You are receiving the error due to version
>> mismatch, because you are using  version 20160212.
>>
>> Can you try using existing dependency and check if your features work
>> okay with that version?\\
>>
>> Thank You!
>>
>> [1]. https://github.com/wso2/orbit/blob/master/json/3.0.0.wso2v1
>>
>> On Fri, Aug 19, 2016 at 3:03 PM, Tharindu Edirisinghe > > wrote:
>>
>>> I meant shipping with the product... by packing with the product.
>>>
>>> Yes, it should be packed by the feature.
>>>
>>> I'll look more into Charon's dependency as well.
>>>
>>> On Fri, Aug 19, 2016 at 10:26 AM, Chamila Wijayarathna <
>>> cdwijayarat...@gmail.com> wrote:
>>>
 Hi Harsha,

 The license seems to be okay, isn't it? It doesn't mention anything
 that prevent us from using it. Also I think we use same library for json
 related stuff in charon as well. So it can't be an issue IMO.

 @Tharindu, Why we should pack this in product? Shouldn't we pack this
 in the feature?

 Thank You!

 On Fri, Aug 19, 2016 at 2:11 PM, Harsha Thirimanna 
 wrote:

> As in the license, there are some restrictions.
>
> http://www.json.org/license.html
>
> *Harsha Thirimanna*
> Associate Tech Lead | WSO2
>
> Email: hars...@wso2.com
> Mob: +94715186770
> Blog: http://harshathirimanna.blogspot.com/
> Twitter: http://twitter.com/harshathirimann
> Linked-In: linked-in: http://www.linkedin.com/pub/ha
> rsha-thirimanna/10/ab8/122
> 
>
> On Fri, Aug 19, 2016 at 9:30 AM, Tharindu Edirisinghe <
> tharin...@wso2.com> wrote:
>
>> Thanks Asantha.
>>
>> @Johann/Darshana - Would it be possible to pack org.json [1]
>> dependency to the product itself ?
>>
>> [1] https://mvnrepository.com/artifact/org.json/json/20160212
>>
>> Regards,
>> TharinduE
>>
>> On Fri, Aug 19, 2016 at 12:48 AM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Tharindu,
>>>
>>> As you instructed i have finished all above process and i already
>>> sent a PR[1] to product-is with my modifications and earlier i have 
>>> sent a
>>> PR[2] to identity-userstore-mongodb
>>> during the deployment of the product-is i face the following issue
>>> In my MongoDBUserStoreManager plugin i will be using org.json[2] lib
>>> for query purposes so it is a dependent for my plugin to work ,For the
>>> moment i manually added json lib to dropin folder to activate my bundle
>>> otherwise i will get following error when i open osgi console and 
>>> checked
>>> Missing optionally imported package org.json_[20160212.0.0,2016021
>>> 3.0.0).
>>> In order to activate the bundle need to add mongo-java-driver[4]
>>> also to dropins folder after that it will activate successfully,
>>> Is there any method to ship the json lib also with my bundle when
>>> deploying it to IS?
>>> [1]https://github.com/wso2/product-is/pull/668
>>> [2]https://github.com/wso2-extensions/identity-userstore-mon
>>> godb/pull/1
>>> [3]https://mvnrepository.com/artifact/org.json/json/20160212
>>> [4]https://mvnrepository.com/artifact/org.mongodb/mongo-java
>>> -driver/3.2.2
>>>
>>> Thanks,
>>> Asantha
>>>
>>>
>>>
>>> On Thu, Aug 18, 2016 at 2:19 AM, Tharindu Edirisinghe <
>>> tharin...@wso2.com> wrote:
>>>
 Hi Asntha,

 Please follow steps below to complete the project.

 1. In your features [1] folder, you have to create etc folder and
 put feature.properties file in it. This is same as [2].
 2. You have to create server.feature in [1]. Refer [3] and do the
 same. Make necessary modifications to pom file.
 3. Once you do above, you can commit and push so that your PR [4]
 will automatically get these changes appended.

 Next step is to add this feature to IS product so when the product
 is built, the jar file is automatically packed to the product. For 
 that,
 follow the instructions below.

 

Re: [Dev] Extensive amount of warning logs are printed once the IS520-Analytics server starts up.

[Sewmini Jayaweera]

+1 For disabling  that at log4j level if possible. Since it is harmless if
we can hide the log or stop printing the log repetitively that would be so
much better.

Sewmini Jayaweera
*Software Engineer - QA Team*
Mobile: +94 (0) 773 381 250
sewm...@wso2.com

On Thu, Aug 18, 2016 at 9:18 PM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:

>
>
> On Thu, Aug 18, 2016 at 3:55 PM, Tanya Madurapperuma 
> wrote:
>
>> This warning is coming from shindig which is the underlying library that
>> we used for gadget rendering and is a 3rd party library. Quick solution for
>> this is to increase maxDepth value as mentioned in [1] by Mohan.
>> If not we will have to analyze EhCache memory for memory consuming
>> objects [2] [3]
>>
>> [1] https://wso2.org/jira/browse/ANLYIS-48
>> [2] https://cwiki.apache.org/confluence/display/SHINDIG/Debuggin
>> g+EhCache's+SizeOfEngine
>> [3] https://cwiki.apache.org/confluence/display/SHINDIG/EhCache+
>> Memory+Analysis
>>
>
> @Tanya, Thanks for the response.. I think, increasing the maxDepth value
> is not helpful all the time.. Whether you guys, explored about this more ?
> Since it is observed in various products/cases. If this log does not
> reflect any useful info then can, we disable that at log4j level ?
>
> Thanks,
> Mohan
>
>
>>
>> Thanks,
>> Tanya
>>
>> On Thu, Aug 18, 2016 at 3:40 PM, Mohanadarshan Vivekanandalingam <
>> mo...@wso2.com> wrote:
>>
>>> [Moving to DEV]
>>>
>>> Related UES/DS jira is [1]..
>>>
>>> @Sewmini, above logs are only printed once for a user (When loading a
>>> gadget for first time - once for each gadget)..
>>>
>>> [1] https://wso2.org/jira/browse/UES-658
>>>
>>>
>>> Thanks,
>>> Mohan
>>>
>>>
>>> On Thu, Aug 18, 2016 at 3:34 PM, Sewmini Jayaweera 
>>> wrote:
>>>
 Hi DS team,

 I observed the same issue reported in [1] in the latest Analytics pack
 given. I reopened the issue since repeatedly printed warning may mislead
 user thinking it's a critical issue eve,n though it is harmless and it
 doesn't give a good impression to the user.

 It would be great if we can get this fixed. If it is difficult to fix
 it in this release can we change it to an improvement and fix it later
 without having it as won't fix?

 [1]. https://wso2.org/jira/browse/ANLYIS-48

 Thank you in advance.
 Kind regards,

 Sewmini Jayaweera
 *Software Engineer - QA Team*
 Mobile: +94 (0) 773 381 250
 sewm...@wso2.com

>>>
>>>
>>>
>>> --
>>> *V. Mohanadarshan*
>>> *Associate Tech Lead,*
>>> *Data Technologies Team,*
>>> *WSO2, Inc. http://wso2.com  *
>>> *lean.enterprise.middleware.*
>>>
>>> email: mo...@wso2.com
>>> phone:(+94) 771117673
>>>
>>
>>
>>
>> --
>> Tanya Madurapperuma
>>
>> Senior Software Engineer,
>> WSO2 Inc. : wso2.com
>> Mobile : +94718184439
>> Blog : http://tanyamadurapperuma.blogspot.com
>>
>
>
>
> --
> *V. Mohanadarshan*
> *Associate Tech Lead,*
> *Data Technologies Team,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: mo...@wso2.com
> phone:(+94) 771117673
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Enterprise Service Bus 5.0.0 RC4

[Eranda Rajapakshe]

Hi,

Tested and verified following,

*ESB runtime*

   - JMS 2.0 scenarios
   - JMS Message Store, Message Processor
   - JMS Inbound Endpoint


[+] - Stable, go ahead and release.

Thanks,
Eranda

On Thu, Aug 18, 2016 at 5:14 PM, Chanaka Fernando  wrote:

> Tested the following functionalities.
>
> *ESB runtime*
>
>- Clustering
>- Deployment Synchronization
>- Tenant use cases
>- Statistics/Tracing data publishing
>- Inbound Coordination
>- Message processor coordination
>- Registry mounting
>- CAR file deployment through management console
>
> *ESB Analytics*
>
>- Statistics/Tracing in super tenant mode for Proxy, Sequence, API,
>Inbound, Endpoint
>- Statistics/Tracing for above artifacts in tenant mode
>
> *ESB Tooling*
>
>- Artifact creation (Proxy, Inbound, Sequence, Endpoint, Message
>Store, Message Processor)
>- Artifact deployment from the Tool
>- Artifact export and deploy through management console
>
> No issues found.
>
> [+] - Stable - Go ahead and release
>
> On Wed, Aug 17, 2016 at 8:13 AM, Senduran Balasubramaniyam <
> sendu...@wso2.com> wrote:
>
>> Hi All,
>>
>> This is the 4th Release Candidate of WSO2 Enterprise Service Bus 5.0.0
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>>
>> Source and distribution
>>
>> Run-time: https://github.com/wso2/product-esb/releases/tag/v5.0.0-rc4
>> Tooling   : https://github.com/wso2/devstu
>> dio-tooling-esb/releases/tag/v5.0.0-rc4
>> Analytics: https://github.com/wso2/analytics-esb/releases/tag/v5.0.0-
>> rc4
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thanks,
>> - WSO2 ESB Team -
>>
>> --
>> *Senduran *
>> Senior Software Engineer,
>> WSO2, Inc.;  http://wso2.com/ 
>> Mobile: +94 77 952 6548
>>
>
>
>
> --
> Thank you and Best Regards,
> Chanaka Fernando
> Senior Technical Lead
> m: +94 773337238
> https://wso2.com 
>
>
>
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Eranda Rajapakshe*
Software Engineer
WSO2 Inc.
Mobile : +94784822608
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Announce] [Architecture] WSO2 Dashboard Server 2.1.0-Alpha Released!

[Susinda Perera]

Hi Nisala

We may need to create a new repo and host these maven plugins. As an
example esb uses maven-tooling-esb[1] and bps uses maven-tooling-bps[2] to
maintain the maven plugins. As we already have the maven plugins i think we
can easily build the DevStudio based tooling with using these plugins.
Please arrange a time to discuss this.

[1] - https://github.com/wso2/maven-tooling-esb
[2] - https://github.com/wso2/maven-tooling-bps



On Thu, Aug 18, 2016 at 6:45 PM, Nisala Nanayakkara  wrote:

> Hi,
>
> I have implemented maven - plugins for each artifacts in WSO2 Dashboard
> Server. So there are four maven - plugins for dashboards,gadgets,layouts
> and themes which can be used to generate a CAR file consisting with these
> artifacts. But we are not very much clear about where we have to maintain
> these maven - plugins. Is it better to keep it within our carbon-dashboards
> repository ? Or is it better to maintain these as a separate repository.
>
> @DevStudioTeam : Can you provide recommended way of maintaining these
> maven-plugins ?
>
> Thanks,
> Nisala
>
> On Mon, Aug 15, 2016 at 10:51 AM, Susinda Perera  wrote:
>
>> Do we have tooling support for this new release, like create/edit/deploy
>> gadgets/dashboards etc. If not shall we add this to roadmap. DevS team will
>> be able to help on this task.
>>
>> Thanks
>> Susinda
>>
>> On Fri, Aug 12, 2016 at 8:23 PM, Megala Uthayakumar 
>> wrote:
>>
>>> WSO2 Dashboard Server 2.1.0-Alpha Released!
>>>
>>> WSO2 Dashboard Server team is pleased to announce the release of WSO2
>>> Dashboard Server 2.1.0 Alpha. This release comes with the following bug
>>> fixes, improvements and tasks. You can download the distribution from [1]
>>> and view the documentation at [2].
>>> Bug
>>>
>>>- [UES-990 ] - All the query
>>>params get appended to the url when navigating via hierarchical menu
>>>- [UES-1016 ] - Tenant ID is
>>>always super tenant ID in Gadget Generation Wizard
>>>- [UES-1018 ] - DS Console
>>>differs from the WSO2 theme
>>>- [UES-1022 ] - Product
>>>version in footer is incorrect
>>>- [UES-1023 ] - Create view
>>>menu rendered incorrectly
>>>- [UES-1028 ] - Creating
>>>gadgets in third-party store - Thumbnail image does not show
>>>
>>> Improvement
>>>
>>>- [UES-970 ] - Add download
>>>functionality to gadgets listed
>>>- [UES-995 ] - Having a
>>>landing page for a dashboard is optional
>>>- [UES-1003 ] - Modify the ES
>>>extension to not allow the assets to be editable in published asset
>>>- [UES-1010 ] - Add shindig
>>>features to get the hostName,port and tenant domain
>>>- [UES-1012 ] - Store the
>>>theme level properties to dashboard.json and retrieve these theme
>>>properties while rendering the page
>>>- [UES-1014 ] - Add new
>>>gadget/layout button at the end of the gadget listing and layout listings
>>>when user designs dashboard
>>>- [UES-1015 ] - Dashboard
>>>page loading icon for embeddable gadget feature
>>>
>>> Task
>>>
>>>- [UES-1005 ] - Provide
>>>common repository for js libraries to use in gadgets
>>>- [UES-1006 ] - Dashboard
>>>page loading icon to show after all gadgets are loaded
>>>- [UES-1007 ] - Fixed the
>>>issue in PDF download feature in firefox browser
>>>- [UES-1008 ] - Fixing issues
>>>in running the dashboard server with samples
>>>- [UES-1029 ] - Create Puppet
>>>script for Dashboard Server Auto Deployment
>>>
>>> Reporting Issues
>>>
>>> Issues can be reported through the Public JIRA
>>>  project for WSO2 Dashboard Server.
>>>
>>>
>>> [1]- https://github.com/wso2/product-ds/releases/download/v2
>>> .1.0-alpha/wso2ds-2.1.0-SNAPSHOT.zip
>>>
>>> [2]- https://docs.wso2.com/display/DS210/WSO2+Dashboard+Serv
>>> er+Documentation
>>>
>>>
>>> Thanks,
>>>
>>> Dashboard Server Team.
>>>
>>> --
>>> Megala Uthayakumar
>>>
>>> Software Engineer
>>> Mobile : 0779967122
>>>
>>> ___
>>> Announce mailing list
>>> annou...@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/announce
>>>
>>>
>>
>>
>> --
>> *Susinda Perera*
>> Software Engineer
>> B.Sc.(Eng), 

Re: [Dev] [GSoC Final Evaluation] Proposal 21: [IS] Document Based NoSQL Support for WSO2 Identity Server Database

[Asantha Thilina]

Hi Chamila,

ok thanks for the comment then i will change the version of my dependency
and test it

Thanks,
Asantha

On Fri, Aug 19, 2016 at 1:13 AM, Chamila Wijayarathna <
cdwijayarat...@gmail.com> wrote:

> Hi Asantha, Tharindu,
>
> I think IS already packs json, but the version is 20140107 which comes
> from wso2 orbit bundle [1]. You are receiving the error due to version
> mismatch, because you are using  version 20160212.
>
> Can you try using existing dependency and check if your features work okay
> with that version?\\
>
> Thank You!
>
> [1]. https://github.com/wso2/orbit/blob/master/json/3.0.0.wso2v1
>
> On Fri, Aug 19, 2016 at 3:03 PM, Tharindu Edirisinghe 
> wrote:
>
>> I meant shipping with the product... by packing with the product.
>>
>> Yes, it should be packed by the feature.
>>
>> I'll look more into Charon's dependency as well.
>>
>> On Fri, Aug 19, 2016 at 10:26 AM, Chamila Wijayarathna <
>> cdwijayarat...@gmail.com> wrote:
>>
>>> Hi Harsha,
>>>
>>> The license seems to be okay, isn't it? It doesn't mention anything that
>>> prevent us from using it. Also I think we use same library for json related
>>> stuff in charon as well. So it can't be an issue IMO.
>>>
>>> @Tharindu, Why we should pack this in product? Shouldn't we pack this in
>>> the feature?
>>>
>>> Thank You!
>>>
>>> On Fri, Aug 19, 2016 at 2:11 PM, Harsha Thirimanna 
>>> wrote:
>>>
 As in the license, there are some restrictions.

 http://www.json.org/license.html

 *Harsha Thirimanna*
 Associate Tech Lead | WSO2

 Email: hars...@wso2.com
 Mob: +94715186770
 Blog: http://harshathirimanna.blogspot.com/
 Twitter: http://twitter.com/harshathirimann
 Linked-In: linked-in: http://www.linkedin.com/pub/ha
 rsha-thirimanna/10/ab8/122
 

 On Fri, Aug 19, 2016 at 9:30 AM, Tharindu Edirisinghe <
 tharin...@wso2.com> wrote:

> Thanks Asantha.
>
> @Johann/Darshana - Would it be possible to pack org.json [1]
> dependency to the product itself ?
>
> [1] https://mvnrepository.com/artifact/org.json/json/20160212
>
> Regards,
> TharinduE
>
> On Fri, Aug 19, 2016 at 12:48 AM, Asantha Thilina <
> asanthathil...@gmail.com> wrote:
>
>> Hi Tharindu,
>>
>> As you instructed i have finished all above process and i already
>> sent a PR[1] to product-is with my modifications and earlier i have sent 
>> a
>> PR[2] to identity-userstore-mongodb
>> during the deployment of the product-is i face the following issue
>> In my MongoDBUserStoreManager plugin i will be using org.json[2] lib
>> for query purposes so it is a dependent for my plugin to work ,For the
>> moment i manually added json lib to dropin folder to activate my bundle
>> otherwise i will get following error when i open osgi console and checked
>> Missing optionally imported package org.json_[20160212.0.0,2016021
>> 3.0.0).
>> In order to activate the bundle need to add mongo-java-driver[4] also
>> to dropins folder after that it will activate successfully,
>> Is there any method to ship the json lib also with my bundle when
>> deploying it to IS?
>> [1]https://github.com/wso2/product-is/pull/668
>> [2]https://github.com/wso2-extensions/identity-userstore-mon
>> godb/pull/1
>> [3]https://mvnrepository.com/artifact/org.json/json/20160212
>> [4]https://mvnrepository.com/artifact/org.mongodb/mongo-java
>> -driver/3.2.2
>>
>> Thanks,
>> Asantha
>>
>>
>>
>> On Thu, Aug 18, 2016 at 2:19 AM, Tharindu Edirisinghe <
>> tharin...@wso2.com> wrote:
>>
>>> Hi Asntha,
>>>
>>> Please follow steps below to complete the project.
>>>
>>> 1. In your features [1] folder, you have to create etc folder and
>>> put feature.properties file in it. This is same as [2].
>>> 2. You have to create server.feature in [1]. Refer [3] and do the
>>> same. Make necessary modifications to pom file.
>>> 3. Once you do above, you can commit and push so that your PR [4]
>>> will automatically get these changes appended.
>>>
>>> Next step is to add this feature to IS product so when the product
>>> is built, the jar file is automatically packed to the product. For that,
>>> follow the instructions below.
>>>
>>> 4. Clone product-is [5] and do a clean repo build skipping tests.
>>> (you can just backup .m2 directory in your home and create an empty 
>>> folder
>>> with name .m2. Then you can run mvn clean install 
>>> -Dmaven.test.skip=true"
>>> command in product-is.
>>> 5. Once the product is built, you can get the zip file in
>>> modules/distribution folder. Run the product and check if you can access
>>> management console.
>>> 6. Next step is to build your feature so local m2 repository get the
>>> jar files of 

Re: [Dev] [GSoC Final Evaluation] Proposal 21: [IS] Document Based NoSQL Support for WSO2 Identity Server Database

[Tharindu Edirisinghe]

Thanks Chamila for the input.

@Asantha - Can you try to change the json dependency version to what
Chamila has mentioned and test.



On Fri, Aug 19, 2016 at 10:43 AM, Chamila Wijayarathna <
cdwijayarat...@gmail.com> wrote:

> Hi Asantha, Tharindu,
>
> I think IS already packs json, but the version is 20140107 which comes
> from wso2 orbit bundle [1]. You are receiving the error due to version
> mismatch, because you are using  version 20160212.
>
> Can you try using existing dependency and check if your features work okay
> with that version?\\
>
> Thank You!
>
> [1]. https://github.com/wso2/orbit/blob/master/json/3.0.0.wso2v1
>
> On Fri, Aug 19, 2016 at 3:03 PM, Tharindu Edirisinghe 
> wrote:
>
>> I meant shipping with the product... by packing with the product.
>>
>> Yes, it should be packed by the feature.
>>
>> I'll look more into Charon's dependency as well.
>>
>> On Fri, Aug 19, 2016 at 10:26 AM, Chamila Wijayarathna <
>> cdwijayarat...@gmail.com> wrote:
>>
>>> Hi Harsha,
>>>
>>> The license seems to be okay, isn't it? It doesn't mention anything that
>>> prevent us from using it. Also I think we use same library for json related
>>> stuff in charon as well. So it can't be an issue IMO.
>>>
>>> @Tharindu, Why we should pack this in product? Shouldn't we pack this in
>>> the feature?
>>>
>>> Thank You!
>>>
>>> On Fri, Aug 19, 2016 at 2:11 PM, Harsha Thirimanna 
>>> wrote:
>>>
 As in the license, there are some restrictions.

 http://www.json.org/license.html

 *Harsha Thirimanna*
 Associate Tech Lead | WSO2

 Email: hars...@wso2.com
 Mob: +94715186770
 Blog: http://harshathirimanna.blogspot.com/
 Twitter: http://twitter.com/harshathirimann
 Linked-In: linked-in: http://www.linkedin.com/pub/ha
 rsha-thirimanna/10/ab8/122
 

 On Fri, Aug 19, 2016 at 9:30 AM, Tharindu Edirisinghe <
 tharin...@wso2.com> wrote:

> Thanks Asantha.
>
> @Johann/Darshana - Would it be possible to pack org.json [1]
> dependency to the product itself ?
>
> [1] https://mvnrepository.com/artifact/org.json/json/20160212
>
> Regards,
> TharinduE
>
> On Fri, Aug 19, 2016 at 12:48 AM, Asantha Thilina <
> asanthathil...@gmail.com> wrote:
>
>> Hi Tharindu,
>>
>> As you instructed i have finished all above process and i already
>> sent a PR[1] to product-is with my modifications and earlier i have sent 
>> a
>> PR[2] to identity-userstore-mongodb
>> during the deployment of the product-is i face the following issue
>> In my MongoDBUserStoreManager plugin i will be using org.json[2] lib
>> for query purposes so it is a dependent for my plugin to work ,For the
>> moment i manually added json lib to dropin folder to activate my bundle
>> otherwise i will get following error when i open osgi console and checked
>> Missing optionally imported package org.json_[20160212.0.0,2016021
>> 3.0.0).
>> In order to activate the bundle need to add mongo-java-driver[4] also
>> to dropins folder after that it will activate successfully,
>> Is there any method to ship the json lib also with my bundle when
>> deploying it to IS?
>> [1]https://github.com/wso2/product-is/pull/668
>> [2]https://github.com/wso2-extensions/identity-userstore-mon
>> godb/pull/1
>> [3]https://mvnrepository.com/artifact/org.json/json/20160212
>> [4]https://mvnrepository.com/artifact/org.mongodb/mongo-java
>> -driver/3.2.2
>>
>> Thanks,
>> Asantha
>>
>>
>>
>> On Thu, Aug 18, 2016 at 2:19 AM, Tharindu Edirisinghe <
>> tharin...@wso2.com> wrote:
>>
>>> Hi Asntha,
>>>
>>> Please follow steps below to complete the project.
>>>
>>> 1. In your features [1] folder, you have to create etc folder and
>>> put feature.properties file in it. This is same as [2].
>>> 2. You have to create server.feature in [1]. Refer [3] and do the
>>> same. Make necessary modifications to pom file.
>>> 3. Once you do above, you can commit and push so that your PR [4]
>>> will automatically get these changes appended.
>>>
>>> Next step is to add this feature to IS product so when the product
>>> is built, the jar file is automatically packed to the product. For that,
>>> follow the instructions below.
>>>
>>> 4. Clone product-is [5] and do a clean repo build skipping tests.
>>> (you can just backup .m2 directory in your home and create an empty 
>>> folder
>>> with name .m2. Then you can run mvn clean install 
>>> -Dmaven.test.skip=true"
>>> command in product-is.
>>> 5. Once the product is built, you can get the zip file in
>>> modules/distribution folder. Run the product and check if you can access
>>> management console.
>>> 6. Next step is to build your feature so local m2 repository get the

Re: [Dev] [GSoC Final Evaluation] Proposal 21: [IS] Document Based NoSQL Support for WSO2 Identity Server Database

[Chamila Wijayarathna]

Hi Asantha, Tharindu,

I think IS already packs json, but the version is 20140107 which comes from
wso2 orbit bundle [1]. You are receiving the error due to version mismatch,
because you are using  version 20160212.

Can you try using existing dependency and check if your features work okay
with that version?\\

Thank You!

[1]. https://github.com/wso2/orbit/blob/master/json/3.0.0.wso2v1

On Fri, Aug 19, 2016 at 3:03 PM, Tharindu Edirisinghe 
wrote:

> I meant shipping with the product... by packing with the product.
>
> Yes, it should be packed by the feature.
>
> I'll look more into Charon's dependency as well.
>
> On Fri, Aug 19, 2016 at 10:26 AM, Chamila Wijayarathna <
> cdwijayarat...@gmail.com> wrote:
>
>> Hi Harsha,
>>
>> The license seems to be okay, isn't it? It doesn't mention anything that
>> prevent us from using it. Also I think we use same library for json related
>> stuff in charon as well. So it can't be an issue IMO.
>>
>> @Tharindu, Why we should pack this in product? Shouldn't we pack this in
>> the feature?
>>
>> Thank You!
>>
>> On Fri, Aug 19, 2016 at 2:11 PM, Harsha Thirimanna 
>> wrote:
>>
>>> As in the license, there are some restrictions.
>>>
>>> http://www.json.org/license.html
>>>
>>> *Harsha Thirimanna*
>>> Associate Tech Lead | WSO2
>>>
>>> Email: hars...@wso2.com
>>> Mob: +94715186770
>>> Blog: http://harshathirimanna.blogspot.com/
>>> Twitter: http://twitter.com/harshathirimann
>>> Linked-In: linked-in: http://www.linkedin.com/pub/ha
>>> rsha-thirimanna/10/ab8/122
>>> 
>>>
>>> On Fri, Aug 19, 2016 at 9:30 AM, Tharindu Edirisinghe <
>>> tharin...@wso2.com> wrote:
>>>
 Thanks Asantha.

 @Johann/Darshana - Would it be possible to pack org.json [1] dependency
 to the product itself ?

 [1] https://mvnrepository.com/artifact/org.json/json/20160212

 Regards,
 TharinduE

 On Fri, Aug 19, 2016 at 12:48 AM, Asantha Thilina <
 asanthathil...@gmail.com> wrote:

> Hi Tharindu,
>
> As you instructed i have finished all above process and i already sent
> a PR[1] to product-is with my modifications and earlier i have sent a 
> PR[2]
> to identity-userstore-mongodb
> during the deployment of the product-is i face the following issue
> In my MongoDBUserStoreManager plugin i will be using org.json[2] lib
> for query purposes so it is a dependent for my plugin to work ,For the
> moment i manually added json lib to dropin folder to activate my bundle
> otherwise i will get following error when i open osgi console and checked
> Missing optionally imported package org.json_[20160212.0.0,2016021
> 3.0.0).
> In order to activate the bundle need to add mongo-java-driver[4] also
> to dropins folder after that it will activate successfully,
> Is there any method to ship the json lib also with my bundle when
> deploying it to IS?
> [1]https://github.com/wso2/product-is/pull/668
> [2]https://github.com/wso2-extensions/identity-userstore-mon
> godb/pull/1
> [3]https://mvnrepository.com/artifact/org.json/json/20160212
> [4]https://mvnrepository.com/artifact/org.mongodb/mongo-java
> -driver/3.2.2
>
> Thanks,
> Asantha
>
>
>
> On Thu, Aug 18, 2016 at 2:19 AM, Tharindu Edirisinghe <
> tharin...@wso2.com> wrote:
>
>> Hi Asntha,
>>
>> Please follow steps below to complete the project.
>>
>> 1. In your features [1] folder, you have to create etc folder and put
>> feature.properties file in it. This is same as [2].
>> 2. You have to create server.feature in [1]. Refer [3] and do the
>> same. Make necessary modifications to pom file.
>> 3. Once you do above, you can commit and push so that your PR [4]
>> will automatically get these changes appended.
>>
>> Next step is to add this feature to IS product so when the product is
>> built, the jar file is automatically packed to the product. For that,
>> follow the instructions below.
>>
>> 4. Clone product-is [5] and do a clean repo build skipping tests.
>> (you can just backup .m2 directory in your home and create an empty 
>> folder
>> with name .m2. Then you can run mvn clean install -Dmaven.test.skip=true"
>> command in product-is.
>> 5. Once the product is built, you can get the zip file in
>> modules/distribution folder. Run the product and check if you can access
>> management console.
>> 6. Next step is to build your feature so local m2 repository get the
>> jar files of your feature.
>> 7. Then, you can fork product-is and modify parent pom [6] adding a
>> new property for your feature's version. Similar to below property, you 
>> can
>> add your own one.
>>
>> 5.1.1> .remote.version>
>>
>> 8.  Modify the p2-profile-get pom file [7] and include your feature
>> there. You can 

Re: [Dev] [GSoC Final Evaluation] Proposal 21: [IS] Document Based NoSQL Support for WSO2 Identity Server Database

[Tharindu Edirisinghe]

I meant shipping with the product... by packing with the product.

Yes, it should be packed by the feature.

I'll look more into Charon's dependency as well.

On Fri, Aug 19, 2016 at 10:26 AM, Chamila Wijayarathna <
cdwijayarat...@gmail.com> wrote:

> Hi Harsha,
>
> The license seems to be okay, isn't it? It doesn't mention anything that
> prevent us from using it. Also I think we use same library for json related
> stuff in charon as well. So it can't be an issue IMO.
>
> @Tharindu, Why we should pack this in product? Shouldn't we pack this in
> the feature?
>
> Thank You!
>
> On Fri, Aug 19, 2016 at 2:11 PM, Harsha Thirimanna 
> wrote:
>
>> As in the license, there are some restrictions.
>>
>> http://www.json.org/license.html
>>
>> *Harsha Thirimanna*
>> Associate Tech Lead | WSO2
>>
>> Email: hars...@wso2.com
>> Mob: +94715186770
>> Blog: http://harshathirimanna.blogspot.com/
>> Twitter: http://twitter.com/harshathirimann
>> Linked-In: linked-in: http://www.linkedin.com/pub/ha
>> rsha-thirimanna/10/ab8/122
>> 
>>
>> On Fri, Aug 19, 2016 at 9:30 AM, Tharindu Edirisinghe > > wrote:
>>
>>> Thanks Asantha.
>>>
>>> @Johann/Darshana - Would it be possible to pack org.json [1] dependency
>>> to the product itself ?
>>>
>>> [1] https://mvnrepository.com/artifact/org.json/json/20160212
>>>
>>> Regards,
>>> TharinduE
>>>
>>> On Fri, Aug 19, 2016 at 12:48 AM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi Tharindu,

 As you instructed i have finished all above process and i already sent
 a PR[1] to product-is with my modifications and earlier i have sent a PR[2]
 to identity-userstore-mongodb
 during the deployment of the product-is i face the following issue
 In my MongoDBUserStoreManager plugin i will be using org.json[2] lib
 for query purposes so it is a dependent for my plugin to work ,For the
 moment i manually added json lib to dropin folder to activate my bundle
 otherwise i will get following error when i open osgi console and checked
 Missing optionally imported package org.json_[20160212.0.0,2016021
 3.0.0).
 In order to activate the bundle need to add mongo-java-driver[4] also
 to dropins folder after that it will activate successfully,
 Is there any method to ship the json lib also with my bundle when
 deploying it to IS?
 [1]https://github.com/wso2/product-is/pull/668
 [2]https://github.com/wso2-extensions/identity-userstore-mongodb/pull/1
 [3]https://mvnrepository.com/artifact/org.json/json/20160212
 [4]https://mvnrepository.com/artifact/org.mongodb/mongo-java
 -driver/3.2.2

 Thanks,
 Asantha



 On Thu, Aug 18, 2016 at 2:19 AM, Tharindu Edirisinghe <
 tharin...@wso2.com> wrote:

> Hi Asntha,
>
> Please follow steps below to complete the project.
>
> 1. In your features [1] folder, you have to create etc folder and put
> feature.properties file in it. This is same as [2].
> 2. You have to create server.feature in [1]. Refer [3] and do the
> same. Make necessary modifications to pom file.
> 3. Once you do above, you can commit and push so that your PR [4] will
> automatically get these changes appended.
>
> Next step is to add this feature to IS product so when the product is
> built, the jar file is automatically packed to the product. For that,
> follow the instructions below.
>
> 4. Clone product-is [5] and do a clean repo build skipping tests. (you
> can just backup .m2 directory in your home and create an empty folder with
> name .m2. Then you can run mvn clean install -Dmaven.test.skip=true"
> command in product-is.
> 5. Once the product is built, you can get the zip file in
> modules/distribution folder. Run the product and check if you can access
> management console.
> 6. Next step is to build your feature so local m2 repository get the
> jar files of your feature.
> 7. Then, you can fork product-is and modify parent pom [6] adding a
> new property for your feature's version. Similar to below property, you 
> can
> add your own one.
>
> 5.1.1 .remote.version>
>
> 8.  Modify the p2-profile-get pom file [7] and include your feature
> there. You can search for "*user.store.remote.feature*" and following
> that, add details for your feature.
> 9. Then re-build the product-is, get the zip file, run it and in
> Management Console, check if mongodb userstore is listed. Also you can
> check if the jar file is packed in plugins.
> 10. Finally send a PR to product-is with these changes.
>
>
> [1] https://github.com/asanthamax/identity-userstore-mongodb/tre
> e/master/features
> [2] https://github.com/wso2-extensions/identity-userstore-remote
> /blob/master/features/etc/feature.properties
> [3] 

Re: [Dev] [GSoC Final Evaluation] Proposal 21: [IS] Document Based NoSQL Support for WSO2 Identity Server Database

[Chamila Wijayarathna]

Hi Harsha,

The license seems to be okay, isn't it? It doesn't mention anything that
prevent us from using it. Also I think we use same library for json related
stuff in charon as well. So it can't be an issue IMO.

@Tharindu, Why we should pack this in product? Shouldn't we pack this in
the feature?

Thank You!

On Fri, Aug 19, 2016 at 2:11 PM, Harsha Thirimanna  wrote:

> As in the license, there are some restrictions.
>
> http://www.json.org/license.html
>
> *Harsha Thirimanna*
> Associate Tech Lead | WSO2
>
> Email: hars...@wso2.com
> Mob: +94715186770
> Blog: http://harshathirimanna.blogspot.com/
> Twitter: http://twitter.com/harshathirimann
> Linked-In: linked-in: http://www.linkedin.com/pub/
> harsha-thirimanna/10/ab8/122
> 
>
> On Fri, Aug 19, 2016 at 9:30 AM, Tharindu Edirisinghe 
> wrote:
>
>> Thanks Asantha.
>>
>> @Johann/Darshana - Would it be possible to pack org.json [1] dependency
>> to the product itself ?
>>
>> [1] https://mvnrepository.com/artifact/org.json/json/20160212
>>
>> Regards,
>> TharinduE
>>
>> On Fri, Aug 19, 2016 at 12:48 AM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Tharindu,
>>>
>>> As you instructed i have finished all above process and i already sent a
>>> PR[1] to product-is with my modifications and earlier i have sent a PR[2]
>>> to identity-userstore-mongodb
>>> during the deployment of the product-is i face the following issue
>>> In my MongoDBUserStoreManager plugin i will be using org.json[2] lib for
>>> query purposes so it is a dependent for my plugin to work ,For the moment i
>>> manually added json lib to dropin folder to activate my bundle otherwise i
>>> will get following error when i open osgi console and checked
>>> Missing optionally imported package org.json_[20160212.0.0,2016021
>>> 3.0.0).
>>> In order to activate the bundle need to add mongo-java-driver[4] also to
>>> dropins folder after that it will activate successfully,
>>> Is there any method to ship the json lib also with my bundle when
>>> deploying it to IS?
>>> [1]https://github.com/wso2/product-is/pull/668
>>> [2]https://github.com/wso2-extensions/identity-userstore-mongodb/pull/1
>>> [3]https://mvnrepository.com/artifact/org.json/json/20160212
>>> [4]https://mvnrepository.com/artifact/org.mongodb/mongo-java
>>> -driver/3.2.2
>>>
>>> Thanks,
>>> Asantha
>>>
>>>
>>>
>>> On Thu, Aug 18, 2016 at 2:19 AM, Tharindu Edirisinghe <
>>> tharin...@wso2.com> wrote:
>>>
 Hi Asntha,

 Please follow steps below to complete the project.

 1. In your features [1] folder, you have to create etc folder and put
 feature.properties file in it. This is same as [2].
 2. You have to create server.feature in [1]. Refer [3] and do the same.
 Make necessary modifications to pom file.
 3. Once you do above, you can commit and push so that your PR [4] will
 automatically get these changes appended.

 Next step is to add this feature to IS product so when the product is
 built, the jar file is automatically packed to the product. For that,
 follow the instructions below.

 4. Clone product-is [5] and do a clean repo build skipping tests. (you
 can just backup .m2 directory in your home and create an empty folder with
 name .m2. Then you can run mvn clean install -Dmaven.test.skip=true"
 command in product-is.
 5. Once the product is built, you can get the zip file in
 modules/distribution folder. Run the product and check if you can access
 management console.
 6. Next step is to build your feature so local m2 repository get the
 jar files of your feature.
 7. Then, you can fork product-is and modify parent pom [6] adding a new
 property for your feature's version. Similar to below property, you can add
 your own one.

 5.1.1>>> .remote.version>

 8.  Modify the p2-profile-get pom file [7] and include your feature
 there. You can search for "*user.store.remote.feature*" and following
 that, add details for your feature.
 9. Then re-build the product-is, get the zip file, run it and in
 Management Console, check if mongodb userstore is listed. Also you can
 check if the jar file is packed in plugins.
 10. Finally send a PR to product-is with these changes.


 [1] https://github.com/asanthamax/identity-userstore-mongodb/tre
 e/master/features
 [2] https://github.com/wso2-extensions/identity-userstore-remote
 /blob/master/features/etc/feature.properties
 [3] https://github.com/wso2-extensions/identity-userstore-remote
 /tree/master/features/org.wso2.carbon.identity.user.store.re
 mote.server.feature
 [4] https://github.com/wso2-extensions/identity-userstore-mongod
 b/pull/1
 [5] https://github.com/wso2/product-is/
 [6] https://github.com/wso2/product-is/blob/master/pom.xml
 [7] https://github.com/wso2/product-is/blob/master/modules/p2-pr

Re: [Dev] [GSoC Final Evaluation] Proposal 21: [IS] Document Based NoSQL Support for WSO2 Identity Server Database

[Harsha Thirimanna]

Hi Tharindu,
As Chamila said, we already use this in charon. Can you please check on
that first.

*Harsha Thirimanna*
Associate Tech Lead | WSO2

Email: hars...@wso2.com
Mob: +94715186770
Blog: http://harshathirimanna.blogspot.com/
Twitter: http://twitter.com/harshathirimann
Linked-In: linked-in:
http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122


On Fri, Aug 19, 2016 at 10:11 AM, Asantha Thilina 
wrote:

> Hi Tharindu,
>
> sure i will check that into
>
> Thanks,
> Asantha
>
> On Fri, Aug 19, 2016 at 12:26 AM, Tharindu Edirisinghe  > wrote:
>
>> Seems we'll have to find some alternative if we are to pack this to the
>> product.
>>
>> @Asantha - Can you check if Apache has a library that provides similar
>> functionality.
>>
>> Thanks,
>> TharinduE
>>
>> On Fri, Aug 19, 2016 at 9:41 AM, Harsha Thirimanna 
>> wrote:
>>
>>> As in the license, there are some restrictions.
>>>
>>> http://www.json.org/license.html
>>>
>>> *Harsha Thirimanna*
>>> Associate Tech Lead | WSO2
>>>
>>> Email: hars...@wso2.com
>>> Mob: +94715186770
>>> Blog: http://harshathirimanna.blogspot.com/
>>> Twitter: http://twitter.com/harshathirimann
>>> Linked-In: linked-in: http://www.linkedin.com/pub/ha
>>> rsha-thirimanna/10/ab8/122
>>> 
>>>
>>> On Fri, Aug 19, 2016 at 9:30 AM, Tharindu Edirisinghe <
>>> tharin...@wso2.com> wrote:
>>>
 Thanks Asantha.

 @Johann/Darshana - Would it be possible to pack org.json [1] dependency
 to the product itself ?

 [1] https://mvnrepository.com/artifact/org.json/json/20160212

 Regards,
 TharinduE

 On Fri, Aug 19, 2016 at 12:48 AM, Asantha Thilina <
 asanthathil...@gmail.com> wrote:

> Hi Tharindu,
>
> As you instructed i have finished all above process and i already sent
> a PR[1] to product-is with my modifications and earlier i have sent a 
> PR[2]
> to identity-userstore-mongodb
> during the deployment of the product-is i face the following issue
> In my MongoDBUserStoreManager plugin i will be using org.json[2] lib
> for query purposes so it is a dependent for my plugin to work ,For the
> moment i manually added json lib to dropin folder to activate my bundle
> otherwise i will get following error when i open osgi console and checked
> Missing optionally imported package org.json_[20160212.0.0,2016021
> 3.0.0).
> In order to activate the bundle need to add mongo-java-driver[4] also
> to dropins folder after that it will activate successfully,
> Is there any method to ship the json lib also with my bundle when
> deploying it to IS?
> [1]https://github.com/wso2/product-is/pull/668
> [2]https://github.com/wso2-extensions/identity-userstore-mon
> godb/pull/1
> [3]https://mvnrepository.com/artifact/org.json/json/20160212
> [4]https://mvnrepository.com/artifact/org.mongodb/mongo-java
> -driver/3.2.2
>
> Thanks,
> Asantha
>
>
>
> On Thu, Aug 18, 2016 at 2:19 AM, Tharindu Edirisinghe <
> tharin...@wso2.com> wrote:
>
>> Hi Asntha,
>>
>> Please follow steps below to complete the project.
>>
>> 1. In your features [1] folder, you have to create etc folder and put
>> feature.properties file in it. This is same as [2].
>> 2. You have to create server.feature in [1]. Refer [3] and do the
>> same. Make necessary modifications to pom file.
>> 3. Once you do above, you can commit and push so that your PR [4]
>> will automatically get these changes appended.
>>
>> Next step is to add this feature to IS product so when the product is
>> built, the jar file is automatically packed to the product. For that,
>> follow the instructions below.
>>
>> 4. Clone product-is [5] and do a clean repo build skipping tests.
>> (you can just backup .m2 directory in your home and create an empty 
>> folder
>> with name .m2. Then you can run mvn clean install -Dmaven.test.skip=true"
>> command in product-is.
>> 5. Once the product is built, you can get the zip file in
>> modules/distribution folder. Run the product and check if you can access
>> management console.
>> 6. Next step is to build your feature so local m2 repository get the
>> jar files of your feature.
>> 7. Then, you can fork product-is and modify parent pom [6] adding a
>> new property for your feature's version. Similar to below property, you 
>> can
>> add your own one.
>>
>> 5.1.1> .remote.version>
>>
>> 8.  Modify the p2-profile-get pom file [7] and include your feature
>> there. You can search for "*user.store.remote.feature*" and
>> following that, add details for your feature.
>> 9. Then re-build the product-is, get the zip file, run it and in
>> Management Console, check if mongodb userstore is listed. Also you 

Re: [Dev] [AppM] SAML response signature validation in tenants

[Johann Nallathamby]

This is what we have the SSO agent for.

@Rushmin, did you check the SSOAgent code? This was improved recently also
and is used in AS 6.0. The goal of the implementation was to make it a
library to be used everywhere in the platform. Can you please check on
that? If there are any limitations we need to fix that library and try to
use it everywhere we need it.

Please check with Kernel team where to get this and use this.

On Fri, Aug 19, 2016 at 9:56 AM, Ishara Karunarathna 
wrote:

> Hi,
>
> On Fri, Aug 19, 2016 at 9:47 AM, Darshana Gunawardana 
> wrote:
>
>>
>>
>> On Thu, Aug 18, 2016 at 4:43 PM, Rushmin Fernando 
>> wrote:
>>
>>>
>>> In current App Manager the service providers of tenants are getting
>>> created in the super tenant space.
>>>
>>> We are in the process of creating the service providers in the relevant
>>> tenants.
>>>
>>> In the app manager gateway, we use SAML SSO to authenticate the users,
>>> and the aforementioned service providers are used.
>>>
>>> When it comes to validating the the SAML response signature, I can see
>>> that we can re-use
>>> *org.wso2.carbon.identity.sso.saml.util.SAMLSSOUtil::getX509CredentialImplForTenant()*
>>>
>>> As per the code, it uses the tenant key store to get the certificates.
>>> And we can get the certificate by using the tenant name as the alias
>>>
>>> @IS team, do you see any issues with re-using this code in our gateway ?
>>>
>>
>> Using this util makes gateway -which is a client side(sp) component-
>> depends on the SAML component -which is server side(idp) component-
>>
>> IMO, its not nice to have that dependency. Once example is, this
>> dependency will expose you a samlsso (idp) endpoint from the gateway. And
>> also gateway profile would need to have saml components and makes you to
>> have whole framework related dependencies as well.
>>
>> Thinking about client side (sp) components which already doing this there
>> are two components we have in wso2 platform.
>> 1. Carbon SAML authenticator : https://github.com/wso2-exte
>> nsions/identity-carbon-auth-saml2
>> 2. AS SSO valve : https://github.com/wso2/carb
>> on-deployment/blob/4.7.x/components/webapp-mgt/org.wso2.
>> carbon.webapp.mgt/src/main/java/org/wso2/carbon/webapp/
>> mgt/sso/SAMLSignatureValidatorImpl.java
>>
>> Better to use utls from those two components, if we have such methods.
>> Most suitable component for gateway is #2, since carbon authenticator don't
>> have usage in gateway.
>>
>> I guess it's even worthy initiate separate component to handle all these
>> saml utils, given that we have isolated components across the platform and
>> we have to fix huge number of components if we identified a core issue.
>>
> +1 with darshans idea. And later better to have some common set of
> libraries to handle this kind of scenarios.
>
>>
>> Thanks,
>>
>>
>>> @Amila, in a cloud story do we need to configure the key aliases for
>>> each tenant or can we live with the default alias (which is the tenant
>>> domain name) ?
>>>
>>>
>>>
>>> --
>>> *Best Regards*
>>>
>>> *Rushmin Fernando*
>>> *Technical Lead*
>>>
>>> WSO2 Inc.  - Lean . Enterprise . Middleware
>>>
>>> mobile : +94772891266
>>>
>>>
>>>
>>
>>
>> --
>> Regards,
>>
>>
>> *Darshana Gunawardana*Associate Technical Lead
>> WSO2 Inc.; http://wso2.com
>>
>> *E-mail: darsh...@wso2.com *
>> *Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware
>>
>
>
>
> --
> Ishara Karunarathna
> Associate Technical Lead
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
> +94717996791
>
>
>


-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*
Technical Lead & Product Lead of WSO2 Identity Server
Governance Technologies Team
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Final Evaluation] Proposal 21: [IS] Document Based NoSQL Support for WSO2 Identity Server Database

[Asantha Thilina]

Hi Tharindu,

sure i will check that into

Thanks,
Asantha

On Fri, Aug 19, 2016 at 12:26 AM, Tharindu Edirisinghe 
wrote:

> Seems we'll have to find some alternative if we are to pack this to the
> product.
>
> @Asantha - Can you check if Apache has a library that provides similar
> functionality.
>
> Thanks,
> TharinduE
>
> On Fri, Aug 19, 2016 at 9:41 AM, Harsha Thirimanna 
> wrote:
>
>> As in the license, there are some restrictions.
>>
>> http://www.json.org/license.html
>>
>> *Harsha Thirimanna*
>> Associate Tech Lead | WSO2
>>
>> Email: hars...@wso2.com
>> Mob: +94715186770
>> Blog: http://harshathirimanna.blogspot.com/
>> Twitter: http://twitter.com/harshathirimann
>> Linked-In: linked-in: http://www.linkedin.com/pub/ha
>> rsha-thirimanna/10/ab8/122
>> 
>>
>> On Fri, Aug 19, 2016 at 9:30 AM, Tharindu Edirisinghe > > wrote:
>>
>>> Thanks Asantha.
>>>
>>> @Johann/Darshana - Would it be possible to pack org.json [1] dependency
>>> to the product itself ?
>>>
>>> [1] https://mvnrepository.com/artifact/org.json/json/20160212
>>>
>>> Regards,
>>> TharinduE
>>>
>>> On Fri, Aug 19, 2016 at 12:48 AM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi Tharindu,

 As you instructed i have finished all above process and i already sent
 a PR[1] to product-is with my modifications and earlier i have sent a PR[2]
 to identity-userstore-mongodb
 during the deployment of the product-is i face the following issue
 In my MongoDBUserStoreManager plugin i will be using org.json[2] lib
 for query purposes so it is a dependent for my plugin to work ,For the
 moment i manually added json lib to dropin folder to activate my bundle
 otherwise i will get following error when i open osgi console and checked
 Missing optionally imported package org.json_[20160212.0.0,2016021
 3.0.0).
 In order to activate the bundle need to add mongo-java-driver[4] also
 to dropins folder after that it will activate successfully,
 Is there any method to ship the json lib also with my bundle when
 deploying it to IS?
 [1]https://github.com/wso2/product-is/pull/668
 [2]https://github.com/wso2-extensions/identity-userstore-mongodb/pull/1
 [3]https://mvnrepository.com/artifact/org.json/json/20160212
 [4]https://mvnrepository.com/artifact/org.mongodb/mongo-java
 -driver/3.2.2

 Thanks,
 Asantha



 On Thu, Aug 18, 2016 at 2:19 AM, Tharindu Edirisinghe <
 tharin...@wso2.com> wrote:

> Hi Asntha,
>
> Please follow steps below to complete the project.
>
> 1. In your features [1] folder, you have to create etc folder and put
> feature.properties file in it. This is same as [2].
> 2. You have to create server.feature in [1]. Refer [3] and do the
> same. Make necessary modifications to pom file.
> 3. Once you do above, you can commit and push so that your PR [4] will
> automatically get these changes appended.
>
> Next step is to add this feature to IS product so when the product is
> built, the jar file is automatically packed to the product. For that,
> follow the instructions below.
>
> 4. Clone product-is [5] and do a clean repo build skipping tests. (you
> can just backup .m2 directory in your home and create an empty folder with
> name .m2. Then you can run mvn clean install -Dmaven.test.skip=true"
> command in product-is.
> 5. Once the product is built, you can get the zip file in
> modules/distribution folder. Run the product and check if you can access
> management console.
> 6. Next step is to build your feature so local m2 repository get the
> jar files of your feature.
> 7. Then, you can fork product-is and modify parent pom [6] adding a
> new property for your feature's version. Similar to below property, you 
> can
> add your own one.
>
> 5.1.1 .remote.version>
>
> 8.  Modify the p2-profile-get pom file [7] and include your feature
> there. You can search for "*user.store.remote.feature*" and following
> that, add details for your feature.
> 9. Then re-build the product-is, get the zip file, run it and in
> Management Console, check if mongodb userstore is listed. Also you can
> check if the jar file is packed in plugins.
> 10. Finally send a PR to product-is with these changes.
>
>
> [1] https://github.com/asanthamax/identity-userstore-mongodb/tre
> e/master/features
> [2] https://github.com/wso2-extensions/identity-userstore-remote
> /blob/master/features/etc/feature.properties
> [3] https://github.com/wso2-extensions/identity-userstore-remote
> /tree/master/features/org.wso2.carbon.identity.user.store.re
> mote.server.feature
> [4] https://github.com/wso2-extensions/identity-userstore-mongod
> b/pull/1
> [5] 

Re: [Dev] Preserving URL parameters across different pages in a dashboard

[Tanya Madurapperuma]

Can't you use the gadget state api to achieve your requirement? Please
refer to gadget-state.zip at [1] for reference.

[1]
https://github.com/wso2/product-ds/blob/master/modules/integration/tests-ui-integration/tests-ui/src/test/resources/gadgets

Thanks,
Tanya

On Fri, Aug 19, 2016 at 8:56 AM, Megala Uthayakumar  wrote:

> Hi Kalpa,
>
> I hope you are using carbon-dashboards  v2.0.0 [1] . In that version, when
> rendering the pages in view mode, we are manually appending all the query
> parameters from landing page[2] to other pages as well, because of that
> only you were able to get the same query parameters in other pages as well
> after reloading. But with the v2.0.1, we have already removed appending all
> the query parameters manually. So even that will not work in future
> versions. Is it possible to achieve this without appending the parameters
> to URL itself?
>
> [1] https://github.com/wso2/analytics-http/blob/master/pom.xml#L486
> [2] https://github.com/wso2/carbon-dashboards/blob/v2.0.0/
> apps/portal/theme/templates/dashboard.jag#L29
>
> On Thu, Aug 18, 2016 at 5:34 PM, Kalpa Welivitigoda 
> wrote:
>
>> Hi dev,
>>
>> I am working on http analytics dashboard, there we have a date time
>> picker gadget. Once a date time range is selected, the gadget publishes
>> those information to a topic so that other gadgets in the same page can
>> update accordingly.
>>
>> I have several pages, I am trying to preserve the date time selection
>> from one page to another.
>>
>> The approach I am trying is to update the url parameters (start_time and
>> end_time) when a date time selection is made. I am using
>> *window.parent.history.**pushState* for this purpose. This works fine.
>> But when I navigate to another page, these URL parameters are lost. If I
>> set the URL parameters and reload the page, they are preserved in the other
>> pages as well. I am looking for a way to accomplish this without reloading
>> the page.
>>
>> Have we come across a similar requirement before?
>>
>>
>> --
>> Best Regards,
>>
>> Kalpa Welivitigoda
>> Senior Software Engineer, WSO2 Inc. http://wso2.com
>> Email: kal...@wso2.com
>> Mobile: +94776509215
>>
>> [image: http://wso2.com/signature] 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Megala Uthayakumar
>
> Software Engineer
> Mobile : 0779967122
>



-- 
Tanya Madurapperuma

Senior Software Engineer,
WSO2 Inc. : wso2.com
Mobile : +94718184439
Blog : http://tanyamadurapperuma.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Final Evaluation] Proposal 21: [IS] Document Based NoSQL Support for WSO2 Identity Server Database

[Tharindu Edirisinghe]

Seems we'll have to find some alternative if we are to pack this to the
product.

@Asantha - Can you check if Apache has a library that provides similar
functionality.

Thanks,
TharinduE

On Fri, Aug 19, 2016 at 9:41 AM, Harsha Thirimanna  wrote:

> As in the license, there are some restrictions.
>
> http://www.json.org/license.html
>
> *Harsha Thirimanna*
> Associate Tech Lead | WSO2
>
> Email: hars...@wso2.com
> Mob: +94715186770
> Blog: http://harshathirimanna.blogspot.com/
> Twitter: http://twitter.com/harshathirimann
> Linked-In: linked-in: http://www.linkedin.com/pub/
> harsha-thirimanna/10/ab8/122
> 
>
> On Fri, Aug 19, 2016 at 9:30 AM, Tharindu Edirisinghe 
> wrote:
>
>> Thanks Asantha.
>>
>> @Johann/Darshana - Would it be possible to pack org.json [1] dependency
>> to the product itself ?
>>
>> [1] https://mvnrepository.com/artifact/org.json/json/20160212
>>
>> Regards,
>> TharinduE
>>
>> On Fri, Aug 19, 2016 at 12:48 AM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Tharindu,
>>>
>>> As you instructed i have finished all above process and i already sent a
>>> PR[1] to product-is with my modifications and earlier i have sent a PR[2]
>>> to identity-userstore-mongodb
>>> during the deployment of the product-is i face the following issue
>>> In my MongoDBUserStoreManager plugin i will be using org.json[2] lib for
>>> query purposes so it is a dependent for my plugin to work ,For the moment i
>>> manually added json lib to dropin folder to activate my bundle otherwise i
>>> will get following error when i open osgi console and checked
>>> Missing optionally imported package org.json_[20160212.0.0,2016021
>>> 3.0.0).
>>> In order to activate the bundle need to add mongo-java-driver[4] also to
>>> dropins folder after that it will activate successfully,
>>> Is there any method to ship the json lib also with my bundle when
>>> deploying it to IS?
>>> [1]https://github.com/wso2/product-is/pull/668
>>> [2]https://github.com/wso2-extensions/identity-userstore-mongodb/pull/1
>>> [3]https://mvnrepository.com/artifact/org.json/json/20160212
>>> [4]https://mvnrepository.com/artifact/org.mongodb/mongo-java
>>> -driver/3.2.2
>>>
>>> Thanks,
>>> Asantha
>>>
>>>
>>>
>>> On Thu, Aug 18, 2016 at 2:19 AM, Tharindu Edirisinghe <
>>> tharin...@wso2.com> wrote:
>>>
 Hi Asntha,

 Please follow steps below to complete the project.

 1. In your features [1] folder, you have to create etc folder and put
 feature.properties file in it. This is same as [2].
 2. You have to create server.feature in [1]. Refer [3] and do the same.
 Make necessary modifications to pom file.
 3. Once you do above, you can commit and push so that your PR [4] will
 automatically get these changes appended.

 Next step is to add this feature to IS product so when the product is
 built, the jar file is automatically packed to the product. For that,
 follow the instructions below.

 4. Clone product-is [5] and do a clean repo build skipping tests. (you
 can just backup .m2 directory in your home and create an empty folder with
 name .m2. Then you can run mvn clean install -Dmaven.test.skip=true"
 command in product-is.
 5. Once the product is built, you can get the zip file in
 modules/distribution folder. Run the product and check if you can access
 management console.
 6. Next step is to build your feature so local m2 repository get the
 jar files of your feature.
 7. Then, you can fork product-is and modify parent pom [6] adding a new
 property for your feature's version. Similar to below property, you can add
 your own one.

 5.1.1>>> .remote.version>

 8.  Modify the p2-profile-get pom file [7] and include your feature
 there. You can search for "*user.store.remote.feature*" and following
 that, add details for your feature.
 9. Then re-build the product-is, get the zip file, run it and in
 Management Console, check if mongodb userstore is listed. Also you can
 check if the jar file is packed in plugins.
 10. Finally send a PR to product-is with these changes.


 [1] https://github.com/asanthamax/identity-userstore-mongodb/tre
 e/master/features
 [2] https://github.com/wso2-extensions/identity-userstore-remote
 /blob/master/features/etc/feature.properties
 [3] https://github.com/wso2-extensions/identity-userstore-remote
 /tree/master/features/org.wso2.carbon.identity.user.store.re
 mote.server.feature
 [4] https://github.com/wso2-extensions/identity-userstore-mongod
 b/pull/1
 [5] https://github.com/wso2/product-is/
 [6] https://github.com/wso2/product-is/blob/master/pom.xml
 [7] https://github.com/wso2/product-is/blob/master/modules/p2-pr
 ofile-gen/pom.xml

 Thanks,
 TharinduE

 On Tue, Aug 16, 2016 at 1:13 PM, Asantha Thilina <
 

Re: [Dev] [AppM] SAML response signature validation in tenants

[Ishara Karunarathna]

Hi,

On Fri, Aug 19, 2016 at 9:47 AM, Darshana Gunawardana 
wrote:

>
>
> On Thu, Aug 18, 2016 at 4:43 PM, Rushmin Fernando 
> wrote:
>
>>
>> In current App Manager the service providers of tenants are getting
>> created in the super tenant space.
>>
>> We are in the process of creating the service providers in the relevant
>> tenants.
>>
>> In the app manager gateway, we use SAML SSO to authenticate the users,
>> and the aforementioned service providers are used.
>>
>> When it comes to validating the the SAML response signature, I can see
>> that we can re-use
>> *org.wso2.carbon.identity.sso.saml.util.SAMLSSOUtil::getX509CredentialImplForTenant()*
>>
>> As per the code, it uses the tenant key store to get the certificates.
>> And we can get the certificate by using the tenant name as the alias
>>
>> @IS team, do you see any issues with re-using this code in our gateway ?
>>
>
> Using this util makes gateway -which is a client side(sp) component-
> depends on the SAML component -which is server side(idp) component-
>
> IMO, its not nice to have that dependency. Once example is, this
> dependency will expose you a samlsso (idp) endpoint from the gateway. And
> also gateway profile would need to have saml components and makes you to
> have whole framework related dependencies as well.
>
> Thinking about client side (sp) components which already doing this there
> are two components we have in wso2 platform.
> 1. Carbon SAML authenticator : https://github.com/wso2-
> extensions/identity-carbon-auth-saml2
> 2. AS SSO valve : https://github.com/wso2/carbon-deployment/blob/4.7.x/
> components/webapp-mgt/org.wso2.carbon.webapp.mgt/src/
> main/java/org/wso2/carbon/webapp/mgt/sso/SAMLSignatureValidatorImpl.java
>
> Better to use utls from those two components, if we have such methods.
> Most suitable component for gateway is #2, since carbon authenticator don't
> have usage in gateway.
>
> I guess it's even worthy initiate separate component to handle all these
> saml utils, given that we have isolated components across the platform and
> we have to fix huge number of components if we identified a core issue.
>
+1 with darshans idea. And later better to have some common set of
libraries to handle this kind of scenarios.

>
> Thanks,
>
>
>> @Amila, in a cloud story do we need to configure the key aliases for each
>> tenant or can we live with the default alias (which is the tenant domain
>> name) ?
>>
>>
>>
>> --
>> *Best Regards*
>>
>> *Rushmin Fernando*
>> *Technical Lead*
>>
>> WSO2 Inc.  - Lean . Enterprise . Middleware
>>
>> mobile : +94772891266
>>
>>
>>
>
>
> --
> Regards,
>
>
> *Darshana Gunawardana*Associate Technical Lead
> WSO2 Inc.; http://wso2.com
>
> *E-mail: darsh...@wso2.com *
> *Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware
>



-- 
Ishara Karunarathna
Associate Technical Lead
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
+94717996791
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AppM] SAML response signature validation in tenants

[Darshana Gunawardana]

On Thu, Aug 18, 2016 at 4:43 PM, Rushmin Fernando  wrote:

>
> In current App Manager the service providers of tenants are getting
> created in the super tenant space.
>
> We are in the process of creating the service providers in the relevant
> tenants.
>
> In the app manager gateway, we use SAML SSO to authenticate the users, and
> the aforementioned service providers are used.
>
> When it comes to validating the the SAML response signature, I can see
> that we can re-use
> *org.wso2.carbon.identity.sso.saml.util.SAMLSSOUtil::getX509CredentialImplForTenant()*
>
> As per the code, it uses the tenant key store to get the certificates. And
> we can get the certificate by using the tenant name as the alias
>
> @IS team, do you see any issues with re-using this code in our gateway ?
>

Using this util makes gateway -which is a client side(sp) component-
depends on the SAML component -which is server side(idp) component-

IMO, its not nice to have that dependency. Once example is, this dependency
will expose you a samlsso (idp) endpoint from the gateway. And also gateway
profile would need to have saml components and makes you to have whole
framework related dependencies as well.

Thinking about client side (sp) components which already doing this there
are two components we have in wso2 platform.
1. Carbon SAML authenticator :
https://github.com/wso2-extensions/identity-carbon-auth-saml2
2. AS SSO valve :
https://github.com/wso2/carbon-deployment/blob/4.7.x/components/webapp-mgt/org.wso2.carbon.webapp.mgt/src/main/java/org/wso2/carbon/webapp/mgt/sso/SAMLSignatureValidatorImpl.java

Better to use utls from those two components, if we have such methods. Most
suitable component for gateway is #2, since carbon authenticator don't have
usage in gateway.

I guess it's even worthy initiate separate component to handle all these
saml utils, given that we have isolated components across the platform and
we have to fix huge number of components if we identified a core issue.

Thanks,


> @Amila, in a cloud story do we need to configure the key aliases for each
> tenant or can we live with the default alias (which is the tenant domain
> name) ?
>
>
>
> --
> *Best Regards*
>
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc.  - Lean . Enterprise . Middleware
>
> mobile : +94772891266
>
>
>


-- 
Regards,


*Darshana Gunawardana*Associate 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] [GSoC Final Evaluation] Proposal 21: [IS] Document Based NoSQL Support for WSO2 Identity Server Database

[Harsha Thirimanna]

As in the license, there are some restrictions.

http://www.json.org/license.html

*Harsha Thirimanna*
Associate Tech Lead | WSO2

Email: hars...@wso2.com
Mob: +94715186770
Blog: http://harshathirimanna.blogspot.com/
Twitter: http://twitter.com/harshathirimann
Linked-In: linked-in:
http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122


On Fri, Aug 19, 2016 at 9:30 AM, Tharindu Edirisinghe 
wrote:

> Thanks Asantha.
>
> @Johann/Darshana - Would it be possible to pack org.json [1] dependency to
> the product itself ?
>
> [1] https://mvnrepository.com/artifact/org.json/json/20160212
>
> Regards,
> TharinduE
>
> On Fri, Aug 19, 2016 at 12:48 AM, Asantha Thilina <
> asanthathil...@gmail.com> wrote:
>
>> Hi Tharindu,
>>
>> As you instructed i have finished all above process and i already sent a
>> PR[1] to product-is with my modifications and earlier i have sent a PR[2]
>> to identity-userstore-mongodb
>> during the deployment of the product-is i face the following issue
>> In my MongoDBUserStoreManager plugin i will be using org.json[2] lib for
>> query purposes so it is a dependent for my plugin to work ,For the moment i
>> manually added json lib to dropin folder to activate my bundle otherwise i
>> will get following error when i open osgi console and checked
>> Missing optionally imported package org.json_[20160212.0.0,20160213.0.0).
>> In order to activate the bundle need to add mongo-java-driver[4] also to
>> dropins folder after that it will activate successfully,
>> Is there any method to ship the json lib also with my bundle when
>> deploying it to IS?
>> [1]https://github.com/wso2/product-is/pull/668
>> [2]https://github.com/wso2-extensions/identity-userstore-mongodb/pull/1
>> [3]https://mvnrepository.com/artifact/org.json/json/20160212
>> [4]https://mvnrepository.com/artifact/org.mongodb/mongo-java-driver/3.2.2
>>
>> Thanks,
>> Asantha
>>
>>
>>
>> On Thu, Aug 18, 2016 at 2:19 AM, Tharindu Edirisinghe > > wrote:
>>
>>> Hi Asntha,
>>>
>>> Please follow steps below to complete the project.
>>>
>>> 1. In your features [1] folder, you have to create etc folder and put
>>> feature.properties file in it. This is same as [2].
>>> 2. You have to create server.feature in [1]. Refer [3] and do the same.
>>> Make necessary modifications to pom file.
>>> 3. Once you do above, you can commit and push so that your PR [4] will
>>> automatically get these changes appended.
>>>
>>> Next step is to add this feature to IS product so when the product is
>>> built, the jar file is automatically packed to the product. For that,
>>> follow the instructions below.
>>>
>>> 4. Clone product-is [5] and do a clean repo build skipping tests. (you
>>> can just backup .m2 directory in your home and create an empty folder with
>>> name .m2. Then you can run mvn clean install -Dmaven.test.skip=true"
>>> command in product-is.
>>> 5. Once the product is built, you can get the zip file in
>>> modules/distribution folder. Run the product and check if you can access
>>> management console.
>>> 6. Next step is to build your feature so local m2 repository get the jar
>>> files of your feature.
>>> 7. Then, you can fork product-is and modify parent pom [6] adding a new
>>> property for your feature's version. Similar to below property, you can add
>>> your own one.
>>>
>>> 5.1.1>> .remote.version>
>>>
>>> 8.  Modify the p2-profile-get pom file [7] and include your feature
>>> there. You can search for "*user.store.remote.feature*" and following
>>> that, add details for your feature.
>>> 9. Then re-build the product-is, get the zip file, run it and in
>>> Management Console, check if mongodb userstore is listed. Also you can
>>> check if the jar file is packed in plugins.
>>> 10. Finally send a PR to product-is with these changes.
>>>
>>>
>>> [1] https://github.com/asanthamax/identity-userstore-mongodb/tre
>>> e/master/features
>>> [2] https://github.com/wso2-extensions/identity-userstore-remote
>>> /blob/master/features/etc/feature.properties
>>> [3] https://github.com/wso2-extensions/identity-userstore-remote
>>> /tree/master/features/org.wso2.carbon.identity.user.store.
>>> remote.server.feature
>>> [4] https://github.com/wso2-extensions/identity-userstore-mongodb/pull/1
>>> [5] https://github.com/wso2/product-is/
>>> [6] https://github.com/wso2/product-is/blob/master/pom.xml
>>> [7] https://github.com/wso2/product-is/blob/master/modules/p2-pr
>>> ofile-gen/pom.xml
>>>
>>> Thanks,
>>> TharinduE
>>>
>>> On Tue, Aug 16, 2016 at 1:13 PM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi Tharindu,

 According to your instructions i have added the components folder with
 the mongodbuserstore package to my forked repo[1] and i also sent the pull
 request to origin also[2] i have refactor the main package to 
 *org.wso2.carbon.identity.user.store.mo
 **ngodb *
 expecting your 

Re: [Dev] [GSoC Final Evaluation] Proposal 21: [IS] Document Based NoSQL Support for WSO2 Identity Server Database

[Tharindu Edirisinghe]

Thanks Asantha.

@Johann/Darshana - Would it be possible to pack org.json [1] dependency to
the product itself ?

[1] https://mvnrepository.com/artifact/org.json/json/20160212

Regards,
TharinduE

On Fri, Aug 19, 2016 at 12:48 AM, Asantha Thilina 
wrote:

> Hi Tharindu,
>
> As you instructed i have finished all above process and i already sent a
> PR[1] to product-is with my modifications and earlier i have sent a PR[2]
> to identity-userstore-mongodb
> during the deployment of the product-is i face the following issue
> In my MongoDBUserStoreManager plugin i will be using org.json[2] lib for
> query purposes so it is a dependent for my plugin to work ,For the moment i
> manually added json lib to dropin folder to activate my bundle otherwise i
> will get following error when i open osgi console and checked
> Missing optionally imported package org.json_[20160212.0.0,20160213.0.0).
> In order to activate the bundle need to add mongo-java-driver[4] also to
> dropins folder after that it will activate successfully,
> Is there any method to ship the json lib also with my bundle when
> deploying it to IS?
> [1]https://github.com/wso2/product-is/pull/668
> [2]https://github.com/wso2-extensions/identity-userstore-mongodb/pull/1
> [3]https://mvnrepository.com/artifact/org.json/json/20160212
> [4]https://mvnrepository.com/artifact/org.mongodb/mongo-java-driver/3.2.2
>
> Thanks,
> Asantha
>
>
>
> On Thu, Aug 18, 2016 at 2:19 AM, Tharindu Edirisinghe 
> wrote:
>
>> Hi Asntha,
>>
>> Please follow steps below to complete the project.
>>
>> 1. In your features [1] folder, you have to create etc folder and put
>> feature.properties file in it. This is same as [2].
>> 2. You have to create server.feature in [1]. Refer [3] and do the same.
>> Make necessary modifications to pom file.
>> 3. Once you do above, you can commit and push so that your PR [4] will
>> automatically get these changes appended.
>>
>> Next step is to add this feature to IS product so when the product is
>> built, the jar file is automatically packed to the product. For that,
>> follow the instructions below.
>>
>> 4. Clone product-is [5] and do a clean repo build skipping tests. (you
>> can just backup .m2 directory in your home and create an empty folder with
>> name .m2. Then you can run mvn clean install -Dmaven.test.skip=true"
>> command in product-is.
>> 5. Once the product is built, you can get the zip file in
>> modules/distribution folder. Run the product and check if you can access
>> management console.
>> 6. Next step is to build your feature so local m2 repository get the jar
>> files of your feature.
>> 7. Then, you can fork product-is and modify parent pom [6] adding a new
>> property for your feature's version. Similar to below property, you can add
>> your own one.
>>
>> 5.1.1> .remote.version>
>>
>> 8.  Modify the p2-profile-get pom file [7] and include your feature
>> there. You can search for "*user.store.remote.feature*" and following
>> that, add details for your feature.
>> 9. Then re-build the product-is, get the zip file, run it and in
>> Management Console, check if mongodb userstore is listed. Also you can
>> check if the jar file is packed in plugins.
>> 10. Finally send a PR to product-is with these changes.
>>
>>
>> [1] https://github.com/asanthamax/identity-userstore-mongodb/tre
>> e/master/features
>> [2] https://github.com/wso2-extensions/identity-userstore-remote
>> /blob/master/features/etc/feature.properties
>> [3] https://github.com/wso2-extensions/identity-userstore-remote
>> /tree/master/features/org.wso2.carbon.identity.user.stor
>> e.remote.server.feature
>> [4] https://github.com/wso2-extensions/identity-userstore-mongodb/pull/1
>> [5] https://github.com/wso2/product-is/
>> [6] https://github.com/wso2/product-is/blob/master/pom.xml
>> [7] https://github.com/wso2/product-is/blob/master/modules/p2-
>> profile-gen/pom.xml
>>
>> Thanks,
>> TharinduE
>>
>> On Tue, Aug 16, 2016 at 1:13 PM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Tharindu,
>>>
>>> According to your instructions i have added the components folder with
>>> the mongodbuserstore package to my forked repo[1] and i also sent the pull
>>> request to origin also[2] i have refactor the main package to 
>>> *org.wso2.carbon.identity.user.store.mo
>>> **ngodb *
>>> expecting your feedback
>>> [1] https://github.com/asanthamax/identity-userstore-mongodb
>>> [2] https://github.com/wso2-extensions/identity-userstore-mongodb/pull/1
>>> Thanks,
>>> Asantha
>>>
>>> On Tue, Aug 16, 2016 at 2:45 AM, Tharindu Edirisinghe <
>>> tharin...@wso2.com> wrote:
>>>
 Hi Asantha,

 Now that you have completed the project [1], for the final evaluation,
 you need to contribute your code to WSO2 codebase.

 For that, we have created the repository [2].

 You can refer [3] to get some idea about the package structure of the
 repo.

Re: [Dev] ESB5.0.0-RC4 | Intermittent Exception in the Cluster Environment

[Chanaka Fernando]

@Chandana: You are correct. This is not related to registry.

@Chaminda: In the ESB home page, there is this status information section
where we check the server up time by contacting the admin service and
display in that page. This looks like that this admin service call (which
happens automatically through ajax calls) is not getting response due to
some intermittent issue. This can be due to invalid CSRF token on browser
session is invalidated. This does not affect the functionality of the
server and we may be able to gracefully handle this at the code level.
Please report a public JIRA so that we can fix this in a future release.

On Thu, Aug 18, 2016 at 5:39 PM, Chandana Napagoda 
wrote:

> Hi Chaminda/Chanaka,
>
> This thread death has occurred from the "system_status_ajaxprocessor" JSP
> file and this is not related to the registry.
>
> Regards,
> Chandana
>
> On Thu, Aug 18, 2016 at 5:26 PM, Chaminda Jayawardena 
> wrote:
>
>> Hi All,
>>
>> Noticed below exception[2] in the logs of the mgt node of an ESB5.0.0-RC4
>> cluster environment. And also this has occurred several times in that node.
>>
>> Though line numbers are different, found a similar kind of issue is
>> reported here [1], but we didn't access the registry from mgt console, in
>> this matter.
>>
>> [1] https://wso2.org/jira/browse/REGISTRY-3046
>>
>> [2]
>> TID: [-1234] [] [2016-08-18 09:03:54,506] ERROR
>> {org.apache.axis2.rpc.receivers.RPCMessageReceiver} -  Exception
>> occurred while trying to invoke service method getServerData
>> {org.apache.axis2.rpc.receivers.RPCMessageReceiver}
>> java.lang.reflect.InvocationTargetException
>> at sun.reflect.GeneratedMethodAccessor201.invoke(Unknown Source)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>> thodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(
>> RPCUtil.java:212)
>> at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusi
>> nessLogic(RPCMessageReceiver.java:117)
>> at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invo
>> keBusinessLogic(AbstractInOutMessageReceiver.java:40)
>> at org.apache.axis2.receivers.AbstractMessageReceiver.receive(A
>> bstractMessageReceiver.java:110)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>> at org.apache.axis2.transport.local.LocalTransportReceiver.proc
>> essMessage(LocalTransportReceiver.java:169)
>> at org.apache.axis2.transport.local.LocalTransportReceiver.proc
>> essMessage(LocalTransportReceiver.java:82)
>> at org.wso2.carbon.core.transports.local.CarbonLocalTransportSe
>> nder.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
>> at org.apache.axis2.transport.local.LocalTransportSender.invoke
>> (LocalTransportSender.java:77)
>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>> at org.apache.axis2.description.OutInAxisOperationClient.send(O
>> utInAxisOperation.java:430)
>> at org.apache.axis2.description.OutInAxisOperationClient.execut
>> eImpl(OutInAxisOperation.java:225)
>> at org.apache.axis2.client.OperationClient.execute(OperationCli
>> ent.java:149)
>> at org.wso2.carbon.server.admin.stub.ServerAdminStub.getServerD
>> ata(ServerAdminStub.java:1621)
>> at org.wso2.carbon.server.admin.ui.ServerAdminClient.getServerD
>> ata(ServerAdminClient.java:131)
>> at org.apache.jsp.server_002dadmin.system_005fstatus_005fajaxpr
>> ocessor_jsp._jspService(system_005fstatus_005fajaxprocessor_jsp.java:165)
>> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at org.apache.jasper.servlet.JspServletWrapper.service(JspServl
>> etWrapper.java:439)
>> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServl
>> et.java:395)
>> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
>> at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.se
>> rvice(ContextPathServletAdaptor.java:37)
>> at org.eclipse.equinox.http.servlet.internal.ServletRegistratio
>> n.service(ServletRegistration.java:61)
>> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce
>> ssAlias(ProxyServlet.java:128)
>> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi
>> ce(ProxyServlet.java:68)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service
>> (DelegationServlet.java:68)
>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFi
>> lter(ApplicationFilterChain.java:303)
>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(App
>> licationFilterChain.java:208)
>> at 

Re: [Dev] Preserving URL parameters across different pages in a dashboard

[Megala Uthayakumar]

Hi Kalpa,

I hope you are using carbon-dashboards  v2.0.0 [1] . In that version, when
rendering the pages in view mode, we are manually appending all the query
parameters from landing page[2] to other pages as well, because of that
only you were able to get the same query parameters in other pages as well
after reloading. But with the v2.0.1, we have already removed appending all
the query parameters manually. So even that will not work in future
versions. Is it possible to achieve this without appending the parameters
to URL itself?

[1] https://github.com/wso2/analytics-http/blob/master/pom.xml#L486
[2]
https://github.com/wso2/carbon-dashboards/blob/v2.0.0/apps/portal/theme/templates/dashboard.jag#L29

On Thu, Aug 18, 2016 at 5:34 PM, Kalpa Welivitigoda  wrote:

> Hi dev,
>
> I am working on http analytics dashboard, there we have a date time picker
> gadget. Once a date time range is selected, the gadget publishes those
> information to a topic so that other gadgets in the same page can update
> accordingly.
>
> I have several pages, I am trying to preserve the date time selection from
> one page to another.
>
> The approach I am trying is to update the url parameters (start_time and
> end_time) when a date time selection is made. I am using
> *window.parent.history.**pushState* for this purpose. This works fine.
> But when I navigate to another page, these URL parameters are lost. If I
> set the URL parameters and reload the page, they are preserved in the other
> pages as well. I am looking for a way to accomplish this without reloading
> the page.
>
> Have we come across a similar requirement before?
>
>
> --
> Best Regards,
>
> Kalpa Welivitigoda
> Senior Software Engineer, WSO2 Inc. http://wso2.com
> Email: kal...@wso2.com
> Mobile: +94776509215
>
> [image: http://wso2.com/signature] 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Megala Uthayakumar

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

Re: [Dev] GSoC2016-Contact Development Team Feature

[Kavith Lokuhewage]

Hi Nathiesha,

You already have two standalone github repos for the plugin and
micro-service. Furthermore, you have a fork of devs-kernel repo with the
code for the plugin is merged - the one you have prepared to send the pull
request.

Since there are multiple places and we cannot submit a single link for them
- in my point of view - the best option is to write a blog post as they
have suggested. You can include the links to individual repos and forked
repo with a filter for your commits. Importantly, you can put the link for
pull request too - once you sent it.

This way, everyone will have a clear picture of your work and the best part
- what is the final work that is going to be merged into WSO2 repository.

Thanks,

*Kavith Lokuhewage*
Senior Software Engineer
WSO2 Inc. - http://wso2.com
lean . enterprise . middleware
Mobile - +94779145123
Linkedin   Twitter


On Thu, Aug 18, 2016 at 11:55 AM, Nathiesha Maddage <
nathieshamadd...@gmail.com> wrote:

> Hi,
>
> I have completed almost all of the coding part now, and working with
> fixing a few left errors and tidying the code.
>
> I plan to submit the plugin project, feature project and the documentation
> as the deliverable.
> For the final submission, I need to upload a URL that contains our
> project. For that Google has provided certain examples such as the link of
> Git Hub commits, a web page or a blog post, public folder in Google Drive
> etc. [1]
>
> What would be the best way of submission, for our project?
>
> [1]. https://developers.google.com/open-source/gsoc/help/work-product
>
>
> Thanks and regards
>
> Nathiesha
>
> On Thu, Aug 11, 2016 at 4:40 PM, Kavith Lokuhewage 
> wrote:
>
>> Hi Nathiesha,
>>
>> Great! We can have the meeting at 3.00pm to 4.00pm tomorrow. I will send
>> the invitation. Meanwhile, please push the latest changes to github before
>> the meeting.
>>
>> Thanks,
>>
>> *Kavith Lokuhewage*
>> Senior Software Engineer
>> WSO2 Inc. - http://wso2.com
>> lean . enterprise . middleware
>> Mobile - +94779145123
>> Linkedin 
>> Twitter 
>>
>> On Thu, Aug 11, 2016 at 4:35 PM, Nathiesha Maddage <
>> nathieshamadd...@gmail.com> wrote:
>>
>>> Hi Kavith,
>>>
>>> I externalized the credentials in micro-service code and implemented the
>>> extension point. I plan to start on OSGI services part once I finalize the
>>> remaining small tasks in these sections.
>>>
>>> How about tomorrow evening for the next meeting? I have lectures in the
>>> morning. So it would be easy if we can arrange the meeting after 2 pm.
>>>
>>> Thanks and regards
>>> Nathiesha
>>>
>>> On Thu, Aug 11, 2016 at 11:42 AM, Kavith Lokuhewage 
>>> wrote:
>>>
 Hi Nathiesha,

 How is the progress on remaining tasks? As per the previous update, you
 are already done with configuring maven build + creating a basic
 micro-service for publishing reports, aren't you?

 The remaining work was to externalize hard coded credentials in
 micro-service code, implement the extension point for providing different
 JIRA keys to report errors for specific java packages and define an OSGI
 service to be able to contribute publishers via other eclipse plugins - if
 needed in future.

 It would be great if we can finalize these soon as we are reaching
 towards the end of GSOC program. Please suggest a time for a meeting
 tomorrow. We can discuss about the issues you are facing - if any - and
 discuss the plat to wrap the rest of the work by end of next week.

 Thanks,

 *Kavith Lokuhewage*
 Senior Software Engineer
 WSO2 Inc. - http://wso2.com
 lean . enterprise . middleware
 Mobile - +94779145123
 Linkedin 
 Twitter 

 On Fri, Aug 5, 2016 at 2:06 PM, Kavith Lokuhewage 
 wrote:

> Hi Nathiesha,
>
> Please join the hangout https://hangouts.googl
> e.com/hangouts/_/wso2.com/kavith
>
> Thanks,
>
> *Kavith Lokuhewage*
> Senior Software Engineer
> WSO2 Inc. - http://wso2.com
> lean . enterprise . middleware
> Mobile - +94779145123
> Linkedin 
> Twitter 
>
> On Fri, Aug 5, 2016 at 11:49 AM, Kavith Lokuhewage 
> wrote:
>
>> Hi Nathiesha,
>>
>> Great! I have sent you the invitation.
>>
>> Thanks,
>>
>> *Kavith Lokuhewage*
>> Senior Software Engineer
>> WSO2 Inc. - http://wso2.com
>> lean . enterprise . middleware
>> Mobile - +94779145123
>> Linkedin 
>> Twitter 

Re: [Dev] rdbms table data view

[Grainier Perera]

Hi Aneela,

First of all if you haven't change 'WSO2_CARBON_DB'
data-source configurations, by default it will use H2 db. Therefore,
the 'ftp_log_table'
table will get created in H2. You can enable and use built-in H2 browser to
view the data  [1]. Moreover, data added to the RDBMS tables will be stored
permanently. However, you can have a delete query from Siddhi to purge data.

[1] http://www.vitharana.org/2012/04/how-to-browse-h2-database-of-wso2.html

Regards,

On Thu, Aug 18, 2016 at 9:24 PM, Aneela Safdar  wrote:

> I have created an rdbms table in an execution plan and write below query
>
> @from(eventtable = 'rdbms' , datasource.name = 'WSO2_CARBON_DB' ,
> table.name ='ftp_log_table')
> define table ftp_log_table (ts string, uid string, id_orig_h string,
> id_orig_p int, id_resp_h string, id_resp_p int, user string, password
> string,command string, arg string, mime_type string, file_size string,
> reply_code int, reply_msg string);
>
> from FTPInStream
> select *
> insert into ftp_log_table;
>
> There is no error of invalidity but I haven't created this table before in
> the database. Also how can I view data in it? Is it going to store data
> permanently or a long period of time for further correspondence?
>
> Regards,
> Aneela Safdar
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Grainier Perera
Software Engineer
Mobile : +94716122384
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Dockerfiles test framework] Updating repository name

[Abhishek Tiwari]

I think I have found the issue, it was due to fully qualified path
referring to old project name so go get tried to clone that as well.

Thanks
Abhishek

On Thursday, August 18, 2016, Abhishek Tiwari 
wrote:

> Thanks Chamila.
>
> Updated repository URL [1]. I have also added instructions specific to
> Mac, Windows and Linux users.
>
> I do not have any setting on local git config, I even cleaned everything
> did a restart, still no luck. The weird part is, git clone works fine with
> the changed repo name. Will keep looking.
>
> Thanks
> Abhishek
>
> [1]. https://github.com/abhishek0198/wso2dockerfiles-test-framework
>
> On Thu, Aug 18, 2016 at 12:45 PM, Chamila De Alwis  > wrote:
>
>> Hi Abhishek,
>>
>> I think the proper name should be wso2dockerfiles-test-framework.
>>
>> Check the git remotes that are in the git config in your local when doing
>> go get. It might have the old remote name that gets temporary redirected to
>> the new one.
>>
>>
>>
>> Regards,
>> Chamila de Alwis
>> Committer and PMC Member - Apache Stratos
>> Senior Software Engineer | WSO2
>> Blog: https://medium.com/@chamilad
>>
>>
>>
>> On Thu, Aug 18, 2016 at 2:39 PM, Abhishek Tiwari <
>> abhishek.tiwari0...@gmail.com
>> > wrote:
>>
>>> Hi All,
>>>
>>> I have changed the name of github repository from "test-framework" to
>>> "wsodockerfiles-testframework". The updated URL is [1].
>>>
>>> For some reason, when I do "go get ", it is cloning both
>>> old and new repo with same content. However, when I do "git clone
>>> ", I get the renamed repo cloned. I will try to see what is wrong
>>> with go get.
>>>
>>> Thanks
>>> Abhishek
>>>
>>> [1]. https://github.com/abhishek0198/wsodockerfiles-testframework
>>>
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Dockerfiles test framework] Updating repository name

[Abhishek Tiwari]

Thanks Chamila.

Updated repository URL [1]. I have also added instructions specific to Mac,
Windows and Linux users.

I do not have any setting on local git config, I even cleaned everything
did a restart, still no luck. The weird part is, git clone works fine with
the changed repo name. Will keep looking.

Thanks
Abhishek

[1]. https://github.com/abhishek0198/wso2dockerfiles-test-framework

On Thu, Aug 18, 2016 at 12:45 PM, Chamila De Alwis 
wrote:

> Hi Abhishek,
>
> I think the proper name should be wso2dockerfiles-test-framework.
>
> Check the git remotes that are in the git config in your local when doing
> go get. It might have the old remote name that gets temporary redirected to
> the new one.
>
>
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Senior Software Engineer | WSO2
> Blog: https://medium.com/@chamilad
>
>
>
> On Thu, Aug 18, 2016 at 2:39 PM, Abhishek Tiwari <
> abhishek.tiwari0...@gmail.com> wrote:
>
>> Hi All,
>>
>> I have changed the name of github repository from "test-framework" to
>> "wsodockerfiles-testframework". The updated URL is [1].
>>
>> For some reason, when I do "go get ", it is cloning both old
>> and new repo with same content. However, when I do "git clone ",
>> I get the renamed repo cloned. I will try to see what is wrong with go get.
>>
>> Thanks
>> Abhishek
>>
>> [1]. https://github.com/abhishek0198/wsodockerfiles-testframework
>>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Dockerfiles test framework] Updating repository name

[Chamila De Alwis]

Hi Abhishek,

I think the proper name should be wso2dockerfiles-test-framework.

Check the git remotes that are in the git config in your local when doing
go get. It might have the old remote name that gets temporary redirected to
the new one.



Regards,
Chamila de Alwis
Committer and PMC Member - Apache Stratos
Senior Software Engineer | WSO2
Blog: https://medium.com/@chamilad



On Thu, Aug 18, 2016 at 2:39 PM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:

> Hi All,
>
> I have changed the name of github repository from "test-framework" to
> "wsodockerfiles-testframework". The updated URL is [1].
>
> For some reason, when I do "go get ", it is cloning both old
> and new repo with same content. However, when I do "git clone ",
> I get the renamed repo cloned. I will try to see what is wrong with go get.
>
> Thanks
> Abhishek
>
> [1]. https://github.com/abhishek0198/wsodockerfiles-testframework
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [GSoC Dockerfiles test framework] Updating repository name

[Abhishek Tiwari]

Hi All,

I have changed the name of github repository from "test-framework" to
"wsodockerfiles-testframework". The updated URL is [1].

For some reason, when I do "go get ", it is cloning both old
and new repo with same content. However, when I do "git clone ",
I get the renamed repo cloned. I will try to see what is wrong with go get.

Thanks
Abhishek

[1]. https://github.com/abhishek0198/wsodockerfiles-testframework
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Final Evaluation] Proposal 21: [IS] Document Based NoSQL Support for WSO2 Identity Server Database

[Asantha Thilina]

Hi Tharindu,

As you instructed i have finished all above process and i already sent a
PR[1] to product-is with my modifications and earlier i have sent a PR[2]
to identity-userstore-mongodb
during the deployment of the product-is i face the following issue
In my MongoDBUserStoreManager plugin i will be using org.json[2] lib for
query purposes so it is a dependent for my plugin to work ,For the moment i
manually added json lib to dropin folder to activate my bundle otherwise i
will get following error when i open osgi console and checked
Missing optionally imported package org.json_[20160212.0.0,20160213.0.0).
In order to activate the bundle need to add mongo-java-driver[4] also to
dropins folder after that it will activate successfully,
Is there any method to ship the json lib also with my bundle when deploying
it to IS?
[1]https://github.com/wso2/product-is/pull/668
[2]https://github.com/wso2-extensions/identity-userstore-mongodb/pull/1
[3]https://mvnrepository.com/artifact/org.json/json/20160212
[4]https://mvnrepository.com/artifact/org.mongodb/mongo-java-driver/3.2.2

Thanks,
Asantha



On Thu, Aug 18, 2016 at 2:19 AM, Tharindu Edirisinghe 
wrote:

> Hi Asntha,
>
> Please follow steps below to complete the project.
>
> 1. In your features [1] folder, you have to create etc folder and put
> feature.properties file in it. This is same as [2].
> 2. You have to create server.feature in [1]. Refer [3] and do the same.
> Make necessary modifications to pom file.
> 3. Once you do above, you can commit and push so that your PR [4] will
> automatically get these changes appended.
>
> Next step is to add this feature to IS product so when the product is
> built, the jar file is automatically packed to the product. For that,
> follow the instructions below.
>
> 4. Clone product-is [5] and do a clean repo build skipping tests. (you can
> just backup .m2 directory in your home and create an empty folder with name
> .m2. Then you can run mvn clean install -Dmaven.test.skip=true" command in
> product-is.
> 5. Once the product is built, you can get the zip file in
> modules/distribution folder. Run the product and check if you can access
> management console.
> 6. Next step is to build your feature so local m2 repository get the jar
> files of your feature.
> 7. Then, you can fork product-is and modify parent pom [6] adding a new
> property for your feature's version. Similar to below property, you can add
> your own one.
>
> 5.1.1 userstore.remote.version>
>
> 8.  Modify the p2-profile-get pom file [7] and include your feature there.
> You can search for "*user.store.remote.feature*" and following that, add
> details for your feature.
> 9. Then re-build the product-is, get the zip file, run it and in
> Management Console, check if mongodb userstore is listed. Also you can
> check if the jar file is packed in plugins.
> 10. Finally send a PR to product-is with these changes.
>
>
> [1] https://github.com/asanthamax/identity-userstore-mongodb/
> tree/master/features
> [2] https://github.com/wso2-extensions/identity-userstore-
> remote/blob/master/features/etc/feature.properties
> [3] https://github.com/wso2-extensions/identity-userstore-
> remote/tree/master/features/org.wso2.carbon.identity.user.
> store.remote.server.feature
> [4] https://github.com/wso2-extensions/identity-userstore-mongodb/pull/1
> [5] https://github.com/wso2/product-is/
> [6] https://github.com/wso2/product-is/blob/master/pom.xml
> [7] https://github.com/wso2/product-is/blob/master/
> modules/p2-profile-gen/pom.xml
>
> Thanks,
> TharinduE
>
> On Tue, Aug 16, 2016 at 1:13 PM, Asantha Thilina  > wrote:
>
>> Hi Tharindu,
>>
>> According to your instructions i have added the components folder with
>> the mongodbuserstore package to my forked repo[1] and i also sent the pull
>> request to origin also[2] i have refactor the main package to 
>> *org.wso2.carbon.identity.user.store.mo
>> **ngodb *
>> expecting your feedback
>> [1] https://github.com/asanthamax/identity-userstore-mongodb
>> [2] https://github.com/wso2-extensions/identity-userstore-mongodb/pull/1
>> Thanks,
>> Asantha
>>
>> On Tue, Aug 16, 2016 at 2:45 AM, Tharindu Edirisinghe > > wrote:
>>
>>> Hi Asantha,
>>>
>>> Now that you have completed the project [1], for the final evaluation,
>>> you need to contribute your code to WSO2 codebase.
>>>
>>> For that, we have created the repository [2].
>>>
>>> You can refer [3] to get some idea about the package structure of the
>>> repo.
>>>
>>> Further, you can refactor your project and rename the main package to 
>>> *org.wso2.carbon.identity.user.store.mo
>>> **ngodb*.
>>>
>>> You can send a pull request with these.
>>>
>>> I will help you with writing the feature and creating the parent pom
>>> file later.
>>>
>>>
>>> [1] https://docs.wso2.com/display/GSoC/Project+Proposals+for+201
>>> 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Thank you

On Thursday, August 18, 2016, Imesh Gunaratne  wrote:

>
>
> On Thu, Aug 18, 2016 at 7:56 PM, Osura Rathnayake  > wrote:
>
>> Hi Imesh,
>>
>> Yes now I understand that creating VM images for each product profile
>> will not going to work out.
>>
>> Can you please give me a step by step guideline on what I should do to
>> achieve this?
>>
>
> ​Please refer [1] and [2].
>
> [1] https://github.com/wso2/puppet-modules
> [2] https://docs.wso2.com/display/PM210/WSO2+Puppet+Modules+Documentation​
>
>
> ​Thanks​
>
> .
>>  Thank you,
>>
>> On Wed, Aug 17, 2016 at 10:41 PM, Imesh Gunaratne > > wrote:
>>
>>>
>>>
>>> On Wed, Aug 17, 2016 at 10:19 PM, Imesh Gunaratne >> > wrote:


 ​There are many spelling mistakes on this file [2], please review it
 again.

>>>
>>> ​Correction: s/on this file/in this file/g
>>>
>>> Thanks
>>> ​
>>>
>>>
 Overall I see very less attention to detail in this repository and the
 membership scheme implementation.


> There I mentioned the things that should be kept in mind while
> configuring wso2 AS and did not go in to detail on hot to configure as it
> can be found in the wso2 documentation. Would that be okay?
>

 ​I don't think this is helpful. Without having detailed steps users
 might not be able to do a complete deployment.

 Few questions:

- How do you create a distributed deployment​

​of AS ​or any other product (say for an example WSO2 API-M) with
this approach? As I explained earlier creating a VM image per product
profile is an unnecessary overhead (time consumption, disk space needed,
maintenance, etc).

- ​What would be the approach of applying​
 a patch or do
​ing​
a configuration change in a such deployment?

 ​IMO it is really important to understand the concepts well and solve
 problems with the most efficient manner. Otherwise the outcome of this
 project might not be usable.

 [2] https://github.com/osuran/azure-artifacts/issues/2

 Thanks


> user do not need to change anything in template.json, so should I
> explain the parameters in that too?
>
> in the paramters.json, except for the vm_image parameter, all of the
> parameters are just for the naming of the elements that you find in a VM,
> for an example, the name of the network interface. Therefore I have given
> instructions on how to set the vm_image parameter.
>
> current progress: The script which was generated by Azure does not
> have the capability to add a custom VM image. I modified it so that now it
> has that capability. Normally when you login to azure from CLI, it needs
> web interaction to authenticate. I modified deploy.sh in a way that it
> authenticates the user without web interaction, this will be useful if we
> run deploy.sh in a minimal version of linux.
>
> currently I'm working on adding deployment patterns to deploy.sh and
> undeploy.sh
>
>
> [1] https://github.com/osuran/azure-artifacts/tree/master/wso2as
>
> thank you,
>
> On Tue, Aug 16, 2016 at 10:10 AM, Isuru Haththotuwa  > wrote:
>
>> Hi Osura,
>>
>> Can you please send an update on the current status?
>>
>> On Mon, Aug 15, 2016 at 10:11 AM, Isuru Haththotuwa > > wrote:
>>
>>> Hi Osura,
>>>
>>> Few comments regarding the README:
>>>
>>>1. Need to mention how to configure the VM with the product pack
>>>and JDK for Azure
>>>2. There are lot of parameters in the template and parameters
>>>json files; please explain what a user needs to change there.
>>>3. The deploy script should be able to handle both standalone
>>>and distributed deployment pattern for the product. Refer to K8s 
>>> repository
>>>as a reference [1]
>>>4. Highlights the commands that a user needs to issue clearly
>>>
>>> Please note a user should be able to deploy a WSO2 product in Azure
>>> by following the README. If we provide abstract and incomplete
>>> instructions, user experience will not be good.
>>>
>>> On Mon, Aug 15, 2016 at 9:05 AM, Osura Rathnayake <
>>> osura...@gmail.com
>>> > wrote:
>>>
 Hi Imesh  /Isuru,

 Please accept my apologies for the delayed response.

 There is a MySQL instance in the Azure marketplace, we can
 straightaway deploy that. It's a 

Re: [Dev] [GSOC 16] Initial Project Progress

[Imesh Gunaratne]

On Thu, Aug 18, 2016 at 7:56 PM, Osura Rathnayake 
wrote:

> Hi Imesh,
>
> Yes now I understand that creating VM images for each product profile will
> not going to work out.
>
> Can you please give me a step by step guideline on what I should do to
> achieve this?
>

​Please refer [1] and [2].

[1] https://github.com/wso2/puppet-modules
[2] https://docs.wso2.com/display/PM210/WSO2+Puppet+Modules+Documentation​


​Thanks​

.
>  Thank you,
>
> On Wed, Aug 17, 2016 at 10:41 PM, Imesh Gunaratne  wrote:
>
>>
>>
>> On Wed, Aug 17, 2016 at 10:19 PM, Imesh Gunaratne  wrote:
>>>
>>>
>>> ​There are many spelling mistakes on this file [2], please review it
>>> again.
>>>
>>
>> ​Correction: s/on this file/in this file/g
>>
>> Thanks
>> ​
>>
>>
>>> Overall I see very less attention to detail in this repository and the
>>> membership scheme implementation.
>>>
>>>
 There I mentioned the things that should be kept in mind while
 configuring wso2 AS and did not go in to detail on hot to configure as it
 can be found in the wso2 documentation. Would that be okay?

>>>
>>> ​I don't think this is helpful. Without having detailed steps users
>>> might not be able to do a complete deployment.
>>>
>>> Few questions:
>>>
>>>- How do you create a distributed deployment​
>>>
>>>​of AS ​or any other product (say for an example WSO2 API-M) with
>>>this approach? As I explained earlier creating a VM image per product
>>>profile is an unnecessary overhead (time consumption, disk space needed,
>>>maintenance, etc).
>>>
>>>- ​What would be the approach of applying​
>>> a patch or do
>>>​ing​
>>>a configuration change in a such deployment?
>>>
>>> ​IMO it is really important to understand the concepts well and solve
>>> problems with the most efficient manner. Otherwise the outcome of this
>>> project might not be usable.
>>>
>>> [2] https://github.com/osuran/azure-artifacts/issues/2
>>>
>>> Thanks
>>>
>>>
 user do not need to change anything in template.json, so should I
 explain the parameters in that too?

 in the paramters.json, except for the vm_image parameter, all of the
 parameters are just for the naming of the elements that you find in a VM,
 for an example, the name of the network interface. Therefore I have given
 instructions on how to set the vm_image parameter.

 current progress: The script which was generated by Azure does not have
 the capability to add a custom VM image. I modified it so that now it has
 that capability. Normally when you login to azure from CLI, it needs web
 interaction to authenticate. I modified deploy.sh in a way that it
 authenticates the user without web interaction, this will be useful if we
 run deploy.sh in a minimal version of linux.

 currently I'm working on adding deployment patterns to deploy.sh and
 undeploy.sh


 [1] https://github.com/osuran/azure-artifacts/tree/master/wso2as

 thank you,

 On Tue, Aug 16, 2016 at 10:10 AM, Isuru Haththotuwa 
 wrote:

> Hi Osura,
>
> Can you please send an update on the current status?
>
> On Mon, Aug 15, 2016 at 10:11 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Few comments regarding the README:
>>
>>1. Need to mention how to configure the VM with the product pack
>>and JDK for Azure
>>2. There are lot of parameters in the template and parameters
>>json files; please explain what a user needs to change there.
>>3. The deploy script should be able to handle both standalone and
>>distributed deployment pattern for the product. Refer to K8s 
>> repository as
>>a reference [1]
>>4. Highlights the commands that a user needs to issue clearly
>>
>> Please note a user should be able to deploy a WSO2 product in Azure
>> by following the README. If we provide abstract and incomplete
>> instructions, user experience will not be good.
>>
>> On Mon, Aug 15, 2016 at 9:05 AM, Osura Rathnayake > > wrote:
>>
>>> Hi Imesh  /Isuru,
>>>
>>> Please accept my apologies for the delayed response.
>>>
>>> There is a MySQL instance in the Azure marketplace, we can
>>> straightaway deploy that. It's a Ubuntu 16.04.1 LTS with MySQL 
>>> installed. I
>>> think it's better to use it as there won't be licensing issues with it.
>>>
>>> Please find the updated readme file in [1] which includes steps on
>>> how to deploy WSO2 AS in Azure.
>>>
>>
>>> About the undeploy.sh, should it remove the VM entirely or just the
>>> WSO2 AS instance?
>>>
>> Ideally we should be able to re-use the VM, so IMHO removing only the
>> instance is ok.
>>
>> [1]. 

Re: [Dev] [GSoC Dockerfiles] Added ability to run smoke tests from test framework

[Abhishek Tiwari]

Hi Thanuja,

Thanks a lot of using the test framework and pointing out the issue. The
check of errors in carbon log is dumb at this point. I will change it look
for the correct logging level to find errors.

Imesh,
Sincerely appreciate code level feedback and creating issues on Github. I
will address all these shortly.

Thanks
Abhishek

On Thu, Aug 18, 2016 at 2:39 AM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrote:

> Hi Abhishek,
>
> Great work on Dockerfiles test framework!!! I have used the test framework
> to check the flow of building and running WSO2 BPS 3.5.1 docker image.
> According to the framework log[1], the test fails because of an error in
> the carbon server log. But when I check the carbon server log, there were
> no *ERROR* logs and it has 'error' as part of a word in line[2].
>
> For this scenario, we should not make the test to be failed. I think
> instead of simply grepping the 'error' word as in[3], we should grep the
> *ERROR* logs.
>
> [1].
> 2016/08/18 14:20:28 main.go:151: Starting test setup up
> 2016/08/18 14:20:28 main.go:154: Completed test setup up
> 2016/08/18 14:20:28 main.go:106: Running tests for wso2bps, 3.5.1, using
> puppet provisioning, under default platform.
> 2016/08/18 14:20:28 common-utils.go:37: Starting building image...
> 2016/08/18 14:20:57 common-utils.go:45: Successfully built docker image.
> 2016/08/18 14:20:57 common-utils.go:85: No errors were found in docker
> build logs
> 2016/08/18 14:20:57 common-utils.go:58: Running image...
> 2016/08/18 14:20:59 common-utils.go:66: Successfully ran docker image.
> 2016/08/18 14:20:59 common-utils.go:98: No errors were found in docker run
> logs
> 2016/08/18 14:20:59 common-utils.go:130: Attempt: 1. Port 9763 is not open
> in the docker container.
> 2016/08/18 14:20:59 common-utils.go:133: Sleeping for 2 seconds
> 2016/08/18 14:21:01 common-utils.go:130: Attempt: 2. Port 9763 is not open
> in the docker container.
> 2016/08/18 14:21:01 common-utils.go:133: Sleeping for 4 seconds
> 2016/08/18 14:21:05 common-utils.go:130: Attempt: 3. Port 9763 is not open
> in the docker container.
> 2016/08/18 14:21:05 common-utils.go:133: Sleeping for 6 seconds
> 2016/08/18 14:21:11 common-utils.go:130: Attempt: 4. Port 9763 is not open
> in the docker container.
> 2016/08/18 14:21:11 common-utils.go:133: Sleeping for 8 seconds
> 2016/08/18 14:21:19 common-utils.go:136: Port 9763 is open in the docker
> container.
> 2016/08/18 14:21:19 common-utils.go:136: Port 9443 is open in the docker
> container.
> 2016/08/18 14:21:20 common-utils.go:153: Carbon server is up and running.
> 2016/08/18 14:21:20 common-utils.go:166: Checking Carbon server logs for
> any errors
> 2016/08/18 14:21:20 docker-utils.go:105: Successfully copied carbon server
> logs from docker container
> 2016/08/18 14:21:20 common-utils.go:173: Errors founds in carbon server
> logs, please check them under wso2bps3.5.1logs
> 2016/08/18 14:21:20 main.go:146: Test completed for wso2bps, 3.5.1.
> 2016/08/18 14:21:20 main.go:158: Starting test clean up
> 2016/08/18 14:21:20 docker-utils.go:61: Stopping and removing docker
> container with id: 6f28d71772e6
> 2016/08/18 14:21:31 docker-utils.go:67: Successfully stopped and removed
> docker container
> 2016/08/18 14:21:31 docker-utils.go:43: Removing docker image wso2bps:3.5.1
> 2016/08/18 14:21:31 docker-utils.go:47: Successfully removed docker image
> 2016/08/18 14:21:31 main.go:161: Completed test clean up
>
> [2].
> TID: [-1234] [] [2016-08-18 08:51:15,701]  INFO
> {org.springframework.beans.factory.support.DefaultListableBeanFactory} -
>  Pre-instantiating singletons in org.springframework.beans.
> factory.support.DefaultListableBeanFactory@38d281d4: defining beans
> [cxf,org.apache.cxf.bus.spring.BusWiringBeanFactoryPostProces
> sor,org.apache.cxf.bus.spring.Jsr250BeanPostProcessor,org.
> apache.cxf.bus.spring.BusExtensionPostProcessor,deploymentService,
> runtimeService,queryRuntimeService,historyService,formService,
> processDefinitionService,identityService,managementService,statsService,
> authenticationBean,exceptionHandlerBean,errorHandlerBean,jacksonBean];
> root of factory hierarchy {org.springframework.beans.factory.support.
> DefaultListableBeanFactory}
>
> [3]. https://github.com/abhishek0198/test-framework/
> blob/master/common/common-utils.go#L169
>
> Thanks.
>
>
> On Fri, Aug 12, 2016 at 3:04 PM, Abhishek Tiwari <
> abhishek.tiwari0...@gmail.com> wrote:
>
>> Here is the correct link:
>>
>> https://hangouts.google.com/call/krqijl3e4fc4xa4bpd2vct3quqe
>>
>> On Fri, Aug 12, 2016 at 2:03 AM, Abhishek Tiwari <
>> abhishek.tiwari0...@gmail.com> wrote:
>>
>>> The meeting got rescheduled to 3:00pm. Here is the updated hangout link:
>>>
>>> https://hangouts.google.com/call/g5q25layaremzfhyli6vbqsv2ye
>>>
>>> Thanks
>>> Abhishek
>>>
>>> On Thu, Aug 11, 2016 at 10:37 PM, Abhishek Tiwari <
>>> abhishek.tiwari0...@gmail.com> wrote:
>>>
 Hi Imesh,

 Yeah 2:30pm IST is perfect.

 Thanks

[Dev] Clarification about Entity Expansion Limit

[Bhathiya Jayasekara]

Hi ESB team,

In "JVM Level Tuning" doc[1] in ESB, it says

"If one or more worker nodes in a clustered deployment require access to
the management console, you need to increase the entity expansion limit."

Could you please explain the rational behind this. I think we need to
explain it in the doc too.

[1]
https://docs.wso2.com/display/ESB490/Java+Virtual+Machine+(JVM)+Level+Tuning

Thanks,

-- 
*Bhathiya Jayasekara*
*Senior Software Engineer,*
*WSO2 inc., http://wso2.com *

*Phone: +94715478185*
*LinkedIn: http://www.linkedin.com/in/bhathiyaj
*
*Twitter: https://twitter.com/bhathiyax *
*Blog: http://movingaheadblog.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Extensive amount of warning logs are printed once the IS520-Analytics server starts up.

[Tanya Madurapperuma]

On Thu, Aug 18, 2016 at 9:18 PM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:

>
>
> On Thu, Aug 18, 2016 at 3:55 PM, Tanya Madurapperuma 
> wrote:
>
>> This warning is coming from shindig which is the underlying library that
>> we used for gadget rendering and is a 3rd party library. Quick solution for
>> this is to increase maxDepth value as mentioned in [1] by Mohan.
>> If not we will have to analyze EhCache memory for memory consuming
>> objects [2] [3]
>>
>> [1] https://wso2.org/jira/browse/ANLYIS-48
>> [2] https://cwiki.apache.org/confluence/display/SHINDIG/Debuggin
>> g+EhCache's+SizeOfEngine
>> [3] https://cwiki.apache.org/confluence/display/SHINDIG/EhCache+
>> Memory+Analysis
>>
>
> @Tanya, Thanks for the response.. I think, increasing the maxDepth value
> is not helpful all the time.. Whether you guys, explored about this more ?
>
AFAIK it depends on the rendered gadgets in the dashboard. Hence need to be
explored on the particular dashboard itself.

> Since it is observed in various products/cases. If this log does not
> reflect any useful info then can, we disable that at log4j level ?
>
@ Sinthuja and team : WDYT? Shall we invest sometime on this?

Thanks,
Tanya

>
> Thanks,
> Mohan
>
>
>>
>> Thanks,
>> Tanya
>>
>> On Thu, Aug 18, 2016 at 3:40 PM, Mohanadarshan Vivekanandalingam <
>> mo...@wso2.com> wrote:
>>
>>> [Moving to DEV]
>>>
>>> Related UES/DS jira is [1]..
>>>
>>> @Sewmini, above logs are only printed once for a user (When loading a
>>> gadget for first time - once for each gadget)..
>>>
>>> [1] https://wso2.org/jira/browse/UES-658
>>>
>>>
>>> Thanks,
>>> Mohan
>>>
>>>
>>> On Thu, Aug 18, 2016 at 3:34 PM, Sewmini Jayaweera 
>>> wrote:
>>>
 Hi DS team,

 I observed the same issue reported in [1] in the latest Analytics pack
 given. I reopened the issue since repeatedly printed warning may mislead
 user thinking it's a critical issue eve,n though it is harmless and it
 doesn't give a good impression to the user.

 It would be great if we can get this fixed. If it is difficult to fix
 it in this release can we change it to an improvement and fix it later
 without having it as won't fix?

 [1]. https://wso2.org/jira/browse/ANLYIS-48

 Thank you in advance.
 Kind regards,

 Sewmini Jayaweera
 *Software Engineer - QA Team*
 Mobile: +94 (0) 773 381 250
 sewm...@wso2.com

>>>
>>>
>>>
>>> --
>>> *V. Mohanadarshan*
>>> *Associate Tech Lead,*
>>> *Data Technologies Team,*
>>> *WSO2, Inc. http://wso2.com  *
>>> *lean.enterprise.middleware.*
>>>
>>> email: mo...@wso2.com
>>> phone:(+94) 771117673
>>>
>>
>>
>>
>> --
>> Tanya Madurapperuma
>>
>> Senior Software Engineer,
>> WSO2 Inc. : wso2.com
>> Mobile : +94718184439
>> Blog : http://tanyamadurapperuma.blogspot.com
>>
>
>
>
> --
> *V. Mohanadarshan*
> *Associate Tech Lead,*
> *Data Technologies Team,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: mo...@wso2.com
> phone:(+94) 771117673
>



-- 
Tanya Madurapperuma

Senior Software Engineer,
WSO2 Inc. : wso2.com
Mobile : +94718184439
Blog : http://tanyamadurapperuma.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] rdbms table data view

[Aneela Safdar]

I have created an rdbms table in an execution plan and write below query
@from(eventtable = 'rdbms' , datasource.name = 'WSO2_CARBON_DB' , table.name 
='ftp_log_table')
define table ftp_log_table (ts string, uid string, id_orig_h string, id_orig_p 
int, id_resp_h string, id_resp_p int, user string, password string,command 
string, arg string, mime_type string, file_size string, reply_code int, 
reply_msg string);

from FTPInStream
select *
insert into ftp_log_table; There is no error of invalidity but I haven't 
created this table before in the database. Also how can I view data in it? Is 
it going to store data permanently or a long period of time for further 
correspondence?

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

Re: [Dev] Extensive amount of warning logs are printed once the IS520-Analytics server starts up.

[Mohanadarshan Vivekanandalingam]

On Thu, Aug 18, 2016 at 3:55 PM, Tanya Madurapperuma  wrote:

> This warning is coming from shindig which is the underlying library that
> we used for gadget rendering and is a 3rd party library. Quick solution for
> this is to increase maxDepth value as mentioned in [1] by Mohan.
> If not we will have to analyze EhCache memory for memory consuming objects
> [2] [3]
>
> [1] https://wso2.org/jira/browse/ANLYIS-48
> [2] https://cwiki.apache.org/confluence/display/SHINDIG/
> Debugging+EhCache's+SizeOfEngine
> [3] https://cwiki.apache.org/confluence/display/SHINDIG/
> EhCache+Memory+Analysis
>

@Tanya, Thanks for the response.. I think, increasing the maxDepth value is
not helpful all the time.. Whether you guys, explored about this more ?
Since it is observed in various products/cases. If this log does not
reflect any useful info then can, we disable that at log4j level ?

Thanks,
Mohan


>
> Thanks,
> Tanya
>
> On Thu, Aug 18, 2016 at 3:40 PM, Mohanadarshan Vivekanandalingam <
> mo...@wso2.com> wrote:
>
>> [Moving to DEV]
>>
>> Related UES/DS jira is [1]..
>>
>> @Sewmini, above logs are only printed once for a user (When loading a
>> gadget for first time - once for each gadget)..
>>
>> [1] https://wso2.org/jira/browse/UES-658
>>
>>
>> Thanks,
>> Mohan
>>
>>
>> On Thu, Aug 18, 2016 at 3:34 PM, Sewmini Jayaweera 
>> wrote:
>>
>>> Hi DS team,
>>>
>>> I observed the same issue reported in [1] in the latest Analytics pack
>>> given. I reopened the issue since repeatedly printed warning may mislead
>>> user thinking it's a critical issue eve,n though it is harmless and it
>>> doesn't give a good impression to the user.
>>>
>>> It would be great if we can get this fixed. If it is difficult to fix it
>>> in this release can we change it to an improvement and fix it later without
>>> having it as won't fix?
>>>
>>> [1]. https://wso2.org/jira/browse/ANLYIS-48
>>>
>>> Thank you in advance.
>>> Kind regards,
>>>
>>> Sewmini Jayaweera
>>> *Software Engineer - QA Team*
>>> Mobile: +94 (0) 773 381 250
>>> sewm...@wso2.com
>>>
>>
>>
>>
>> --
>> *V. Mohanadarshan*
>> *Associate Tech Lead,*
>> *Data Technologies Team,*
>> *WSO2, Inc. http://wso2.com  *
>> *lean.enterprise.middleware.*
>>
>> email: mo...@wso2.com
>> phone:(+94) 771117673
>>
>
>
>
> --
> Tanya Madurapperuma
>
> Senior Software Engineer,
> WSO2 Inc. : wso2.com
> Mobile : +94718184439
> Blog : http://tanyamadurapperuma.blogspot.com
>



-- 
*V. Mohanadarshan*
*Associate Tech Lead,*
*Data Technologies Team,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: mo...@wso2.com
phone:(+94) 771117673
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Preserving URL parameters across different pages in a dashboard

[Fathima Dilhasha]

Hi Kalpa,

I know it's not a good practice, but what about storing the start and end
time in session variables?

Thanks.
Dilhasha

On Thu, Aug 18, 2016 at 5:34 PM, Kalpa Welivitigoda  wrote:

> Hi dev,
>
> I am working on http analytics dashboard, there we have a date time picker
> gadget. Once a date time range is selected, the gadget publishes those
> information to a topic so that other gadgets in the same page can update
> accordingly.
>
> I have several pages, I am trying to preserve the date time selection from
> one page to another.
>
> The approach I am trying is to update the url parameters (start_time and
> end_time) when a date time selection is made. I am using
> *window.parent.history.**pushState* for this purpose. This works fine.
> But when I navigate to another page, these URL parameters are lost. If I
> set the URL parameters and reload the page, they are preserved in the other
> pages as well. I am looking for a way to accomplish this without reloading
> the page.
>
> Have we come across a similar requirement before?
>
>
> --
> Best Regards,
>
> Kalpa Welivitigoda
> Senior Software Engineer, WSO2 Inc. http://wso2.com
> Email: kal...@wso2.com
> Mobile: +94776509215
>
> [image: http://wso2.com/signature] 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Fathima Dilhasha
*Software Engineer*
Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
<%2B94%20%280%29%20773%20451194>
dilha...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Imesh,

Yes now I understand that creating VM images for each product profile will
not going to work out.

Can you please give me a step by step guideline on what I should do to
achieve this?
.
 Thank you,

On Wed, Aug 17, 2016 at 10:41 PM, Imesh Gunaratne  wrote:

>
>
> On Wed, Aug 17, 2016 at 10:19 PM, Imesh Gunaratne  wrote:
>>
>>
>> ​There are many spelling mistakes on this file [2], please review it
>> again.
>>
>
> ​Correction: s/on this file/in this file/g
>
> Thanks
> ​
>
>
>> Overall I see very less attention to detail in this repository and the
>> membership scheme implementation.
>>
>>
>>> There I mentioned the things that should be kept in mind while
>>> configuring wso2 AS and did not go in to detail on hot to configure as it
>>> can be found in the wso2 documentation. Would that be okay?
>>>
>>
>> ​I don't think this is helpful. Without having detailed steps users might
>> not be able to do a complete deployment.
>>
>> Few questions:
>>
>>- How do you create a distributed deployment​
>>
>>​of AS ​or any other product (say for an example WSO2 API-M) with
>>this approach? As I explained earlier creating a VM image per product
>>profile is an unnecessary overhead (time consumption, disk space needed,
>>maintenance, etc).
>>
>>- ​What would be the approach of applying​
>> a patch or do
>>​ing​
>>a configuration change in a such deployment?
>>
>> ​IMO it is really important to understand the concepts well and solve
>> problems with the most efficient manner. Otherwise the outcome of this
>> project might not be usable.
>>
>> [2] https://github.com/osuran/azure-artifacts/issues/2
>>
>> Thanks
>>
>>
>>> user do not need to change anything in template.json, so should I
>>> explain the parameters in that too?
>>>
>>> in the paramters.json, except for the vm_image parameter, all of the
>>> parameters are just for the naming of the elements that you find in a VM,
>>> for an example, the name of the network interface. Therefore I have given
>>> instructions on how to set the vm_image parameter.
>>>
>>> current progress: The script which was generated by Azure does not have
>>> the capability to add a custom VM image. I modified it so that now it has
>>> that capability. Normally when you login to azure from CLI, it needs web
>>> interaction to authenticate. I modified deploy.sh in a way that it
>>> authenticates the user without web interaction, this will be useful if we
>>> run deploy.sh in a minimal version of linux.
>>>
>>> currently I'm working on adding deployment patterns to deploy.sh and
>>> undeploy.sh
>>>
>>>
>>> [1] https://github.com/osuran/azure-artifacts/tree/master/wso2as
>>>
>>> thank you,
>>>
>>> On Tue, Aug 16, 2016 at 10:10 AM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 Can you please send an update on the current status?

 On Mon, Aug 15, 2016 at 10:11 AM, Isuru Haththotuwa 
 wrote:

> Hi Osura,
>
> Few comments regarding the README:
>
>1. Need to mention how to configure the VM with the product pack
>and JDK for Azure
>2. There are lot of parameters in the template and parameters json
>files; please explain what a user needs to change there.
>3. The deploy script should be able to handle both standalone and
>distributed deployment pattern for the product. Refer to K8s 
> repository as
>a reference [1]
>4. Highlights the commands that a user needs to issue clearly
>
> Please note a user should be able to deploy a WSO2 product in Azure by
> following the README. If we provide abstract and incomplete instructions,
> user experience will not be good.
>
> On Mon, Aug 15, 2016 at 9:05 AM, Osura Rathnayake 
> wrote:
>
>> Hi Imesh  /Isuru,
>>
>> Please accept my apologies for the delayed response.
>>
>> There is a MySQL instance in the Azure marketplace, we can
>> straightaway deploy that. It's a Ubuntu 16.04.1 LTS with MySQL 
>> installed. I
>> think it's better to use it as there won't be licensing issues with it.
>>
>> Please find the updated readme file in [1] which includes steps on
>> how to deploy WSO2 AS in Azure.
>>
>
>> About the undeploy.sh, should it remove the VM entirely or just the
>> WSO2 AS instance?
>>
> Ideally we should be able to re-use the VM, so IMHO removing only the
> instance is ok.
>
> [1]. https://github.com/wso2/kubernetes-artifacts/tree/master/wso2as
>
>>
>> [1] https://github.com/osuran/azure-artifacts
>>
>> Thank you,
>>
>> On Sun, Aug 14, 2016 at 10:06 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> I see that you have updated the repo [1] with a deploy script for
>>> wso2as. Additionally we would need an undeploy script as well. What 

Re: [Dev] [Announce] [Architecture] WSO2 Dashboard Server 2.1.0-Alpha Released!

[Nisala Nanayakkara]

Hi,

I have implemented maven - plugins for each artifacts in WSO2 Dashboard
Server. So there are four maven - plugins for dashboards,gadgets,layouts
and themes which can be used to generate a CAR file consisting with these
artifacts. But we are not very much clear about where we have to maintain
these maven - plugins. Is it better to keep it within our carbon-dashboards
repository ? Or is it better to maintain these as a separate repository.

@DevStudioTeam : Can you provide recommended way of maintaining these
maven-plugins ?

Thanks,
Nisala

On Mon, Aug 15, 2016 at 10:51 AM, Susinda Perera  wrote:

> Do we have tooling support for this new release, like create/edit/deploy
> gadgets/dashboards etc. If not shall we add this to roadmap. DevS team will
> be able to help on this task.
>
> Thanks
> Susinda
>
> On Fri, Aug 12, 2016 at 8:23 PM, Megala Uthayakumar 
> wrote:
>
>> WSO2 Dashboard Server 2.1.0-Alpha Released!
>>
>> WSO2 Dashboard Server team is pleased to announce the release of WSO2
>> Dashboard Server 2.1.0 Alpha. This release comes with the following bug
>> fixes, improvements and tasks. You can download the distribution from [1]
>> and view the documentation at [2].
>> Bug
>>
>>- [UES-990 ] - All the query
>>params get appended to the url when navigating via hierarchical menu
>>- [UES-1016 ] - Tenant ID is
>>always super tenant ID in Gadget Generation Wizard
>>- [UES-1018 ] - DS Console
>>differs from the WSO2 theme
>>- [UES-1022 ] - Product
>>version in footer is incorrect
>>- [UES-1023 ] - Create view
>>menu rendered incorrectly
>>- [UES-1028 ] - Creating
>>gadgets in third-party store - Thumbnail image does not show
>>
>> Improvement
>>
>>- [UES-970 ] - Add download
>>functionality to gadgets listed
>>- [UES-995 ] - Having a landing
>>page for a dashboard is optional
>>- [UES-1003 ] - Modify the ES
>>extension to not allow the assets to be editable in published asset
>>- [UES-1010 ] - Add shindig
>>features to get the hostName,port and tenant domain
>>- [UES-1012 ] - Store the
>>theme level properties to dashboard.json and retrieve these theme
>>properties while rendering the page
>>- [UES-1014 ] - Add new
>>gadget/layout button at the end of the gadget listing and layout listings
>>when user designs dashboard
>>- [UES-1015 ] - Dashboard page
>>loading icon for embeddable gadget feature
>>
>> Task
>>
>>- [UES-1005 ] - Provide common
>>repository for js libraries to use in gadgets
>>- [UES-1006 ] - Dashboard page
>>loading icon to show after all gadgets are loaded
>>- [UES-1007 ] - Fixed the
>>issue in PDF download feature in firefox browser
>>- [UES-1008 ] - Fixing issues
>>in running the dashboard server with samples
>>- [UES-1029 ] - Create Puppet
>>script for Dashboard Server Auto Deployment
>>
>> Reporting Issues
>>
>> Issues can be reported through the Public JIRA
>>  project for WSO2 Dashboard Server.
>>
>>
>> [1]- https://github.com/wso2/product-ds/releases/download/v2
>> .1.0-alpha/wso2ds-2.1.0-SNAPSHOT.zip
>>
>> [2]- https://docs.wso2.com/display/DS210/WSO2+Dashboard+Serv
>> er+Documentation
>>
>>
>> Thanks,
>>
>> Dashboard Server Team.
>>
>> --
>> Megala Uthayakumar
>>
>> Software Engineer
>> Mobile : 0779967122
>>
>> ___
>> Announce mailing list
>> annou...@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/announce
>>
>>
>
>
> --
> *Susinda Perera*
> Software Engineer
> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
> Mobile:(+94)716049075
> Blog: susinda.blogspot.com
> WSO2 Inc. http://wso2.com/
> Tel : 94 11 214 5345 Fax :94 11 2145300
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DAS 310] ML Siddhi Extension doc update

[Mohanadarshan Vivekanandalingam]

>
>>> I can see in the doc[1] for the ML siddhi extension, we need to install
>>> the features (ML Siddhi extension ...etc). This was true for previous
>>> releases.
>>>
>>> But I can see these features are already installed in the latest DAS
>>> pack.
>>>
>>> If that's so, we need to update the docs accordingly.
>>>
>>> Can someone please confirm this?
>>>
>>> [1] https://docs.wso2.com/display/ML111/WSO2+CEP+Extension+for+M
>>> L+Predictions
>>>
>>
Yes, correct for DAS.. But,we are not shipping above extension with WSO2
CEP then we need to correct above document appropriately and mention that
DAS does not required these.. BTW, below [1] is the latest documentation
for above..

[1] https://docs.wso2.com/display/CEP420/Installing+Machine+Learner+Features

Thanks,
Mohan


>
>>>
>>> Thanks,
>>> Sachith
>>> --
>>> Sachith Withana
>>> Software Engineer; WSO2 Inc.; http://wso2.com
>>> E-mail: sachith AT wso2.com
>>> M: +94715518127
>>> Linked-In: https://lk.linkedin.com/in/sac
>>> hithwithana
>>>
>>
>>
>>
>> --
>> Rukshani Weerasinha
>>
>> WSO2 Inc.
>> Web:http://wso2.com
>> Mobile: 0777 683 738
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> W.G. Gihan Anuruddha
> Senior Software Engineer | WSO2, Inc.
> M: +94772272595
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*V. Mohanadarshan*
*Associate Tech Lead,*
*Data Technologies Team,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: mo...@wso2.com
phone:(+94) 771117673
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AppM] SAML response signature validation in tenants

[Amila Maha Arachchi]

Hi Rushmin,

Please see my answer inline.

On Thu, Aug 18, 2016 at 4:43 PM, Rushmin Fernando  wrote:

>
> In current App Manager the service providers of tenants are getting
> created in the super tenant space.
>
> We are in the process of creating the service providers in the relevant
> tenants.
>
> In the app manager gateway, we use SAML SSO to authenticate the users, and
> the aforementioned service providers are used.
>
> When it comes to validating the the SAML response signature, I can see
> that we can re-use
> *org.wso2.carbon.identity.sso.saml.util.SAMLSSOUtil::getX509CredentialImplForTenant()*
>
> As per the code, it uses the tenant key store to get the certificates. And
> we can get the certificate by using the tenant name as the alias
>
> @IS team, do you see any issues with re-using this code in our gateway ?
>
> @Amila, in a cloud story do we need to configure the key aliases for each
> tenant or can we live with the default alias (which is the tenant domain
> name) ?
>

Default alias is fine. Since the tenant keystores are only used for
intetnal purposes similar to this one, there wont be scenarios where
tenants changing this.

>
>
>
> --
> *Best Regards*
>
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc.  - Lean . Enterprise . Middleware
>
> mobile : +94772891266
>
>
>


-- 
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com

Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB5.0.0-RC4 | Intermittent Exception in the Cluster Environment

[Chandana Napagoda]

Hi Chaminda/Chanaka,

This thread death has occurred from the "system_status_ajaxprocessor" JSP
file and this is not related to the registry.

Regards,
Chandana

On Thu, Aug 18, 2016 at 5:26 PM, Chaminda Jayawardena 
wrote:

> Hi All,
>
> Noticed below exception[2] in the logs of the mgt node of an ESB5.0.0-RC4
> cluster environment. And also this has occurred several times in that node.
>
> Though line numbers are different, found a similar kind of issue is
> reported here [1], but we didn't access the registry from mgt console, in
> this matter.
>
> [1] https://wso2.org/jira/browse/REGISTRY-3046
>
> [2]
> TID: [-1234] [] [2016-08-18 09:03:54,506] ERROR 
> {org.apache.axis2.rpc.receivers.RPCMessageReceiver}
> -  Exception occurred while trying to invoke service method getServerData
> {org.apache.axis2.rpc.receivers.RPCMessageReceiver}
> java.lang.reflect.InvocationTargetException
> at sun.reflect.GeneratedMethodAccessor201.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.
> java:212)
> at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(
> RPCMessageReceiver.java:117)
> at org.apache.axis2.receivers.AbstractInOutMessageReceiver.
> invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
> at org.apache.axis2.receivers.AbstractMessageReceiver.receive(
> AbstractMessageReceiver.java:110)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> at org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(
> LocalTransportReceiver.java:169)
> at org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(
> LocalTransportReceiver.java:82)
> at org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.
> finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
> at org.apache.axis2.transport.local.LocalTransportSender.
> invoke(LocalTransportSender.java:77)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
> at org.apache.axis2.description.OutInAxisOperationClient.send(
> OutInAxisOperation.java:430)
> at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(
> OutInAxisOperation.java:225)
> at org.apache.axis2.client.OperationClient.execute(
> OperationClient.java:149)
> at org.wso2.carbon.server.admin.stub.ServerAdminStub.
> getServerData(ServerAdminStub.java:1621)
> at org.wso2.carbon.server.admin.ui.ServerAdminClient.getServerData(
> ServerAdminClient.java:131)
> at org.apache.jsp.server_002dadmin.system_005fstatus_
> 005fajaxprocessor_jsp._jspService(system_005fstatus_
> 005fajaxprocessor_jsp.java:165)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> at org.apache.jasper.servlet.JspServletWrapper.service(
> JspServletWrapper.java:439)
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(
> JspServlet.java:395)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
> at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(
> ContextPathServletAdaptor.java:37)
> at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(
> ServletRegistration.java:61)
> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.
> processAlias(ProxyServlet.java:128)
> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.
> service(ProxyServlet.java:68)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.
> service(DelegationServlet.java:68)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
> ApplicationFilterChain.java:303)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:208)
> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
> ApplicationFilterChain.java:241)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:208)
> at org.owasp.csrfguard.CsrfGuardFilter.doFilter(CsrfGuardFilter.java:88)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
> ApplicationFilterChain.java:241)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:208)
> at org.wso2.carbon.ui.filters.CSRFPreventionFilter.doFilter(
> CSRFPreventionFilter.java:88)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
> ApplicationFilterChain.java:241)
> at 

[Dev] Preserving URL parameters across different pages in a dashboard

[Kalpa Welivitigoda]

Hi dev,

I am working on http analytics dashboard, there we have a date time picker
gadget. Once a date time range is selected, the gadget publishes those
information to a topic so that other gadgets in the same page can update
accordingly.

I have several pages, I am trying to preserve the date time selection from
one page to another.

The approach I am trying is to update the url parameters (start_time and
end_time) when a date time selection is made. I am using
*window.parent.history.**pushState* for this purpose. This works fine. But
when I navigate to another page, these URL parameters are lost. If I set
the URL parameters and reload the page, they are preserved in the other
pages as well. I am looking for a way to accomplish this without reloading
the page.

Have we come across a similar requirement before?


-- 
Best Regards,

Kalpa Welivitigoda
Senior Software Engineer, WSO2 Inc. http://wso2.com
Email: kal...@wso2.com
Mobile: +94776509215

[image: http://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DAS 310] ML Siddhi Extension doc update

[Gihan Anuruddha]

Yes. We have added ML Siddhi extension to the DAS 3.1.0.

On Thu, Aug 18, 2016 at 8:04 AM, Rukshani Weerasinha 
wrote:

> Hi Sachith,
>
> Thank you for mentioning this. I will check with someone in the team to
> confirm, and update accordingly.
>
> Best Regards,
> Rukshani.
>
> On Wed, Aug 17, 2016 at 12:23 AM, Sachith Withana 
> wrote:
>
>> Hi all,
>>
>> I can see in the doc[1] for the ML siddhi extension, we need to install
>> the features (ML Siddhi extension ...etc). This was true for previous
>> releases.
>>
>> But I can see these features are already installed in the latest DAS
>> pack.
>>
>> If that's so, we need to update the docs accordingly.
>>
>> Can someone please confirm this?
>>
>> [1] https://docs.wso2.com/display/ML111/WSO2+CEP+Extension+for+M
>> L+Predictions
>>
>> Thanks,
>> Sachith
>> --
>> Sachith Withana
>> Software Engineer; WSO2 Inc.; http://wso2.com
>> E-mail: sachith AT wso2.com
>> M: +94715518127
>> Linked-In: https://lk.linkedin.com/in/sac
>> hithwithana
>>
>
>
>
> --
> Rukshani Weerasinha
>
> WSO2 Inc.
> Web:http://wso2.com
> Mobile: 0777 683 738
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
W.G. Gihan Anuruddha
Senior Software Engineer | WSO2, Inc.
M: +94772272595
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] ESB5.0.0-RC4 | Intermittent Exception in the Cluster Environment

[Chaminda Jayawardena]

Hi All,

Noticed below exception[2] in the logs of the mgt node of an ESB5.0.0-RC4
cluster environment. And also this has occurred several times in that node.

Though line numbers are different, found a similar kind of issue is
reported here [1], but we didn't access the registry from mgt console, in
this matter.

[1] https://wso2.org/jira/browse/REGISTRY-3046

[2]
TID: [-1234] [] [2016-08-18 09:03:54,506] ERROR
{org.apache.axis2.rpc.receivers.RPCMessageReceiver} -  Exception occurred
while trying to invoke service method getServerData
{org.apache.axis2.rpc.receivers.RPCMessageReceiver}
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor201.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
at
org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
at
org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at
org.wso2.carbon.server.admin.stub.ServerAdminStub.getServerData(ServerAdminStub.java:1621)
at
org.wso2.carbon.server.admin.ui.ServerAdminClient.getServerData(ServerAdminClient.java:131)
at
org.apache.jsp.server_002dadmin.system_005fstatus_005fajaxprocessor_jsp._jspService(system_005fstatus_005fajaxprocessor_jsp.java:165)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:439)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at
org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.owasp.csrfguard.CsrfGuardFilter.doFilter(CsrfGuardFilter.java:88)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.wso2.carbon.ui.filters.CSRFPreventionFilter.doFilter(CSRFPreventionFilter.java:88)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.wso2.carbon.ui.filters.CRLFPreventionFilter.doFilter(CRLFPreventionFilter.java:59)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at

Re: [Dev] [VOTE] Release WSO2 Enterprise Service Bus 5.0.0 RC4

[Chanaka Fernando]

Tested the following functionalities.

*ESB runtime*

   - Clustering
   - Deployment Synchronization
   - Tenant use cases
   - Statistics/Tracing data publishing
   - Inbound Coordination
   - Message processor coordination
   - Registry mounting
   - CAR file deployment through management console

*ESB Analytics*

   - Statistics/Tracing in super tenant mode for Proxy, Sequence, API,
   Inbound, Endpoint
   - Statistics/Tracing for above artifacts in tenant mode

*ESB Tooling*

   - Artifact creation (Proxy, Inbound, Sequence, Endpoint, Message Store,
   Message Processor)
   - Artifact deployment from the Tool
   - Artifact export and deploy through management console

No issues found.

[+] - Stable - Go ahead and release

On Wed, Aug 17, 2016 at 8:13 AM, Senduran Balasubramaniyam <
sendu...@wso2.com> wrote:

> Hi All,
>
> This is the 4th Release Candidate of WSO2 Enterprise Service Bus 5.0.0
>
> Please download, test the product and vote. Vote will be open for 72 hours
> or as needed.
>
> Source and distribution
>
> Run-time: https://github.com/wso2/product-esb/releases/tag/v5.0.0-rc4
> Tooling   : https://github.com/wso2/devstudio-tooling-esb/
> releases/tag/v5.0.0-rc4
> Analytics: https://github.com/wso2/analytics-esb/releases/tag/v5.
> 0.0-rc4
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Thanks,
> - WSO2 ESB Team -
>
> --
> *Senduran *
> Senior Software Engineer,
> WSO2, Inc.;  http://wso2.com/ 
> Mobile: +94 77 952 6548
>



-- 
Thank you and Best Regards,
Chanaka Fernando
Senior Technical Lead
m: +94 773337238
https://wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [AppM] SAML response signature validation in tenants

[Rushmin Fernando]

In current App Manager the service providers of tenants are getting created
in the super tenant space.

We are in the process of creating the service providers in the relevant
tenants.

In the app manager gateway, we use SAML SSO to authenticate the users, and
the aforementioned service providers are used.

When it comes to validating the the SAML response signature, I can see that
we can re-use
*org.wso2.carbon.identity.sso.saml.util.SAMLSSOUtil::getX509CredentialImplForTenant()*

As per the code, it uses the tenant key store to get the certificates. And
we can get the certificate by using the tenant name as the alias

@IS team, do you see any issues with re-using this code in our gateway ?

@Amila, in a cloud story do we need to configure the key aliases for each
tenant or can we live with the default alias (which is the tenant domain
name) ?



-- 
*Best Regards*

*Rushmin Fernando*
*Technical Lead*

WSO2 Inc.  - Lean . Enterprise . Middleware

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

Re: [Dev] Extensive amount of warning logs are printed once the IS520-Analytics server starts up.

[Tanya Madurapperuma]

This warning is coming from shindig which is the underlying library that we
used for gadget rendering and is a 3rd party library. Quick solution for
this is to increase maxDepth value as mentioned in [1] by Mohan.
If not we will have to analyze EhCache memory for memory consuming objects
[2] [3]

[1] https://wso2.org/jira/browse/ANLYIS-48
[2]
https://cwiki.apache.org/confluence/display/SHINDIG/Debugging+EhCache's+SizeOfEngine
[3]
https://cwiki.apache.org/confluence/display/SHINDIG/EhCache+Memory+Analysis

Thanks,
Tanya

On Thu, Aug 18, 2016 at 3:40 PM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:

> [Moving to DEV]
>
> Related UES/DS jira is [1]..
>
> @Sewmini, above logs are only printed once for a user (When loading a
> gadget for first time - once for each gadget)..
>
> [1] https://wso2.org/jira/browse/UES-658
>
>
> Thanks,
> Mohan
>
>
> On Thu, Aug 18, 2016 at 3:34 PM, Sewmini Jayaweera 
> wrote:
>
>> Hi DS team,
>>
>> I observed the same issue reported in [1] in the latest Analytics pack
>> given. I reopened the issue since repeatedly printed warning may mislead
>> user thinking it's a critical issue eve,n though it is harmless and it
>> doesn't give a good impression to the user.
>>
>> It would be great if we can get this fixed. If it is difficult to fix it
>> in this release can we change it to an improvement and fix it later without
>> having it as won't fix?
>>
>> [1]. https://wso2.org/jira/browse/ANLYIS-48
>>
>> Thank you in advance.
>> Kind regards,
>>
>> Sewmini Jayaweera
>> *Software Engineer - QA Team*
>> Mobile: +94 (0) 773 381 250
>> sewm...@wso2.com
>>
>
>
>
> --
> *V. Mohanadarshan*
> *Associate Tech Lead,*
> *Data Technologies Team,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: mo...@wso2.com
> phone:(+94) 771117673
>



-- 
Tanya Madurapperuma

Senior Software Engineer,
WSO2 Inc. : wso2.com
Mobile : +94718184439
Blog : http://tanyamadurapperuma.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Extensive amount of warning logs are printed once the IS520-Analytics server starts up.

[Mohanadarshan Vivekanandalingam]

[Moving to DEV]

Related UES/DS jira is [1]..

@Sewmini, above logs are only printed once for a user (When loading a
gadget for first time - once for each gadget)..

[1] https://wso2.org/jira/browse/UES-658


Thanks,
Mohan


On Thu, Aug 18, 2016 at 3:34 PM, Sewmini Jayaweera  wrote:

> Hi DS team,
>
> I observed the same issue reported in [1] in the latest Analytics pack
> given. I reopened the issue since repeatedly printed warning may mislead
> user thinking it's a critical issue eve,n though it is harmless and it
> doesn't give a good impression to the user.
>
> It would be great if we can get this fixed. If it is difficult to fix it
> in this release can we change it to an improvement and fix it later without
> having it as won't fix?
>
> [1]. https://wso2.org/jira/browse/ANLYIS-48
>
> Thank you in advance.
> Kind regards,
>
> Sewmini Jayaweera
> *Software Engineer - QA Team*
> Mobile: +94 (0) 773 381 250
> sewm...@wso2.com
>



-- 
*V. Mohanadarshan*
*Associate Tech Lead,*
*Data Technologies Team,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: mo...@wso2.com
phone:(+94) 771117673
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Dockerfiles] Added ability to run smoke tests from test framework

[Thanuja Uruththirakodeeswaran]

Hi Abhishek,

Great work on Dockerfiles test framework!!! I have used the test framework
to check the flow of building and running WSO2 BPS 3.5.1 docker image.
According to the framework log[1], the test fails because of an error in
the carbon server log. But when I check the carbon server log, there were
no *ERROR* logs and it has 'error' as part of a word in line[2].

For this scenario, we should not make the test to be failed. I think
instead of simply grepping the 'error' word as in[3], we should grep the
*ERROR* logs.

[1].
2016/08/18 14:20:28 main.go:151: Starting test setup up
2016/08/18 14:20:28 main.go:154: Completed test setup up
2016/08/18 14:20:28 main.go:106: Running tests for wso2bps, 3.5.1, using
puppet provisioning, under default platform.
2016/08/18 14:20:28 common-utils.go:37: Starting building image...
2016/08/18 14:20:57 common-utils.go:45: Successfully built docker image.
2016/08/18 14:20:57 common-utils.go:85: No errors were found in docker
build logs
2016/08/18 14:20:57 common-utils.go:58: Running image...
2016/08/18 14:20:59 common-utils.go:66: Successfully ran docker image.
2016/08/18 14:20:59 common-utils.go:98: No errors were found in docker run
logs
2016/08/18 14:20:59 common-utils.go:130: Attempt: 1. Port 9763 is not open
in the docker container.
2016/08/18 14:20:59 common-utils.go:133: Sleeping for 2 seconds
2016/08/18 14:21:01 common-utils.go:130: Attempt: 2. Port 9763 is not open
in the docker container.
2016/08/18 14:21:01 common-utils.go:133: Sleeping for 4 seconds
2016/08/18 14:21:05 common-utils.go:130: Attempt: 3. Port 9763 is not open
in the docker container.
2016/08/18 14:21:05 common-utils.go:133: Sleeping for 6 seconds
2016/08/18 14:21:11 common-utils.go:130: Attempt: 4. Port 9763 is not open
in the docker container.
2016/08/18 14:21:11 common-utils.go:133: Sleeping for 8 seconds
2016/08/18 14:21:19 common-utils.go:136: Port 9763 is open in the docker
container.
2016/08/18 14:21:19 common-utils.go:136: Port 9443 is open in the docker
container.
2016/08/18 14:21:20 common-utils.go:153: Carbon server is up and running.
2016/08/18 14:21:20 common-utils.go:166: Checking Carbon server logs for
any errors
2016/08/18 14:21:20 docker-utils.go:105: Successfully copied carbon server
logs from docker container
2016/08/18 14:21:20 common-utils.go:173: Errors founds in carbon server
logs, please check them under wso2bps3.5.1logs
2016/08/18 14:21:20 main.go:146: Test completed for wso2bps, 3.5.1.
2016/08/18 14:21:20 main.go:158: Starting test clean up
2016/08/18 14:21:20 docker-utils.go:61: Stopping and removing docker
container with id: 6f28d71772e6
2016/08/18 14:21:31 docker-utils.go:67: Successfully stopped and removed
docker container
2016/08/18 14:21:31 docker-utils.go:43: Removing docker image wso2bps:3.5.1
2016/08/18 14:21:31 docker-utils.go:47: Successfully removed docker image
2016/08/18 14:21:31 main.go:161: Completed test clean up

[2].
TID: [-1234] [] [2016-08-18 08:51:15,701]  INFO
{org.springframework.beans.factory.support.DefaultListableBeanFactory} -
 Pre-instantiating singletons in
org.springframework.beans.factory.support.DefaultListableBeanFactory@38d281d4:
defining beans
[cxf,org.apache.cxf.bus.spring.BusWiringBeanFactoryPostProcessor,org.apache.cxf.bus.spring.Jsr250BeanPostProcessor,org.apache.cxf.bus.spring.BusExtensionPostProcessor,deploymentService,runtimeService,queryRuntimeService,historyService,formService,processDefinitionService,identityService,managementService,statsService,authenticationBean,exceptionHandlerBean,
errorHandlerBean,jacksonBean]; root of factory hierarchy
{org.springframework.beans.factory.support.DefaultListableBeanFactory}

[3].
https://github.com/abhishek0198/test-framework/blob/master/common/common-utils.go#L169

Thanks.


On Fri, Aug 12, 2016 at 3:04 PM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:

> Here is the correct link:
>
> https://hangouts.google.com/call/krqijl3e4fc4xa4bpd2vct3quqe
>
> On Fri, Aug 12, 2016 at 2:03 AM, Abhishek Tiwari <
> abhishek.tiwari0...@gmail.com> wrote:
>
>> The meeting got rescheduled to 3:00pm. Here is the updated hangout link:
>>
>> https://hangouts.google.com/call/g5q25layaremzfhyli6vbqsv2ye
>>
>> Thanks
>> Abhishek
>>
>> On Thu, Aug 11, 2016 at 10:37 PM, Abhishek Tiwari <
>> abhishek.tiwari0...@gmail.com> wrote:
>>
>>> Hi Imesh,
>>>
>>> Yeah 2:30pm IST is perfect.
>>>
>>> Thanks
>>> Abhishek
>>>
>>> On Thu, Aug 11, 2016 at 9:59 PM, Imesh Gunaratne  wrote:
>>>


 On Fri, Aug 12, 2016 at 10:08 AM, Abhishek Tiwari <
 abhishek.tiwari0...@gmail.com> wrote:

> Hi Mentors,
>
> Just a quick reminder for the Dockerfiles test framework demo today
> afternoon?
>

 ​Would 2:30 PM IST work for you?

 Thanks​

>
> Thanks
> Abhishek
>
> On Tue, Aug 9, 2016 at 11:00 PM, Abhishek Tiwari <
> abhishek.tiwari0...@gmail.com> wrote:
>
>> HI Vishanth,
>>
>> Friday afternoon works fine with 

[Dev] Cookie based authorization to PEP proxy

[Lahiru Cooray]

Hi IS team,

Regarding [1] which AppM requires to get implemented (IS feature) prior to
cloud integration.

I'm planning to implement $subject and I would like to share few
concerns/feedbacks with you.

When looking at the PEPProxyFactory class we find few clients (eg: soap,
json, trift, ws xacml, basic auth). So I plan to introduce Cookie base
authorization initially only to the soap client which is the most common
use case. (AFAIK this is not a valid use case for clients like thrift/basic
auth)

This will allow users to authenticate using both credentials and authorized
cookie.
So when the cookie is available it will authenticate using the cookie and
if not it will validate the credentials.

WDYT?




[1] https://wso2.org/jira/browse/IDENTITY-4987

-- 
*Lahiru Cooray*
Software Engineer
WSO2, Inc.;http://wso2.com/
lean.enterprise.middleware

Mobile: +94 715 654154
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2-DSS - AMQP Consumer

[Madhawa Gunasekara]

Hi Reza,

Since RabbitMq has JMS support, you can directly use DSS JMS Transport [1]
to achieve this.

[1] https://docs.wso2.com/display/DSS350/JMS+Transport

Thanks,
Madhawa

On Wed, Aug 17, 2016 at 10:51 PM, Reza Ameri  wrote:

> Hi all,
>
> I am using RabbitMq as my message queue and I have to use AMQP protocol in
> my application. I am publishing messages to my queues in RabbitMq and
> consume the messages using nodejs client. As an enhancement I want to omit
> the nodejs consumer client and replace it with WSO2 Data Service Server,
> since currently the nodejs client calls the services hosted on wso2-dss,
> after fetching them from queue.
>
> I searched a lot and I didn't find proper way to do this without using
> wso2-esb. I may be able to solve my problem with qpid client, but I really
> need help.
>
> It would be better if you answer my question on Stackoverflow[1]
>  so others can reach it too.
>
>
> [1]: http://stackoverflow.com/q/38958756/1635051
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Madhawa Gunasekara*
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] Test Case fail due to Null Point Exception from Rampart

[Susinda Perera]

Hi Vanji

Do you remember the resolution for this issue.

Thanks
Susinda

On Sat, Jun 28, 2014 at 10:39 PM, Vanjikumaran Sivajothy 
wrote:

> Hi,
> we notice several test cases failing in due to null point exception thrown
> by rampart fro ESB security policy scenario.
>
> Reproduce method.
> ===
> 1) Start SecureStockquateService
> 2) Start Deploy the given synapse config and the policy.
> 3) Send a message to ESB ant stockquote -Dtrpurl=http://localhost:8280/
>
> Observation
> Request is not send to backend and error thrown at ESB [1].
>
> What could be the reason? Was there any change in rampart or Security
> component?
>
> While i am debuging the Rampart noticed in BindingBuilder class. *Result*
> is null. therefore in for loop when size checked. It is throwing the null
> point exception.
>
>
> protected void addSignatureConfirmation(RampartMessageData rmd, Vector
> sigParts) {
>
> if (!rmd.getPolicyData().isSignatureConfirmation()) {
>
> // If we don't require sig confirmation simply go back :-)
> return;
> }
>
> Document doc = rmd.getDocument();
>
>* Vector results = (Vector)
> rmd.getMsgContext().getProperty(WSHandlerConstants.RECV_RESULTS);*
> /*
>  * loop over all results gathered by all handlers in the chain.
> For each handler result get
>  * the various actions. After that loop we have all signature
> results in the
>  * signatureActions vector
>  */
> Vector signatureActions = new Vector();
> for (int i = 0; i < *results.size()*; i++) {
> WSHandlerResult wshResult = (WSHandlerResult) results.get(i);
>
>
> [1]
> ERROR {org.apache.synapse.core.axis2.Axis2Sender} -  Unexpected error
> during sending message out {org.apache.synapse.core.axis2.Axis2Sender}
> java.lang.NullPointerException
> at org.apache.rampart.builder.BindingBuilder.addSignatureConfirmation(
> BindingBuilder.java:807)
> at org.apache.rampart.builder.AsymmetricBindingBuilder.doSignBe
> foreEncrypt(AsymmetricBindingBuilder.java:433)
> at org.apache.rampart.builder.AsymmetricBindingBuilder.build(As
> ymmetricBindingBuilder.java:97)
> at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:147)
> at org.apache.rampart.handler.RampartSender.invoke(RampartSende
> r.java:65)
> 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.send(AxisEngine.java:426)
> at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOp
> erationClient.send(DynamicAxisOperation.java:185)
> at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOp
> erationClient.executeImpl(DynamicAxisOperation.java:167)
> at org.apache.axis2.client.OperationClient.execute(OperationCli
> ent.java:149)
> at org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Ax
> is2FlexibleMEPClient.java:496)
> at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender
> .java:59)
> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(A
> xis2SynapseEnvironment.java:338)
> at org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractE
> ndpoint.java:333)
> at org.apache.synapse.endpoints.AddressEndpoint.send(AddressEnd
> point.java:59)
> at org.apache.synapse.mediators.builtin.SendMediator.mediate(Se
> ndMediator.java:97)
> at org.apache.synapse.mediators.AbstractListMediator.mediate(Ab
> stractListMediator.java:77)
> at org.apache.synapse.mediators.AbstractListMediator.mediate(Ab
> stractListMediator.java:47)
> at org.apache.synapse.mediators.base.SequenceMediator.mediate(S
> equenceMediator.java:131)
> at org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(
> ProxyServiceMessageReceiver.java:166)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> at org.apache.synapse.transport.passthru.ServerWorker.processEn
> tityEnclosingRequest(ServerWorker.java:411)
> at org.apache.synapse.transport.passthru.ServerWorker.run(Serve
> rWorker.java:183)
> at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.
> run(NativeWorkerPool.java:172)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
> ThreadPoolExecutor.java:895)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
> lExecutor.java:918)
> at java.lang.Thread.run(Thread.java:662)
> --
> Sivajothy Vanjikumaran
> *Senior Software Engineer*
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com *
> *Mobile:(+94)777219209*
> [image: Facebook]  [image: Twitter]
>  [image: LinkedIn]
>  [image:
> Blogger]  [image: SlideShare]
> 

Re: [Dev] Why some of the features aren't shown in the Available Feature UI

[Abimaran Kugathasan]

Thanks for the input, Yes the feature was hidden from UI.

On Tue, Aug 16, 2016 at 6:21 PM, Niranjan Karunanandham 
wrote:

> Hi Abimaran,
>
> As mentioned by Aruna and KasunG, this is based on the value defined in
> the feature pom under adviceFile. In the Feature Management UI when the
> "Group by" is unticked, features which have "org.eclipse.
> equinox.p2.type.group:false" within "adviceFile" in the
> pom.xml are not displayed. This is used when defining the features by the
> corresponding. Here there can be minor features and all these features can
> be packed into feature F1 which the team (who created the features) wants
> other to use. Therefore using this property Definition, the team can hide
> these features from the UI.
>
> Regards,
> Nira
>
> On Tue, Aug 16, 2016 at 5:45 PM, Aruna Karunarathna 
> wrote:
>
>>
>>
>> On Tue, Aug 16, 2016 at 5:35 PM, Abimaran Kugathasan 
>> wrote:
>>
>>> Hi Dev,
>>>
>>> When I tried to install features on latest Identity Server 5.2.0
>>> SNAPHOT, I could observe that, the features listed under a category are not
>>> shown in the list of feature when I don't select either of below checkbox.
>>>Show only the latest versions
>>>Group features by category
>>>
>>> For example, there is a feature called  "Api management Key Manager"
>>> version 5.0.3 and it's listed under API Key Manager/API Key Manager 5.0.3.
>>> But, if you use Find Feature without selecting above two check boxes, You
>>> won't see this feature anyware in the list.
>>>
>>> Why is that? This happens only for some features.
>>>
>> AFAIR check the adviceFile of the relevant feature.
>>
>>>
>>> --
>>> Thanks
>>> Abimaran Kugathasan
>>> Senior Software Engineer - API Technologies
>>>
>>> Email : abima...@wso2.com
>>> Mobile : +94 773922820
>>>
>>> 
>>> 
>>>   
>>> 
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> -
>>
>
>
>
> --
>
>
> *Niranjan Karunanandham*
> Associate Technical Lead - WSO2 Inc.
> WSO2 Inc.: http://www.wso2.com
>
>


-- 
Thanks
Abimaran Kugathasan
Senior Software Engineer - API Technologies

Email : abima...@wso2.com
Mobile : +94 773922820


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

Re: [Dev] GSoC2016-Contact Development Team Feature

[Nathiesha Maddage]

Hi,

I have completed almost all of the coding part now, and working with fixing
a few left errors and tidying the code.

I plan to submit the plugin project, feature project and the documentation
as the deliverable.
For the final submission, I need to upload a URL that contains our project.
For that Google has provided certain examples such as the link of Git Hub
commits, a web page or a blog post, public folder in Google Drive etc. [1]

What would be the best way of submission, for our project?

[1]. https://developers.google.com/open-source/gsoc/help/work-product


Thanks and regards

Nathiesha

On Thu, Aug 11, 2016 at 4:40 PM, Kavith Lokuhewage  wrote:

> Hi Nathiesha,
>
> Great! We can have the meeting at 3.00pm to 4.00pm tomorrow. I will send
> the invitation. Meanwhile, please push the latest changes to github before
> the meeting.
>
> Thanks,
>
> *Kavith Lokuhewage*
> Senior Software Engineer
> WSO2 Inc. - http://wso2.com
> lean . enterprise . middleware
> Mobile - +94779145123
> Linkedin 
> Twitter 
>
> On Thu, Aug 11, 2016 at 4:35 PM, Nathiesha Maddage <
> nathieshamadd...@gmail.com> wrote:
>
>> Hi Kavith,
>>
>> I externalized the credentials in micro-service code and implemented the
>> extension point. I plan to start on OSGI services part once I finalize the
>> remaining small tasks in these sections.
>>
>> How about tomorrow evening for the next meeting? I have lectures in the
>> morning. So it would be easy if we can arrange the meeting after 2 pm.
>>
>> Thanks and regards
>> Nathiesha
>>
>> On Thu, Aug 11, 2016 at 11:42 AM, Kavith Lokuhewage 
>> wrote:
>>
>>> Hi Nathiesha,
>>>
>>> How is the progress on remaining tasks? As per the previous update, you
>>> are already done with configuring maven build + creating a basic
>>> micro-service for publishing reports, aren't you?
>>>
>>> The remaining work was to externalize hard coded credentials in
>>> micro-service code, implement the extension point for providing different
>>> JIRA keys to report errors for specific java packages and define an OSGI
>>> service to be able to contribute publishers via other eclipse plugins - if
>>> needed in future.
>>>
>>> It would be great if we can finalize these soon as we are reaching
>>> towards the end of GSOC program. Please suggest a time for a meeting
>>> tomorrow. We can discuss about the issues you are facing - if any - and
>>> discuss the plat to wrap the rest of the work by end of next week.
>>>
>>> Thanks,
>>>
>>> *Kavith Lokuhewage*
>>> Senior Software Engineer
>>> WSO2 Inc. - http://wso2.com
>>> lean . enterprise . middleware
>>> Mobile - +94779145123
>>> Linkedin 
>>> Twitter 
>>>
>>> On Fri, Aug 5, 2016 at 2:06 PM, Kavith Lokuhewage 
>>> wrote:
>>>
 Hi Nathiesha,

 Please join the hangout https://hangouts.googl
 e.com/hangouts/_/wso2.com/kavith

 Thanks,

 *Kavith Lokuhewage*
 Senior Software Engineer
 WSO2 Inc. - http://wso2.com
 lean . enterprise . middleware
 Mobile - +94779145123
 Linkedin 
 Twitter 

 On Fri, Aug 5, 2016 at 11:49 AM, Kavith Lokuhewage 
 wrote:

> Hi Nathiesha,
>
> Great! I have sent you the invitation.
>
> Thanks,
>
> *Kavith Lokuhewage*
> Senior Software Engineer
> WSO2 Inc. - http://wso2.com
> lean . enterprise . middleware
> Mobile - +94779145123
> Linkedin 
> Twitter 
>
> -- Forwarded message --
> From: Nathiesha Maddage 
> Date: Fri, Aug 5, 2016 at 9:36 AM
> Subject: Re: [Dev] GSoC2016-Contact Development Team Feature
> To: Kavith Lokuhewage 
>
>
> Hi Kavith,
>
> That time is OK with me.
>
> Thanks
> Nathiesha
>
>
> On Fri, Aug 5, 2016 at 8:01 AM, Kavith Lokuhewage 
> wrote:
>
>> Hi Nathiesha,
>>
>> Shall we have the meeting at 2pm – 3pm today? Please let us know
>> your availability.
>> Thanks,
>>
>> *Kavith Lokuhewage*
>> Senior Software Engineer
>> WSO2 Inc. - http://wso2.com
>> lean . enterprise . middleware
>> Mobile - +94779145123
>> Linkedin 
>> Twitter 
>>
>> On Thu, Aug 4, 2016 at 12:21 PM, Nathiesha Maddage <
>> nathieshamadd...@gmail.com> wrote:
>>
>>> Hi Kavith,
>>>
>>> I started with creating a micro service. Thank you for the
>>> reference.
>>> If you can please show 

Re: [Dev] [GSoC Final Evaluation] Proposal 21: [IS] Document Based NoSQL Support for WSO2 Identity Server Database

[Tharindu Edirisinghe]

Hi Asntha,

Please follow steps below to complete the project.

1. In your features [1] folder, you have to create etc folder and put
feature.properties file in it. This is same as [2].
2. You have to create server.feature in [1]. Refer [3] and do the same.
Make necessary modifications to pom file.
3. Once you do above, you can commit and push so that your PR [4] will
automatically get these changes appended.

Next step is to add this feature to IS product so when the product is
built, the jar file is automatically packed to the product. For that,
follow the instructions below.

4. Clone product-is [5] and do a clean repo build skipping tests. (you can
just backup .m2 directory in your home and create an empty folder with name
.m2. Then you can run mvn clean install -Dmaven.test.skip=true" command in
product-is.
5. Once the product is built, you can get the zip file in
modules/distribution folder. Run the product and check if you can access
management console.
6. Next step is to build your feature so local m2 repository get the jar
files of your feature.
7. Then, you can fork product-is and modify parent pom [6] adding a new
property for your feature's version. Similar to below property, you can add
your own one.

5.1.1

8.  Modify the p2-profile-get pom file [7] and include your feature there.
You can search for "*user.store.remote.feature*" and following that, add
details for your feature.
9. Then re-build the product-is, get the zip file, run it and in Management
Console, check if mongodb userstore is listed. Also you can check if the
jar file is packed in plugins.
10. Finally send a PR to product-is with these changes.


[1]
https://github.com/asanthamax/identity-userstore-mongodb/tree/master/features
[2]
https://github.com/wso2-extensions/identity-userstore-remote/blob/master/features/etc/feature.properties
[3]
https://github.com/wso2-extensions/identity-userstore-remote/tree/master/features/org.wso2.carbon.identity.user.store.remote.server.feature
[4] https://github.com/wso2-extensions/identity-userstore-mongodb/pull/1
[5] https://github.com/wso2/product-is/
[6] https://github.com/wso2/product-is/blob/master/pom.xml
[7]
https://github.com/wso2/product-is/blob/master/modules/p2-profile-gen/pom.xml

Thanks,
TharinduE

On Tue, Aug 16, 2016 at 1:13 PM, Asantha Thilina 
wrote:

> Hi Tharindu,
>
> According to your instructions i have added the components folder with the
> mongodbuserstore package to my forked repo[1] and i also sent the pull
> request to origin also[2] i have refactor the main package to 
> *org.wso2.carbon.identity.user.store.mo
> **ngodb *
> expecting your feedback
> [1] https://github.com/asanthamax/identity-userstore-mongodb
> [2] https://github.com/wso2-extensions/identity-userstore-mongodb/pull/1
> Thanks,
> Asantha
>
> On Tue, Aug 16, 2016 at 2:45 AM, Tharindu Edirisinghe 
> wrote:
>
>> Hi Asantha,
>>
>> Now that you have completed the project [1], for the final evaluation,
>> you need to contribute your code to WSO2 codebase.
>>
>> For that, we have created the repository [2].
>>
>> You can refer [3] to get some idea about the package structure of the
>> repo.
>>
>> Further, you can refactor your project and rename the main package to 
>> *org.wso2.carbon.identity.user.store.mo
>> **ngodb*.
>>
>> You can send a pull request with these.
>>
>> I will help you with writing the feature and creating the parent pom file
>> later.
>>
>>
>> [1] https://docs.wso2.com/display/GSoC/Project+Proposals+for+201
>> 6#ProjectProposalsfor2016-Proposal21:[IS]DocumentBasedNoSQLS
>> upportforWSO2IdentityServerDatabase
>> [2] https://github.com/wso2-extensions/identity-userstore-mongodb
>> [3] https://github.com/wso2-extensions/identity-userstore-remote
>>
>> Thank you,
>> TharinduE
>> --
>>
>> Tharindu Edirisinghe
>> Senior Software Engineer | WSO2 Inc
>> Platform Security Team
>> Blog : tharindue.blogspot.com
>> mobile : +94 775181586
>>
>
>


-- 

Tharindu Edirisinghe
Senior Software Engineer | WSO2 Inc
Platform Security Team
Blog : tharindue.blogspot.com
mobile : +94 775181586
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev