[Dev] OSGI imports are not getting resolved

[Hasintha Indrajee]

Hi All,

I am building a new orbit bundle for opensaml [1], The reason for building
this is to make some of the imports optional (javax.servlet.jsp and
org.apache.axiom.om.impl.dom.jaxp).

With this OSGI bundle I am getting issues while starting up the server. The
issue is while resolving [org.apache.commons.ssl] import. But this is being
exported in my osgi environment by [commons-httpclient_3.1.0.wso2v3]. The
issues is that this is not being picked up by opensaml (Even though we
import correct version ranges).

Another thing I have observed is "org.apache.commons.httpclient" which is
also being exported from the above httpclient bundle is also imported by
opensaml bundle without any issue. This import is working as expected.

Currently above imports are as optional. I made them compulsory bus still
the issue is there since it cannot find the "org.apache.commons.ssl"
package within opensaml.

I have uploaded a distribution where I can observe this issue to the svn
location [2].


[1]
https://github.com/hasinthaindrajee/orbit/blob/opensaml_and_encorder/opensaml/2.6.4.wso2v4/pom.xml
[2]
https://svn.wso2.org/repos/wso2/people/hasintha/opensaml_issue/wso2is-6.0.0-SNAPSHOT.zip
-- 
Hasintha Indrajee
WSO2, Inc.
Mobile:+94 771892453
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Releasing puppet-base 1.0.0 and puppet-common 1.0.0

[Pubudu Gunatilaka]

Hi Raj,

We haven't considered this aspect. In the latest puppet modules we have
introduced two ways of applying patches.

1. You can just copy patches into the patches folder and all the patches
inside that folder will be copied.
2. You can define required patches in a patch list. Once this is defined,
it will copy only the mentioned patches.

I think you can use option 2 which is the patch list to define the relevant
patches. But it does not check the checksum of the patch. If you need to
verify the checksum of the patches, you can write a custom function and
call this function to copy patches.

Thank you!

On Tue, Feb 21, 2017 at 11:31 AM, Isuru Haththotuwa  wrote:

> Hi Raj,
>
> On Tue, Feb 21, 2017 at 11:23 AM, Rajkumar Rajaratnam 
> wrote:
>
>> Hi Pubudu,
>>
>> Thanks for the response. My question is bit different. We have a
>> requirement that we want to make sure the official patches released by WSO2
>> should be applied to the nodes. That means, we should be able to specify
>> the the checksum of the official patches in hiera or whatever and verify
>> the checksum of the patches before applying it to the nodes. I think with
>> the current puppet modules, it's not possible to do, as we copy all patches
>> found inside /files folder to the nodes. But if we want to have this
>> feature, then we need to define a resource per patch, I think that's not
>> scalable or maintainable.
>>
> Do we need a resource per patch here? If we have the list of official
> patches and their checksums, we can write a function in the puppet side to
> verify and apply AFAIU?
>
> However, I do believe that applying only official patches for production
> environment is the responsibility of the person/team who is maintaining the
> deployment. And with WUM, we won't have this issue.
>
>>
>> Thanks,
>> Raj.
>>
>> On Tue, Feb 21, 2017 at 12:42 AM, Pubudu Gunatilaka 
>> wrote:
>>
>>> Hi Raj,
>>>
>>> Yes, we do. Basically, when copying files or templates puppet checks the
>>> checksum by default. We haven't done anything specifically to verify
>>> checksum in files in our puppet modules.
>>>
>>> Thank you!
>>>
>>> On Tue, Feb 21, 2017 at 9:58 AM, Rajkumar Rajaratnam >> > wrote:
>>>
 Hi Pubudu,

 Do we support verifying checksum when applying patches, in latest
 puppet modules?

 Thanks,
 Raj.

 On Fri, Feb 17, 2017 at 12:30 AM, Pubudu Gunatilaka 
 wrote:

> Hi Devs,
>
> We are currently doing final testing for releasing puppet-base [1] and
> puppet-common [2] repositories. Once these repos are released, 
> puppet-apim,
> puppet-iot and puppet-is can be released for latest product versions.
> Please let us know if you have any concerns.
>
> [1] - https://github.com/wso2/puppet-base
> [2] - https://github.com/wso2/puppet-common
>
> Thank you!
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Rajkumar Rajaratnam
 Committer & PMC Member, Apache Stratos
 Senior Software Engineer, WSO2

 LinkedIn : https://lk.linkedin.com/in/rajuu
 Mobile : +94777568639 <+94%2077%20756%208639>

>>>
>>>
>>>
>>> --
>>> *Pubudu Gunatilaka*
>>> Committer and PMC Member - Apache Stratos
>>> Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> mobile : +94774078049 <%2B94772207163>
>>>
>>>
>>
>>
>> --
>> Rajkumar Rajaratnam
>> Committer & PMC Member, Apache Stratos
>> Senior Software Engineer, WSO2
>>
>> LinkedIn : https://lk.linkedin.com/in/rajuu
>> Mobile : +94777568639 <077%20756%208639>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048 <+94%2071%20635%208048>* *
>
>
>


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

Re: [Dev] interested in gsoc project Eclipse Plugin for Siddhi

[Tishan Dahanayakage]

Hi Ravindu,

Thank you for your interest in this project. We have provided useful
resources in the idea page. If you need additional context or help
regarding anything specific please ask. As starters I would suggest that
you start implementing an eclipse plugin for a simple antlr based grammar.
Later we can move on to the actual implementation.

Thanks,
/Tishan

On Sat, Feb 18, 2017 at 11:11 PM, Ravindu Perera 
wrote:

> HI
> My name is Ravindu Perera and i am 20 years old and currently 3rd year
> student of Informatics institute of technology of Sri Lanka (IIT), and i am
> confident java programmer who has a 3 year experience in java programming
> and also has done java projects and has a fair knowledge in eclipse plugin
> development .
>
> So i am interested in the Eclipse Plugin for Siddhi , and i would like to
> get more information about this projects and also more information of
> Siddhi . So please give me some help
>
> Thank you
> Ravindu Perera
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Tishan Dahanayakage
Senior Software Engineer
WSO2, Inc.
Mobile:+94 716481328

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

Re: [Dev] Releasing puppet-base 1.0.0 and puppet-common 1.0.0

[Isuru Haththotuwa]

Hi Raj,

On Tue, Feb 21, 2017 at 11:23 AM, Rajkumar Rajaratnam 
wrote:

> Hi Pubudu,
>
> Thanks for the response. My question is bit different. We have a
> requirement that we want to make sure the official patches released by WSO2
> should be applied to the nodes. That means, we should be able to specify
> the the checksum of the official patches in hiera or whatever and verify
> the checksum of the patches before applying it to the nodes. I think with
> the current puppet modules, it's not possible to do, as we copy all patches
> found inside /files folder to the nodes. But if we want to have this
> feature, then we need to define a resource per patch, I think that's not
> scalable or maintainable.
>
Do we need a resource per patch here? If we have the list of official
patches and their checksums, we can write a function in the puppet side to
verify and apply AFAIU?

However, I do believe that applying only official patches for production
environment is the responsibility of the person/team who is maintaining the
deployment. And with WUM, we won't have this issue.

>
> Thanks,
> Raj.
>
> On Tue, Feb 21, 2017 at 12:42 AM, Pubudu Gunatilaka 
> wrote:
>
>> Hi Raj,
>>
>> Yes, we do. Basically, when copying files or templates puppet checks the
>> checksum by default. We haven't done anything specifically to verify
>> checksum in files in our puppet modules.
>>
>> Thank you!
>>
>> On Tue, Feb 21, 2017 at 9:58 AM, Rajkumar Rajaratnam 
>> wrote:
>>
>>> Hi Pubudu,
>>>
>>> Do we support verifying checksum when applying patches, in latest puppet
>>> modules?
>>>
>>> Thanks,
>>> Raj.
>>>
>>> On Fri, Feb 17, 2017 at 12:30 AM, Pubudu Gunatilaka 
>>> wrote:
>>>
 Hi Devs,

 We are currently doing final testing for releasing puppet-base [1] and
 puppet-common [2] repositories. Once these repos are released, puppet-apim,
 puppet-iot and puppet-is can be released for latest product versions.
 Please let us know if you have any concerns.

 [1] - https://github.com/wso2/puppet-base
 [2] - https://github.com/wso2/puppet-common

 Thank you!
 --
 *Pubudu Gunatilaka*
 Committer and PMC Member - Apache Stratos
 Software Engineer
 WSO2, Inc.: http://wso2.com
 mobile : +94774078049 <%2B94772207163>


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


>>>
>>>
>>> --
>>> Rajkumar Rajaratnam
>>> Committer & PMC Member, Apache Stratos
>>> Senior Software Engineer, WSO2
>>>
>>> LinkedIn : https://lk.linkedin.com/in/rajuu
>>> Mobile : +94777568639 <+94%2077%20756%208639>
>>>
>>
>>
>>
>> --
>> *Pubudu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : +94774078049 <%2B94772207163>
>>
>>
>
>
> --
> Rajkumar Rajaratnam
> Committer & PMC Member, Apache Stratos
> Senior Software Engineer, WSO2
>
> LinkedIn : https://lk.linkedin.com/in/rajuu
> Mobile : +94777568639 <077%20756%208639>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Releasing puppet-base 1.0.0 and puppet-common 1.0.0

[Rajkumar Rajaratnam]

Hi Pubudu,

Thanks for the response. My question is bit different. We have a
requirement that we want to make sure the official patches released by WSO2
should be applied to the nodes. That means, we should be able to specify
the the checksum of the official patches in hiera or whatever and verify
the checksum of the patches before applying it to the nodes. I think with
the current puppet modules, it's not possible to do, as we copy all patches
found inside /files folder to the nodes. But if we want to have this
feature, then we need to define a resource per patch, I think that's not
scalable or maintainable.

Thanks,
Raj.

On Tue, Feb 21, 2017 at 12:42 AM, Pubudu Gunatilaka 
wrote:

> Hi Raj,
>
> Yes, we do. Basically, when copying files or templates puppet checks the
> checksum by default. We haven't done anything specifically to verify
> checksum in files in our puppet modules.
>
> Thank you!
>
> On Tue, Feb 21, 2017 at 9:58 AM, Rajkumar Rajaratnam 
> wrote:
>
>> Hi Pubudu,
>>
>> Do we support verifying checksum when applying patches, in latest puppet
>> modules?
>>
>> Thanks,
>> Raj.
>>
>> On Fri, Feb 17, 2017 at 12:30 AM, Pubudu Gunatilaka 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> We are currently doing final testing for releasing puppet-base [1] and
>>> puppet-common [2] repositories. Once these repos are released, puppet-apim,
>>> puppet-iot and puppet-is can be released for latest product versions.
>>> Please let us know if you have any concerns.
>>>
>>> [1] - https://github.com/wso2/puppet-base
>>> [2] - https://github.com/wso2/puppet-common
>>>
>>> Thank you!
>>> --
>>> *Pubudu Gunatilaka*
>>> Committer and PMC Member - Apache Stratos
>>> Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> mobile : +94774078049 <%2B94772207163>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Rajkumar Rajaratnam
>> Committer & PMC Member, Apache Stratos
>> Senior Software Engineer, WSO2
>>
>> LinkedIn : https://lk.linkedin.com/in/rajuu
>> Mobile : +94777568639 <+94%2077%20756%208639>
>>
>
>
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>


-- 
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Senior Software Engineer, WSO2

LinkedIn : https://lk.linkedin.com/in/rajuu
Mobile : +94777568639
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Environments Support for WSO2 API Manager

[Kasun Thennakoon]

Hi Ravindu,

We are glad to see your interest in WSO2 API manager and the GSOC project.
It is good to see that you already have experience on working with WSO2 API
Manager.
As we have mentioned in the project description[1], the expectation of this
project is to develop an UI feature to seamlessly switch between different
environments and perform user operations on that selected environment.To
get started with the work, I would suggest you build the product from
source[2][3] and walk through the current implementation details of the
store and publisher and try to get familiar with those apps.
And also since API manager C5  UIs are built with UUF framework[4] it would
be great if you can try out the samples in UUF core[5] and UUF
commons[6] repositories and learn about the features and capabilities in
UUF framework.

Regards
~KasunTe

[1] : https://docs.wso2.com/display/GSoC/Project+Proposals+for+2017#
ProjectProposalsfor2017-Proposal7:EnvironmentsSupportforWSO2APIManager

[2] : https://github.com/wso2/carbon-apimgt/tree/C5

[3] : https://github.com/wso2/product-apim/tree/C5

[4] : https://github.com/wso2/carbon-uuf

[5] : https://github.com/wso2/carbon-uuf/tree/master/samples

[6] : https://github.com/wso2/carbon-uuf-common/tree/master/samples


On Tue, Feb 21, 2017 at 9:27 AM, Ravindu Perera 
wrote:

> Hi
> I am a 3rd year student from Informatics Institute of technology and i got
> 3 years experience in HTML, CSS, Javascript and knowledge and also
> knowledge in using rest service , and experience on using the WSO2 API
> Manger cloud as well , familiar  handlebars.js . And have a good confident
> level for this project , so can you all please provide more information and
> guidance to start the project off.
>
> Thank you
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Kasun Thennakoon*
Software Engineer
WSO2, Inc.
Mobile:+94 711661919
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Releasing puppet-base 1.0.0 and puppet-common 1.0.0

[Pubudu Gunatilaka]

Hi Raj,

Yes, we do. Basically, when copying files or templates puppet checks the
checksum by default. We haven't done anything specifically to verify
checksum in files in our puppet modules.

Thank you!

On Tue, Feb 21, 2017 at 9:58 AM, Rajkumar Rajaratnam 
wrote:

> Hi Pubudu,
>
> Do we support verifying checksum when applying patches, in latest puppet
> modules?
>
> Thanks,
> Raj.
>
> On Fri, Feb 17, 2017 at 12:30 AM, Pubudu Gunatilaka 
> wrote:
>
>> Hi Devs,
>>
>> We are currently doing final testing for releasing puppet-base [1] and
>> puppet-common [2] repositories. Once these repos are released, puppet-apim,
>> puppet-iot and puppet-is can be released for latest product versions.
>> Please let us know if you have any concerns.
>>
>> [1] - https://github.com/wso2/puppet-base
>> [2] - https://github.com/wso2/puppet-common
>>
>> Thank you!
>> --
>> *Pubudu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : +94774078049 <%2B94772207163>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Rajkumar Rajaratnam
> Committer & PMC Member, Apache Stratos
> Senior Software Engineer, WSO2
>
> LinkedIn : https://lk.linkedin.com/in/rajuu
> Mobile : +94777568639 <+94%2077%20756%208639>
>



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

Re: [Dev] Releasing puppet-base 1.0.0 and puppet-common 1.0.0

[Rajkumar Rajaratnam]

Hi Pubudu,

Do we support verifying checksum when applying patches, in latest puppet
modules?

Thanks,
Raj.

On Fri, Feb 17, 2017 at 12:30 AM, Pubudu Gunatilaka 
wrote:

> Hi Devs,
>
> We are currently doing final testing for releasing puppet-base [1] and
> puppet-common [2] repositories. Once these repos are released, puppet-apim,
> puppet-iot and puppet-is can be released for latest product versions.
> Please let us know if you have any concerns.
>
> [1] - https://github.com/wso2/puppet-base
> [2] - https://github.com/wso2/puppet-common
>
> Thank you!
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Senior Software Engineer, WSO2

LinkedIn : https://lk.linkedin.com/in/rajuu
Mobile : +94777568639
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] GSoC 2017 - Real-Time Machine Learning Toolkit for Siddhi

[Kasun Weerakoon]

Hi Upul,

Thanks you for your reply. I'll go through above mentioned guides and get
back to you later.

Regards,
Kasun Weerakoon.

On Tue, 21 Feb 2017, 08:39 Upul Bandara,  wrote:

Hi Kasun,

We are glad to see your interest!

The main objective of this project is to develop a real-time machine
learning toolkit for Siddhi [1]. Siddhi CEP is a lightweight, easy-to-use
Open Source Complex Event Processing Engine (CEP) released as a Java
Library under Apache Software License v2.0. The readme page of the Siddhi's
Github repository contains a good overview of the Siddhi library. Also,
SiddhiQL Guide [2] will be helpful you to understand Siddhi Query Language.

Most probably, we will be writing this toolkit as a Siddhi extension.
Therefore, please go through Siddhi Extension Guide [3] to get a quick
overview regarding how to write Siddhi extensions.

In addition to that, if you are not familiar with general machine learning
concepts, I think Chapter 12 of the Mining of Massive Datasets book (link
is provided in the GSco project page) will be really helpful. Also, if you
have some free time please look at other streaming machine learning
libraries such as Apache Samoa[4].

Please go through these Siddhi/ML tutorials/guides. They will be helpful
when it comes to writing your project proposal.

Thanks,
Upul

[1]. https://github.com/wso2/siddhi
[2]. https://docs.wso2.com/display/CEP420/SiddhiQL+Guide+3.1
[3] https://docs.wso2.com/display/CEP420/Writing+Extensions+to+Siddhi
[4] https://samoa.incubator.apache.org/

On Mon, Feb 20, 2017 at 7:00 PM, Kasun Weerakoon  wrote:

Hi all,

I'm Kasun Weerakoon, final year undergraduate of University of Moratuwa,
Sri Lanka. I'm interested about above mentioned project idea as I'm
passionate about machine learning and deep learning techniques. I have used
ML in my final year project and have followed the Coursera machine learning
course by Stanford University as well as a ML course module in the
university. I've recently participated to the Deep Learning meetup held in
your organization. I use Java as my major programming language and
currently  I'm following tutorials on Siddhi. I believe I'm a good
candidate for this project and hope your guidance for this project.

Regards,
Kasun Weerakoon.

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




-- 
Upul Bandara,
Mob: +94 715 468 345.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Nullpointer print intermittently when the C5 product start

[Niranjan Karunanandham]

Hi Harsha,

On Mon, Feb 20, 2017 at 11:23 PM, Harsha Thirimanna 
wrote:

> I changed the mvn version, but still i am getting this issue. This is the
> complete log. I am using *Kenral 5.1.0*
>

> JAVA_HOME environment variable is set to /usr/lib/jvm/jdk1.8.0_102
> CARBON_HOME environment variable is set to /home/product-is/product/
> target/wso2is-6.0.0-SNAPSHOT
> Listening for transport dt_socket at address: 5005
> [2017-02-20 23:18:57,183]  INFO 
> {org.wso2.carbon.launcher.extensions.DropinsBundleDeployerUtils
> updateDropins} - Successfully updated the OSGi bundle information of Carbon
> Profile: default
> osgi> [2017-02-20 23:19:10,338]  INFO {org.wso2.carbon.metrics.core.
> config.model.JmxReporterConfig} - Creating JMX reporter for Metrics with
> domain 'org.wso2.carbon.metrics'
> [2017-02-20 23:19:10,356]  INFO {org.wso2.carbon.metrics.core.
> reporter.impl.AbstractReporter} - Started JMX reporter for Metrics
> [2017-02-20 23:19:10,371]  INFO 
> {org.wso2.msf4j.analytics.metrics.MetricsComponent}
> - Metrics Component is activated
> [2017-02-20 23:19:10,424]  WARN {org.wso2.carbon.kernel.
> internal.startupresolver.StartupComponentManager} - Adding a
> RequiredCapabilityListener from bundle(org.wso2.carbon.security.caas:1.0.0),
> but specified startup component is not available, component-name: wso2-caas
> [2017-02-20 23:19:10,513]  INFO 
> {org.wso2.msf4j.internal.MicroservicesRegistryImpl}
> - Added microservice: org.wso2.msf4j.swagger.SwaggerDefinitionService@
> 35c12c7a
> [2017-02-20 23:19:10,527]  INFO 
> {org.wso2.msf4j.internal.MicroservicesRegistryImpl}
> - Added microservice: org.wso2.carbon.identity.gateway.resource.
> GatewayResource@1e58512c
> [2017-02-20 23:19:10,576]  INFO {com.zaxxer.hikari.HikariDataSource} -
> HikariPool-0 - is starting.
> [2017-02-20 23:19:10,897]  INFO {org.wso2.carbon.uuf.internal.UUFServer}
> - RenderableCreator 
> 'org.wso2.carbon.uuf.renderablecreator.hbs.internal.HbsRenderableCreator'
> registered for [hbs] extensions.
> [2017-02-20 23:19:10,910]  INFO {org.wso2.carbon.uuf.internal.UUFServer}
> - RenderableCreator 
> 'org.wso2.carbon.uuf.renderablecreator.html.internal.HtmlRenderableCreator'
> registered for [html] extensions.
> [2017-02-20 23:19:11,437]  INFO {com.zaxxer.hikari.HikariDataSource} -
> HikariPool-1 - is starting.
> [2017-02-20 23:19:13,906]  INFO {org.wso2.carbon.identity.mgt.
> store.connector.jdbc.internal.ConnectorComponent} - JDBC user store
> bundle successfully activated.
> [2017-02-20 23:19:13,993]  INFO {org.wso2.carbon.metrics.jdbc.
> core.config.model.JdbcReporterConfig} - Creating JDBC reporter for
> Metrics with source 'carbon-kernel', data source 
> 'java:comp/env/jdbc/WSO2MetricsDB'
> and 60 seconds polling period
> [2017-02-20 23:19:14,020]  INFO {org.wso2.carbon.metrics.core.
> reporter.impl.AbstractReporter} - Started JDBC reporter for Metrics
> [2017-02-20 23:19:14,368]  WARN {org.wso2.carbon.kernel.
> internal.startupresolver.StartupComponentManager} - You are trying to add
> an available capability org.wso2.carbon.deployment.engine.Deployer from
> bundle(org.wso2.carbon.identity.gateway:1.0.0.SNAPSHOT) to an already
> activated startup listener component carbon-deployment-service in
> bundle(org.wso2.carbon.deployment.engine:5.0.0). Refer the Startup Order
> Resolver documentation and validated your configuration
> [2017-02-20 23:19:14,379]  WARN {org.wso2.carbon.kernel.
> internal.startupresolver.StartupComponentManager} - You are trying to add
> an available capability org.wso2.carbon.deployment.engine.Deployer from
> bundle(org.wso2.carbon.identity.gateway:1.0.0.SNAPSHOT) to an already
> activated startup listener component carbon-deployment-service in
> bundle(org.wso2.carbon.deployment.engine:5.0.0). Refer the Startup Order
> Resolver documentation and validated your configuration
> [2017-02-20 23:19:14,556]  INFO {org.wso2.carbon.identity.mgt.
> impl.internal.IdentityMgtComponent} - Realm service registered
> successfully.
> [2017-02-20 23:19:14,556]  INFO {org.wso2.carbon.identity.mgt.
> impl.internal.IdentityMgtComponent} - Carbon-Identity-Mgt bundle
> activated successfully.
> [2017-02-20 23:19:14,632]  INFO {org.wso2.carbon.uuf.internal.UUFServer}
> - 'org.wso2.carbon.uuf.internal.UUFServer' registered as a Server.
> [2017-02-20 23:19:14,633]  INFO {org.wso2.carbon.transport.
> http.netty.internal.NettyTransportServiceComponent} - All
> CarbonNettyServerInitializers are available
> [2017-02-20 23:19:14,691]  INFO 
> {org.wso2.msf4j.internal.MicroservicesRegistryImpl}
> - Added microservice: org.wso2.carbon.uuf.httpconnector.msf4j.
> UUFMicroservice@302c4471
> [2017-02-20 23:19:14,692]  INFO {org.wso2.carbon.uuf.
> httpconnector.msf4j.internal.MSF4JHttpConnector} - UUF app
> 'org.wso2.carbon.iam.user-portal' is available at '/user-portal'.
> [2017-02-20 23:19:14,692]  INFO 
> {org.wso2.msf4j.internal.MicroservicesServerSC}
> - All microservices are available
> [2017-02-20 23:19:14,693]  INFO 

[Dev] Environments Support for WSO2 API Manager

[Ravindu Perera]

Hi
I am a 3rd year student from Informatics Institute of technology and i got
3 years experience in HTML, CSS, Javascript and knowledge and also
knowledge in using rest service , and experience on using the WSO2 API
Manger cloud as well , familiar  handlebars.js . And have a good confident
level for this project , so can you all please provide more information and
guidance to start the project off.

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

[Dev] WSO2 Governance Registry 5.4.0 Released !!

[Chandana Napagoda]

WSO2 Governance Registry team is pleased to announce the release of WSO2
Governance Registry 5.4.0.!!

WSO2 Governance Registry provides end-to-end governance for enterprises. IT
professionals can streamline application development, testing and
deployment processes, as well as manage service lifecycles and assets using
WSO2 Governance Registry. The community and social aspects of WSO2
Governance Registry will act as an enabler for collaboration between
distributed teams, converting traditional human-centric tasks into key
assets of the governance process. It also includes business runtime
governance requirements through its interoperability with well-known
external monitoring and reporting applications.

For more information on WSO2 Governance Registry and to download the
product please visit http://wso2.com/products/governance-registry. Also,
take a look at the online product documentation

and quick start guide
.

*How to Run*

1. Extract the downloaded zip

2. Go to the bin directory in the extracted folder
3. Run the wso2server.sh or wso2server.bat as appropriate
4. Launch a web browser and navigate to https://localhost:9443/carbon to
access the admin console
5. Navigate to https://localhost:9443/publisher to access the publisher
webapp
6. Navigate to https://localhost:9443/store to access the store webapp
7. Use "admin", "admin" as the username and password to login as an
admin

WSO2 Governance Registry 5.4.0 includes following new features,
improvements and bug fixes.

Improvement

   - [REGISTRY-3107 ] - View
   "SEE MORE" option in search result page, if there are more results to show
   only
   - [REGISTRY-3904 ] - Include
   version in breadcrumb
   - [REGISTRY-3906 ] -
   Introduce an API delete executor for APIM integration.
   - [REGISTRY-3914 ] -
   Incorporate lifecycle Vote into a publisher.

Bug

   - [REGISTRY-3868 ] -
   [Publisher] OR and AND search is not working in landing page.
   - [REGISTRY-3869 ] -
   Publisher Association API doesn't return assets when search query params
   are not passed
   - [REGISTRY-3870 ] - WSDL
   doesn't show associated schemas in store UI
   - [REGISTRY-3871 ] - Ability
   to show/hide certain dependency types in dependency/impact analysis graph
   - [REGISTRY-3877 ] - The
   issuer is hard coded in store publisher in acs.jag's
   - [REGISTRY-3880 ] -
   Throwing solr exception in when we log into publisher with a role that has
   a special character
   - [REGISTRY-3883 ] -
   Customizing the storage path for endpoints artifacts an error occurs when a
   SOAP Service is created manually
   - [REGISTRY-3889 ] -
   Governance REST API doesn't return LC actions
   - [REGISTRY-3894 ] -
   Resource Not Found error is thrown for tenant anon users.
   - [REGISTRY-3909 ] -
   endpoints activate and deactivate apis should be PUT not POST in Gov REST
   API
   - [REGISTRY-3910 ] - Can not
   add a new RXT in the latest greg build
   - [REGISTRY-3913 ] - When
   updating custom artifact, it loss associated connections
   - [REGISTRY-3916 ] - WSDL
   Visualization doesn't work
   - [REGISTRY-3917 ] - Store
   User Registration is not working
   - [REGISTRY-3918 ] - UI
   alert are displaying with HTML content.
   - [REGISTRY-3920 ] - can not
   update the custom artifact name




*Key Features of WSO2 Governance Registry*Registry & Repository for Anything

   - Store any type of data or metadata as resources including contracts,
   models, workflows, WSDLs, Word documents, server configurations and more
   - Revisions, versions with checkpointing and rollback for any resource
   or resource collections
   - Full-text search, metadata search, tagging
   - Register externally stored resources including via Microsoft Sharepoint
   - Define behaviors that trigger automatically based on resource type
   - Out of the box versioning support for WSDL, WADL and XSD
   - Out of the box support 

Re: [Dev] [DEV] GSoC 2017 - Real-Time Machine Learning Toolkit for Siddhi

[Upul Bandara]

Hi Kasun,

We are glad to see your interest!

The main objective of this project is to develop a real-time machine
learning toolkit for Siddhi [1]. Siddhi CEP is a lightweight, easy-to-use
Open Source Complex Event Processing Engine (CEP) released as a Java
Library under Apache Software License v2.0. The readme page of the Siddhi's
Github repository contains a good overview of the Siddhi library. Also,
SiddhiQL Guide [2] will be helpful you to understand Siddhi Query Language.

Most probably, we will be writing this toolkit as a Siddhi extension.
Therefore, please go through Siddhi Extension Guide [3] to get a quick
overview regarding how to write Siddhi extensions.

In addition to that, if you are not familiar with general machine learning
concepts, I think Chapter 12 of the Mining of Massive Datasets book (link
is provided in the GSco project page) will be really helpful. Also, if you
have some free time please look at other streaming machine learning
libraries such as Apache Samoa[4].

Please go through these Siddhi/ML tutorials/guides. They will be helpful
when it comes to writing your project proposal.

Thanks,
Upul

[1]. https://github.com/wso2/siddhi
[2]. https://docs.wso2.com/display/CEP420/SiddhiQL+Guide+3.1
[3] https://docs.wso2.com/display/CEP420/Writing+Extensions+to+Siddhi
[4] https://samoa.incubator.apache.org/

On Mon, Feb 20, 2017 at 7:00 PM, Kasun Weerakoon  wrote:

> Hi all,
>
> I'm Kasun Weerakoon, final year undergraduate of University of Moratuwa,
> Sri Lanka. I'm interested about above mentioned project idea as I'm
> passionate about machine learning and deep learning techniques. I have used
> ML in my final year project and have followed the Coursera machine learning
> course by Stanford University as well as a ML course module in the
> university. I've recently participated to the Deep Learning meetup held in
> your organization. I use Java as my major programming language and
> currently  I'm following tutorials on Siddhi. I believe I'm a good
> candidate for this project and hope your guidance for this project.
>
> Regards,
> Kasun Weerakoon.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Upul Bandara,
Mob: +94 715 468 345.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS-6] Need clarifications on Unique claim(s) as user identifier in Identity Server

[Johann Nallathamby]

Hi Isura,

On Mon, Feb 20, 2017 at 5:23 PM, Isura Karunaratne  wrote:

> Hi,
>
>
>
> On Mon, Feb 20, 2017 at 2:20 PM, Johann Nallathamby 
> wrote:
>
>> Hi Ayesha,
>>
>> On Mon, Feb 20, 2017 at 11:49 AM, Ayesha Dissanayaka 
>> wrote:
>>
>>> Hi,
>>>
>>> In Identity Management we have the concept of unique claims which can
>>> only have a unique value within a domain.
>>> With the value of a unique claim we can identify a unique user within a
>>> domain. While implementing identity management capabilities in IS-6.0 User
>>> portal we came across below concerns.
>>>
>>>- System can have one or more unique claims.
>>>
>>> Can't it be zero? W have a globally unique UUID. Must we always have a
>> unique claim also within a domain? Can't we say a combination of claims
>> make the user unique? If there isn't anything like that in the system then
>> the user can't perform recovery. Is that a acceptable? I don't think in amy
>> practical system we can't find a combination of claims that identify the
>> user uniquely in the domain.
>>
>
> If it is zero, we have to use unique UUID as the unique idefier for all
> the opeartions such as authentication, recovery. It is not practical to
> remember unique UUID, so an external applicatoin should have the mapping
> between unique UUID and username. Do we support zero unique claim scenario?
>

What I meant by zero unique claims is, there is not one single unique claim
in the system. But there is a set of claims whose combination of values
will uniquely identify the user. This needs to be defined using attribute
profile.


>
> If we don't define a unique claim, how to identify the correct DomainUser
> object for authentication. Fllowing is the existing API for authentication
> and if there is no unique claim, we need to create a new API with unique
> userid.
>
>
>
>   AuthenticationContext authenticate(Claim claim, Callback[] credentials,
> String domainName)
>
> throws AuthenticationFailure, IdentityStoreException;
>
>
>
>
>
>>>- All the unique claims doesn't have to be required claims.
>>>
>>> Yes.
>>
>>>
>>>-
>>>- At least one unique claim has to be required claim.
>>>
>>> If we go with my previous explanation, if one claim isn't enough to
>> identify the user uniquely then there can be more claims that are required.
>>
>>>
>>>-
>>>
>>> For authentication and recovery scenarios we need to have a unique
>>> identifier for users. Currently we use "username" claim. I assume we need
>>> to provide the flexibility to change this identifier claim.
>>>
>>>1. Do we allow client applications to choose this identifier claim
>>>from unique claims?
>>>   - Then the IS will have to accept any of the unique claims as the
>>>   user identifier in authentication and validate against it.
>>>
>>> No need to let client applications choose this. We are talking about
>> account recovery of an account centrally and solely managed by IS, and it
>> is the sole responsibility of IS to allow its to recover their accounts
>> securely and efficiently. Applications don't need to specify criteria for
>> this process and change security requirements for the process.
>>
> +1
>
>
>>
>>>-
>>>1. Otherwise should we keep it as a system wide configuration?
>>>
>>> Yes, it's a system (tenant) configuration.
>>
>>>
>>>1. For the User Portal, we use 'username' claim as the user
>>>identifier. I have noticed we have hard-coded this claim 
>>> '*http://wso2.org/claims/username
>>>*'.
>>>1. I think we need to get this value from a configuration.
>>>   2. Is it OK to keep this as a configuration within the User
>>>   Portal.
>>>   3. Otherwise where should we keep this?
>>>   4. Will this identifier be username, for User portal always?
>>>   Otherwise we need to have the flexibility of changing UI labels 
>>> according
>>>   to the identifier without much effort.
>>>
>>> Can't this be handled by attribute profile feature? Again the answer
>> depends on the answer for my previous question, about having a set of
>> claims that uniquely identify a user in a domain.
>>
>>>
>>>1. Should we support authentication and recovery by multiple
>>>identifiers ( ex: username or email or NIC, each representing an 
>>> individual
>>>unique claim)
>>>
>>> Password based authentication - yes. Since we take in a password that
>> has very low probability of being the same of another user within the
>> domain for the same claim identifier, we can actually allow authentication
>> with any claim - doesn't necessarily have to be unique.
>>
>> However for recovery we must identify user uniquely and for that we need
>> to have a set of claims that identify the user uniquely within a domain.
>> Again can we use the attribute profile concept here?
>>
>> Regards,
>> Johann.
>>
>>> Appreciate your input on this.
>>>
>>> Thanks!
>>> -Ayesha
>>>
>>> --
>>> *Ayesha 

Re: [Dev] [IS-6] Need clarifications on Unique claim(s) as user identifier in Identity Server

[Johann Nallathamby]

On Mon, Feb 20, 2017 at 4:36 PM, Ayesha Dissanayaka  wrote:

> Hi Johann,
>
> Thanks for the clarification.
>
> On Mon, Feb 20, 2017 at 2:20 PM, Johann Nallathamby 
> wrote:
>
>> Password based authentication - yes. Since we take in a password that has
>> very low probability of being the same of another user within the domain
>> for the same claim identifier, we can actually allow authentication with
>> any claim - doesn't necessarily have to be unique.
>>
> So, we can choose some claim as the identifier for password based
> authentication at a time as a configuration in the User Portal.
>

+1


>
>
>> However for recovery we must identify user uniquely and for that we need
>> to have a set of claims that identify the user uniquely within a domain.
>> Again can we use the attribute profile concept here?
>>
>
> Agreed that we use attribute profile based approach for username recovery.
> For password recovery do we need to follow that approach. Shouldn't this
> align with whatever the claim users use to authenticate to the system in
> password based authentication?
> for example, a system may choose to use email claim as login identifier.
> Then shouldn't we ask for the same identifier at password recovery of that
> system?
>
In that case if we use a claim which is not unique, it will be hard to
> identify the user for password recovery.
>

So seems there are two options.

1. Use single unique identifier for authentication and password recovery -
if not can't do password recovery
2. Use a profile - similar to username recovery. However authentication and
recovery may be using different claims.

For me option 2 looks good if possible. If the claims required is one then
it actually converges to option 1.

Regards,
Johann.


>
> Thanks!
> -Ayesha
> --
> *Ayesha Dissanayaka*
> Software Engineer,
> WSO2, Inc : http://wso2.com
> 
> 20, Palmgrove Avenue, Colombo 3
> E-Mail: aye...@wso2.com 
>



-- 
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] Nullpointer print intermittently when the C5 product start

[Harsha Thirimanna]

I changed the mvn version, but still i am getting this issue. This is the
complete log. I am using *Kenral 5.1.0*

JAVA_HOME environment variable is set to /usr/lib/jvm/jdk1.8.0_102
CARBON_HOME environment variable is set to
/home/product-is/product/target/wso2is-6.0.0-SNAPSHOT
Listening for transport dt_socket at address: 5005
[2017-02-20 23:18:57,183]  INFO
{org.wso2.carbon.launcher.extensions.DropinsBundleDeployerUtils
updateDropins} - Successfully updated the OSGi bundle information of Carbon
Profile: default
osgi> [2017-02-20 23:19:10,338]  INFO
{org.wso2.carbon.metrics.core.config.model.JmxReporterConfig} - Creating
JMX reporter for Metrics with domain 'org.wso2.carbon.metrics'
[2017-02-20 23:19:10,356]  INFO
{org.wso2.carbon.metrics.core.reporter.impl.AbstractReporter} - Started JMX
reporter for Metrics
[2017-02-20 23:19:10,371]  INFO
{org.wso2.msf4j.analytics.metrics.MetricsComponent} - Metrics Component is
activated
[2017-02-20 23:19:10,424]  WARN
{org.wso2.carbon.kernel.internal.startupresolver.StartupComponentManager} -
Adding a RequiredCapabilityListener from
bundle(org.wso2.carbon.security.caas:1.0.0), but specified startup
component is not available, component-name: wso2-caas
[2017-02-20 23:19:10,513]  INFO
{org.wso2.msf4j.internal.MicroservicesRegistryImpl} - Added microservice:
org.wso2.msf4j.swagger.SwaggerDefinitionService@35c12c7a
[2017-02-20 23:19:10,527]  INFO
{org.wso2.msf4j.internal.MicroservicesRegistryImpl} - Added microservice:
org.wso2.carbon.identity.gateway.resource.GatewayResource@1e58512c
[2017-02-20 23:19:10,576]  INFO {com.zaxxer.hikari.HikariDataSource} -
HikariPool-0 - is starting.
[2017-02-20 23:19:10,897]  INFO {org.wso2.carbon.uuf.internal.UUFServer} -
RenderableCreator
'org.wso2.carbon.uuf.renderablecreator.hbs.internal.HbsRenderableCreator'
registered for [hbs] extensions.
[2017-02-20 23:19:10,910]  INFO {org.wso2.carbon.uuf.internal.UUFServer} -
RenderableCreator
'org.wso2.carbon.uuf.renderablecreator.html.internal.HtmlRenderableCreator'
registered for [html] extensions.
[2017-02-20 23:19:11,437]  INFO {com.zaxxer.hikari.HikariDataSource} -
HikariPool-1 - is starting.
[2017-02-20 23:19:13,906]  INFO
{org.wso2.carbon.identity.mgt.store.connector.jdbc.internal.ConnectorComponent}
- JDBC user store bundle successfully activated.
[2017-02-20 23:19:13,993]  INFO
{org.wso2.carbon.metrics.jdbc.core.config.model.JdbcReporterConfig} -
Creating JDBC reporter for Metrics with source 'carbon-kernel', data source
'java:comp/env/jdbc/WSO2MetricsDB' and 60 seconds polling period
[2017-02-20 23:19:14,020]  INFO
{org.wso2.carbon.metrics.core.reporter.impl.AbstractReporter} - Started
JDBC reporter for Metrics
[2017-02-20 23:19:14,368]  WARN
{org.wso2.carbon.kernel.internal.startupresolver.StartupComponentManager} -
You are trying to add an available capability
org.wso2.carbon.deployment.engine.Deployer from
bundle(org.wso2.carbon.identity.gateway:1.0.0.SNAPSHOT) to an already
activated startup listener component carbon-deployment-service in
bundle(org.wso2.carbon.deployment.engine:5.0.0). Refer the Startup Order
Resolver documentation and validated your configuration
[2017-02-20 23:19:14,379]  WARN
{org.wso2.carbon.kernel.internal.startupresolver.StartupComponentManager} -
You are trying to add an available capability
org.wso2.carbon.deployment.engine.Deployer from
bundle(org.wso2.carbon.identity.gateway:1.0.0.SNAPSHOT) to an already
activated startup listener component carbon-deployment-service in
bundle(org.wso2.carbon.deployment.engine:5.0.0). Refer the Startup Order
Resolver documentation and validated your configuration
[2017-02-20 23:19:14,556]  INFO
{org.wso2.carbon.identity.mgt.impl.internal.IdentityMgtComponent} - Realm
service registered successfully.
[2017-02-20 23:19:14,556]  INFO
{org.wso2.carbon.identity.mgt.impl.internal.IdentityMgtComponent} -
Carbon-Identity-Mgt bundle activated successfully.
[2017-02-20 23:19:14,632]  INFO {org.wso2.carbon.uuf.internal.UUFServer} -
'org.wso2.carbon.uuf.internal.UUFServer' registered as a Server.
[2017-02-20 23:19:14,633]  INFO
{org.wso2.carbon.transport.http.netty.internal.NettyTransportServiceComponent}
- All CarbonNettyServerInitializers are available
[2017-02-20 23:19:14,691]  INFO
{org.wso2.msf4j.internal.MicroservicesRegistryImpl} - Added microservice:
org.wso2.carbon.uuf.httpconnector.msf4j.UUFMicroservice@302c4471
[2017-02-20 23:19:14,692]  INFO
{org.wso2.carbon.uuf.httpconnector.msf4j.internal.MSF4JHttpConnector} - UUF
app 'org.wso2.carbon.iam.user-portal' is available at '/user-portal'.
[2017-02-20 23:19:14,692]  INFO
{org.wso2.msf4j.internal.MicroservicesServerSC} - All microservices are
available
[2017-02-20 23:19:14,693]  INFO
{org.wso2.carbon.transport.http.netty.listener.NettyListener} - Starting
Netty Http Transport Listener
[2017-02-20 23:19:15,137]  INFO
{org.wso2.carbon.transport.http.netty.listener.NettyListener} - Netty
Listener starting on port 9292
Exception in thread "Timer-0" java.lang.NullPointerException

Re: [Dev] [VOTE] Release WSO2 Enterprise Integrator 6.0.0 RC2

[Madhawa Gunasekara]

Hi All,

Thanks for testing and verifying the WSO2 Enterprise Integrator 6.0.0 RC2.
We are closing the vote now. This vote has passed with 5+1s and 0 -1s.
Therefore we are proceeding with the WSO2 Enterprise Integrator 6.0.0
release.

5 +1
0 -1

Thanks,
Madhawa

On Mon, Feb 20, 2017 at 7:14 PM, Madhawa Gunasekara 
wrote:

> tested DSS features
>
> [x ] Stable - go ahead and release
>
>
>
> On Mon, Feb 20, 2017 at 7:01 PM, Afkham Azeez  wrote:
>
>>
>> On Mon, Feb 20, 2017 at 6:57 PM, Malith Munasinghe 
>> wrote:
>>
>>> [ ] Stable - go ahead and release
>>
>>
>> [x ] Stable - go ahead and release
>>
>>
>> --
>> *Afkham Azeez*
>> Senior Director, Platform Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * *
>> *email: **az...@wso2.com* 
>> * cell: +94 77 3320919 <+94%2077%20332%200919>blog: *
>> *http://blog.afkham.org* 
>> *twitter: **http://twitter.com/afkham_azeez*
>> 
>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
> *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
> *
>



-- 
*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] [VOTE] Release WSO2 Enterprise Integrator 6.0.0 RC2

[Himasha Guruge]

Tested Business Process related features.

[x ] Stable - go ahead and release

On Mon, Feb 20, 2017 at 7:14 PM, Madhawa Gunasekara 
wrote:

> tested DSS features
>
> [x ] Stable - go ahead and release
>
>
>
> On Mon, Feb 20, 2017 at 7:01 PM, Afkham Azeez  wrote:
>
>>
>> On Mon, Feb 20, 2017 at 6:57 PM, Malith Munasinghe 
>> wrote:
>>
>>> [ ] Stable - go ahead and release
>>
>>
>> [x ] Stable - go ahead and release
>>
>>
>> --
>> *Afkham Azeez*
>> Senior Director, Platform Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * *
>> *email: **az...@wso2.com* 
>> * cell: +94 77 3320919 <+94%2077%20332%200919>blog: *
>> *http://blog.afkham.org* 
>> *twitter: **http://twitter.com/afkham_azeez*
>> 
>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
> *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
>
>


-- 
Himasha Guruge
*Software Engineer*
WS*O2* *Inc.*
Mobile: +94 777459299
himas...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Enterprise Integrator 6.0.0 RC2

[Madhawa Gunasekara]

tested DSS features

[x ] Stable - go ahead and release



On Mon, Feb 20, 2017 at 7:01 PM, Afkham Azeez  wrote:

>
> On Mon, Feb 20, 2017 at 6:57 PM, Malith Munasinghe 
> wrote:
>
>> [ ] Stable - go ahead and release
>
>
> [x ] Stable - go ahead and release
>
>
> --
> *Afkham Azeez*
> Senior Director, Platform Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <+94%2077%20332%200919>blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> 
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>



-- 
*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] [VOTE] Release WSO2 Enterprise Integrator 6.0.0 RC2

[Malith Munasinghe]

Tested.

- Analytics for EI
- Web application deployment
- Sample deployment
- Startup scripts

[x] Stable - go ahead and release

On Mon, Feb 20, 2017 at 7:01 PM, Afkham Azeez  wrote:

>
> On Mon, Feb 20, 2017 at 6:57 PM, Malith Munasinghe 
> wrote:
>
>> [ ] Stable - go ahead and release
>
>
> [x ] Stable - go ahead and release
>
>
> --
> *Afkham Azeez*
> Senior Director, Platform Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <+94%2077%20332%200919>blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> 
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>



-- 
Malith Munasinghe | Software Engineer
M: +94 (71) 9401122
E: mali...@wso2.com
W: http://wso2.com

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

Re: [Dev] [VOTE] Release WSO2 Enterprise Integrator 6.0.0 RC2

[Nandika Jayawardana]

Checked Integrator and Business Processes.

[x ] Stable - go ahead and release

Regards
Nandika

On Mon, Feb 20, 2017 at 7:01 PM, Afkham Azeez  wrote:

>
> On Mon, Feb 20, 2017 at 6:57 PM, Malith Munasinghe 
> wrote:
>
>> [ ] Stable - go ahead and release
>
>
> [x ] Stable - go ahead and release
>
>
> --
> *Afkham Azeez*
> Senior Director, Platform Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <077%20332%200919>blog: **http://blog.afkham.org*
> 
> *twitter: **http://twitter.com/afkham_azeez*
> 
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Nandika Jayawardana
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Enterprise Integrator 6.0.0 RC2

[Afkham Azeez]

On Mon, Feb 20, 2017 at 6:57 PM, Malith Munasinghe  wrote:

> [ ] Stable - go ahead and release


[x ] Stable - go ahead and release


-- 
*Afkham Azeez*
Senior Director, Platform Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* *
*email: **az...@wso2.com* 
* cell: +94 77 3320919blog: **http://blog.afkham.org*

*twitter: **http://twitter.com/afkham_azeez*

*linked-in: **http://lk.linkedin.com/in/afkhamazeez
*

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

[Dev] [DEV] GSoC 2017 - Real-Time Machine Learning Toolkit for Siddhi

[Kasun Weerakoon]

Hi all,

I'm Kasun Weerakoon, final year undergraduate of University of Moratuwa,
Sri Lanka. I'm interested about above mentioned project idea as I'm
passionate about machine learning and deep learning techniques. I have used
ML in my final year project and have followed the Coursera machine learning
course by Stanford University as well as a ML course module in the
university. I've recently participated to the Deep Learning meetup held in
your organization. I use Java as my major programming language and
currently  I'm following tutorials on Siddhi. I believe I'm a good
candidate for this project and hope your guidance for this project.

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

Re: [Dev] [VOTE] Release WSO2 Enterprise Integrator 6.0.0 RC2

[Malith Munasinghe]

On Mon, Feb 20, 2017 at 6:53 PM, Madhawa Gunasekara 
wrote:

> Hi Devs, This is the second release candidate of WSO2 Enterprise
> Integrator 6.0.0.
>
> The vote will be open for 24 hours or as needed. Please download, test the
> product and vote. ​​This release fixes the following issues:
> https://github.com/wso2/product-ei/issues?utf8=%E2%9C%93=i
> s%3Aissue%20is%3Aclosed%20 ​​*Source & binary distribution files*: ​
> https://svn.wso2.org/repos/wso2/scratch/EI-6.0.0/
> 
>
>
>
Please find the corrected url for the binary distribution
https://svn.wso2.org/repos/wso2/scratch/EI-6.0.0/


> *Maven staging repo:*
> https://maven.wso2.org/nexus/content/repositories/orgwso2ei-1002 *​​The
> tag to be voted upon*:
> https://github.com/wso2/product-ei/releases/tag/v6.0.0-rc2
>
>
> 
>
> *Documentation*: https://docs.wso2.com/display/
> EI600/WSO2+Enterprise+Integrator+Documentation [ ] Broken - do not
> release (explain why) [ ] Stable - go ahead and release Thanks, Integration
> Team
>
>
>
> --
> *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
>
>


-- 
Malith Munasinghe | Software Engineer
M: +94 (71) 9401122
E: mali...@wso2.com
W: http://wso2.com

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

[Dev] [VOTE] Release WSO2 Enterprise Integrator 6.0.0 RC2

[Madhawa Gunasekara]

Hi Devs, This is the second release candidate of WSO2 Enterprise Integrator
6.0.0.

The vote will be open for 24 hours or as needed. Please download, test the
product and vote. ​​This release fixes the following issues:
https://github.com/wso2/product-ei/issues?utf8=%E2%9C%93=
is%3Aissue%20is%3Aclosed%20 ​​*Source & binary distribution files*: ​
https://svn.wso2.org/repos/wso2/scratch/EI-6.0.0/



*Maven staging repo:*
https://maven.wso2.org/nexus/content/repositories/orgwso2ei-1002 *​​The tag
to be voted upon*:
https://github.com/wso2/product-ei/releases/tag/v6.0.0-rc2




*Documentation*: https://docs.wso2.com/display/
EI600/WSO2+Enterprise+Integrator+Documentation [ ] Broken - do not release
(explain why) [ ] Stable - go ahead and release Thanks, Integration Team



-- 
*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] [IS-6] Need clarifications on Unique claim(s) as user identifier in Identity Server

[Isura Karunaratne]

Hi,



On Mon, Feb 20, 2017 at 2:20 PM, Johann Nallathamby  wrote:

> Hi Ayesha,
>
> On Mon, Feb 20, 2017 at 11:49 AM, Ayesha Dissanayaka 
> wrote:
>
>> Hi,
>>
>> In Identity Management we have the concept of unique claims which can
>> only have a unique value within a domain.
>> With the value of a unique claim we can identify a unique user within a
>> domain. While implementing identity management capabilities in IS-6.0 User
>> portal we came across below concerns.
>>
>>- System can have one or more unique claims.
>>
>> Can't it be zero? W have a globally unique UUID. Must we always have a
> unique claim also within a domain? Can't we say a combination of claims
> make the user unique? If there isn't anything like that in the system then
> the user can't perform recovery. Is that a acceptable? I don't think in amy
> practical system we can't find a combination of claims that identify the
> user uniquely in the domain.
>

If it is zero, we have to use unique UUID as the unique idefier for all the
opeartions such as authentication, recovery. It is not practical to
remember unique UUID, so an external applicatoin should have the mapping
between unique UUID and username. Do we support zero unique claim scenario?

If we don't define a unique claim, how to identify the correct DomainUser
object for authentication. Fllowing is the existing API for authentication
and if there is no unique claim, we need to create a new API with unique
userid.



  AuthenticationContext authenticate(Claim claim, Callback[] credentials,
String domainName)

throws AuthenticationFailure, IdentityStoreException;





>>- All the unique claims doesn't have to be required claims.
>>
>> Yes.
>
>>
>>-
>>- At least one unique claim has to be required claim.
>>
>> If we go with my previous explanation, if one claim isn't enough to
> identify the user uniquely then there can be more claims that are required.
>
>>
>>-
>>
>> For authentication and recovery scenarios we need to have a unique
>> identifier for users. Currently we use "username" claim. I assume we need
>> to provide the flexibility to change this identifier claim.
>>
>>1. Do we allow client applications to choose this identifier claim
>>from unique claims?
>>   - Then the IS will have to accept any of the unique claims as the
>>   user identifier in authentication and validate against it.
>>
>> No need to let client applications choose this. We are talking about
> account recovery of an account centrally and solely managed by IS, and it
> is the sole responsibility of IS to allow its to recover their accounts
> securely and efficiently. Applications don't need to specify criteria for
> this process and change security requirements for the process.
>
+1


>
>>-
>>1. Otherwise should we keep it as a system wide configuration?
>>
>> Yes, it's a system (tenant) configuration.
>
>>
>>1. For the User Portal, we use 'username' claim as the user
>>identifier. I have noticed we have hard-coded this claim 
>> '*http://wso2.org/claims/username
>>*'.
>>1. I think we need to get this value from a configuration.
>>   2. Is it OK to keep this as a configuration within the User Portal.
>>   3. Otherwise where should we keep this?
>>   4. Will this identifier be username, for User portal always?
>>   Otherwise we need to have the flexibility of changing UI labels 
>> according
>>   to the identifier without much effort.
>>
>> Can't this be handled by attribute profile feature? Again the answer
> depends on the answer for my previous question, about having a set of
> claims that uniquely identify a user in a domain.
>
>>
>>1. Should we support authentication and recovery by multiple
>>identifiers ( ex: username or email or NIC, each representing an 
>> individual
>>unique claim)
>>
>> Password based authentication - yes. Since we take in a password that has
> very low probability of being the same of another user within the domain
> for the same claim identifier, we can actually allow authentication with
> any claim - doesn't necessarily have to be unique.
>
> However for recovery we must identify user uniquely and for that we need
> to have a set of claims that identify the user uniquely within a domain.
> Again can we use the attribute profile concept here?
>
> Regards,
> Johann.
>
>> Appreciate your input on this.
>>
>> Thanks!
>> -Ayesha
>>
>> --
>> *Ayesha Dissanayaka*
>> Software Engineer,
>> WSO2, Inc : http://wso2.com
>> 
>> 20, Palmgrove Avenue, Colombo 3
>> E-Mail: aye...@wso2.com 
>>
>
>
>
> --
> Thanks & Regards,
>
> *Johann Dilantha Nallathamby*
> Technical Lead & Product Lead of WSO2 Identity Server
> Governance Technologies Team
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - *+9476950*
> Blog - 

[Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Dinuksha Ishwari]

Hi All,


I am Dinuksha Kanda Samanage, a 3rd year undergraduate from Sri Lanka
Institute of Information Technology, following the Software Engineering
specialization.


This is to convey my interest in implementing the OAuth 2.0 Dynamic Client
Registration Management Protocol Support for Identity Server (Proposal 20)
in GSoC 2017.


I am well versed in Java and also familiar with Maven and Git. I have been
involved in implementing an OAuth 2.0 and OpenID Connect related project
for almost 7 months during my internship.


I have already started to get familiar with WSO2 codebase and fixed the
JIRA [1] where the pull request is already merged to the WSO2 codebase. I
will continue fixing more open JIRA tickets on Identity Server. (If you can
suggest some, that would be great too)


In order to get ready for this project, I already setup OAuth 2.0
Playground2 sample with Identity Server 5.3.0 and wrote the blog post [2]
for sharing my experience. When running this flow, I faced an issue and
raised it in the Dev mail [3] and have got the answer now.


My GitHub profile can be found at [4].


Therefore I believe I can learn the required concepts/technologies and
implement this project for GSoC 2017.


I appreciate if you can guide me on proceeding further with the project.


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

[2]
http://dinukshaish.blogspot.com/2017/02/getting-started-with-oauth-20-using.html

[3] [Dev] Mandatory Claims in OAuth 2.0 with Identity Server 5.3.0

[4] https://github.com/dinuish94


Best Regards,

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

Re: [Dev] [IS-6] Need clarifications on Unique claim(s) as user identifier in Identity Server

[Ayesha Dissanayaka]

Hi Johann,

Thanks for the clarification.

On Mon, Feb 20, 2017 at 2:20 PM, Johann Nallathamby  wrote:

> Password based authentication - yes. Since we take in a password that has
> very low probability of being the same of another user within the domain
> for the same claim identifier, we can actually allow authentication with
> any claim - doesn't necessarily have to be unique.
>
So, we can choose some claim as the identifier for password based
authentication at a time as a configuration in the User Portal.


> However for recovery we must identify user uniquely and for that we need
> to have a set of claims that identify the user uniquely within a domain.
> Again can we use the attribute profile concept here?
>

Agreed that we use attribute profile based approach for username recovery.
For password recovery do we need to follow that approach. Shouldn't this
align with whatever the claim users use to authenticate to the system in
password based authentication?
for example, a system may choose to use email claim as login identifier.
Then shouldn't we ask for the same identifier at password recovery of that
system?
In that case if we use a claim which is not unique, it will be hard to
identify the user for password recovery.

Thanks!
-Ayesha
-- 
*Ayesha Dissanayaka*
Software Engineer,
WSO2, Inc : http://wso2.com

20, Palmgrove Avenue, Colombo 3
E-Mail: aye...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSoC 2017 Proposal 24

[Upul Bandara]

Hi Sujeeharan,

We are glad to see your interest!

The main objective of this project is to develop a real-time machine
learning toolkit for Siddhi [1]. Siddhi CEP is a lightweight, easy-to-use
Open Source Complex Event Processing Engine (CEP) released as a Java
Library under Apache Software License v2.0. The readme page of the Siddhi's
Github repository contains a good overview of the Siddhi library. Also,
SiddhiQL Guide [2] will be helpful you to understand Siddhi Query Language.

Most probably, we will be writing this toolkit as a Siddhi extension.
Therefore, please go through Siddhi Extension Guide [3] to get a quick
overview regarding how to write Siddhi extensions.

In addition to that, if you are not familiar with general machine learning
concepts, I think Chapter 12 of the Mining of Massive Datasets book (link
is provided in the GSco project page) will be really helpful. Also, if you
have some free time please look at other streaming machine learning
libraries such as Apache Samoa[4].

Please go through these Siddhi/ML tutorials/guides. They will be helpful
when it comes to writing your project proposal.

Thanks,
Upul

[1]. https://github.com/wso2/siddhi
[2]. https://docs.wso2.com/display/CEP420/SiddhiQL+Guide+3.1
[3] https://docs.wso2.com/display/CEP420/Writing+Extensions+to+Siddhi
[4] https://samoa.incubator.apache.org/

On Mon, Feb 20, 2017 at 3:15 PM, Sujeeharan Ganeshan  wrote:

> Hi Upul and Suhothayan,
>
> We are a set of four final year students from Sri Lanka Institute of
> Information and Technology. While we were looking for GSoC related projects
> and researches for our 4th Year CDAP Module we came across WSO2 and found
> some project. Since we are interested in the area Artificial Intelligence
> we thought of doing something that is related to that area. And we came
> across your project proposal Real-Time machine learning toolkit for Siddhi.
> We are interested to work with you in this project. We all are familiar
> with Java well. And we are in the process of learning about ML as well
> (Actually taking a course in Coursera by Stanford University ). We hope we
> made a good impression.
> We hope to work with you all in this project.
>
> Thanks and Regards
> Sujeeharan
> Sri Lanka Institute of Information and Technology
>



-- 
Upul Bandara,
Associate Technical Lead, WSO2, Inc.,
Mob: +94 715 468 345.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSOC 2017 -CLI tool for WSO2 API Manager

[Heshan Jayasinghe]

Hi Pubudu,

Thank you for your reply.Now I am in the API manager installing process.
I'll go through all these resources and get back to you soon.

Thanks

regards,

Heshan jayasinghe

On Mon, Feb 20, 2017 at 11:47 AM, Pubudu Gunatilaka 
wrote:

> Hi Heshan,
>
> Thank you for your interest in the project. As explained in the project
> description, you need to develop a CLI tool for API Manager capabilities.
>
> First of all, you can try out WSO2 API Manager 2.1.0 and get familiar with
> the product [1] and the concepts [2]. Additionally, you can try out API
> export/import feature [3] and the API Manager 2.1.0 REST APIs [4] to tryout
> the product.
>
> Currently, WSO2 API Manager team is working on Carbon 5(C5) based API
> Manager implementation and you can find the relevant repos in [5] and [6].
> When you are developing the CLI, you should use the C5 REST APIs. API
> Manager team has already added most important REST APIs and we are working
> on adding new REST APIs based on the functionalities. Meantime, you can
> also get familiar with GO language and learn the concepts.
>
> [1] - http://wso2.com/products/api-manager/
> [2] - https://docs.wso2.com/display/AM210/Key+Concepts
> [3] - https://docs.wso2.com/display/AM210/Migrating+the+
> APIs+to+a+Different+Environment
> [4] - https://docs.wso2.com/display/AM210/WSO2+APIs
> [5] - https://github.com/wso2/carbon-apimgt/tree/C5
> [6] - https://github.com/wso2/product-apim/tree/C5
>
> Thank you!
>
> On Mon, Feb 20, 2017 at 10:49 AM, Sajith Abeywardhana 
> wrote:
>
>> Adding project mentors.
>>
>> On Mon, Feb 20, 2017 at 9:33 AM, Heshan Jayasinghe 
>> wrote:
>>
>>> Hi all,
>>>
>>> I am Heshan Jayasinghe 4th year undergraduate of university of
>>> moratuwa,Srilanka. I have experience in Java/MEAN/android/Go projects. I
>>> was GSOC 2016 participant with your Organization and successfully finish
>>> all my tasks and complete my project.
>>>
>>> I go though all the information you mention in this project and I go
>>> though Go sample CLI tools examples too.I familiar with REST services in
>>> java and node.js and haven't more experience using Go.I think i
>>> can familiar with those areas before start this project. Could you
>>> please give me further information about this projects then i can research
>>> on those area.
>>>
>>> Thank you,
>>> regards,
>>>
>>> Heshan Jayasinghe
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Sajith Abeywardhana* | Software Engineer
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka.
>> Mobile: +94772260485
>> Email: saji...@wso2.com | Web: www.wso2.com
>>
>
>
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Governance Registry 5.4.0 RC2

[Chandana Napagoda]

Hi All,

Thanks for testing and verifying the WSO2 Governance Registry 5.4.0 RC2. We
are closing this vote now. This vote has passed with 8 +1s and 0 -1s.
Therefore we are proceeding with the WSO2 Governance Registry 5.4.0 release.

8 +1s
0  -1s

Thanks and Regards,
G-Reg Team

On Mon, Feb 20, 2017 at 2:23 PM, Chandana Napagoda 
wrote:

> Hi,
>
> Tested following scenarios:
>
> - Lifecycle Voting
> - Lifecycle permission
> - Multiple Lifecycles
> - Publisher asset CRUD operations
>
> [X] Stable
>
> Regards,
> Chandana
>
>
>
>
>
> On Mon, Feb 20, 2017 at 1:50 PM, Thushara Kasun Ranawaka <
> thusharade...@gmail.com> wrote:
>
>> Hi All,
>>
>> Tested the following scenarios in standalone setup
>>
>> Adding custom artifact(with and without version) and related
>> operations(versioning, association, lifecycle)
>> Adding new association types.
>> Getting started guide
>> Dependency view and its new operations
>>
>> [X] Stable - Go ahead and release
>>
>> Thanks,
>> Thushara.
>>
>>
>> On Mon, Feb 20, 2017 at 1:55 PM, Chanaka Jayasena 
>> wrote:
>>
>>> Hi all,
>>>
>>> Tested following scenarios,
>>>
>>>
>>>- Add new rxt
>>>- Create, update, delete assets
>>>- Create new version of an asset
>>>- Change lifecycle version of an asset
>>>- Review and rate assets in store.
>>>- Store basic search - tags search, lcState Search, version search,
>>>tags search, name search.
>>>
>>>
>>> Found no blockers.
>>>
>>> [+} Stable - go ahead and release
>>>
>>> thanks,
>>> Chanaka
>>>
>>>
>>>
>>> On Mon, Feb 20, 2017 at 10:51 AM, Rajith Roshan 
>>> wrote:
>>>
 Hi all,
 Tested following scenarios.

- Getting started sample
- Bi directional associations
- Life cycle transitions
- Attribute search in publisher

 Found no blockers.

 [+] Stable - go ahead and release

 Thanks!
 Rajith



 On Mon, Feb 20, 2017 at 10:46 AM, Kasun Thennakoon 
 wrote:

> Hi all,
>
> Tested following scenarios:
>
>- Adding and then editing user reviews
>- Voting on user reviews
>- Store notifications when Lifecycle State Change and Information
>Update
>- Create new version of an asset
>- Sorting assets in Store and Publisher
>
> Found no major issues.
>
> [X] Stable - Go ahead and release
>
> On Sun, Feb 19, 2017 at 4:12 PM, Chandana Napagoda 
> wrote:
>
>> Hi Devs,
>>
>> WSO2 Governance Registry 5.4.0 RC2 Release Vote.
>>
>>
>> This release fixes the following issues:
>> https://wso2.org/jira/issues/?filter=13649
>>
>> The vote will be open for 24 hours or as needed. Please download,
>> test and vote. Please refer the release verification guide for detailed
>> information on verifying this release.
>>
>> Source & binary distribution files:
>> https://svn.wso2.org/repos/wso2/scratch/G-Reg/5.4.0/RC2
>>
>> Maven staging repo:
>> https://maven.wso2.org/nexus/content/repositories/orgwso2greg-1010
>>
>> The tag to be voted upon:
>> https://github.com/wso2/product-greg/releases/tag/v5.4.0-RC2
>>
>>
>> [+] Stable - go ahead and release
>> [-]  Broken - do not release (explain why)
>>
>> Thanks and Regards
>> G-Reg team
>>
>> --
>> *Chandana Napagoda*
>> Associate Technical Lead
>> WSO2 Inc. - http://wso2.org
>>
>> *Email  :  chand...@wso2.com **Mobile :
>> +94718169299 <+94%2071%20816%209299>*
>>
>> *Blog  :http://cnapagoda.blogspot.com
>>  | http://chandana.napagoda.com
>> *
>>
>> *Linkedin : http://www.linkedin.com/in/chandananapagoda
>> *
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Kasun Thennakoon*
> Software Engineer
> WSO2, Inc.
> Mobile:+94 711661919
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Rajith Roshan
 Software Engineer, WSO2 Inc.
 Mobile: +94-72-642-8350 <%2B94-71-554-8430>

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


>>>
>>>
>>> --
>>> Chanaka Jayasena
>>> Associate Tech Lead,
>>> email: chan...@wso2.com; cell: +94 77 4464006 <+94%2077%20446%204006>
>>> blog: http://chanaka3d.blogspot.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> 

Re: [Dev] [VOTE] Release WSO2 Governance Registry 5.4.0 RC2

[Chandana Napagoda]

Hi,

Tested following scenarios:

- Lifecycle Voting
- Lifecycle permission
- Multiple Lifecycles
- Publisher asset CRUD operations

[X] Stable

Regards,
Chandana





On Mon, Feb 20, 2017 at 1:50 PM, Thushara Kasun Ranawaka <
thusharade...@gmail.com> wrote:

> Hi All,
>
> Tested the following scenarios in standalone setup
>
> Adding custom artifact(with and without version) and related
> operations(versioning, association, lifecycle)
> Adding new association types.
> Getting started guide
> Dependency view and its new operations
>
> [X] Stable - Go ahead and release
>
> Thanks,
> Thushara.
>
>
> On Mon, Feb 20, 2017 at 1:55 PM, Chanaka Jayasena 
> wrote:
>
>> Hi all,
>>
>> Tested following scenarios,
>>
>>
>>- Add new rxt
>>- Create, update, delete assets
>>- Create new version of an asset
>>- Change lifecycle version of an asset
>>- Review and rate assets in store.
>>- Store basic search - tags search, lcState Search, version search,
>>tags search, name search.
>>
>>
>> Found no blockers.
>>
>> [+} Stable - go ahead and release
>>
>> thanks,
>> Chanaka
>>
>>
>>
>> On Mon, Feb 20, 2017 at 10:51 AM, Rajith Roshan  wrote:
>>
>>> Hi all,
>>> Tested following scenarios.
>>>
>>>- Getting started sample
>>>- Bi directional associations
>>>- Life cycle transitions
>>>- Attribute search in publisher
>>>
>>> Found no blockers.
>>>
>>> [+] Stable - go ahead and release
>>>
>>> Thanks!
>>> Rajith
>>>
>>>
>>>
>>> On Mon, Feb 20, 2017 at 10:46 AM, Kasun Thennakoon 
>>> wrote:
>>>
 Hi all,

 Tested following scenarios:

- Adding and then editing user reviews
- Voting on user reviews
- Store notifications when Lifecycle State Change and Information
Update
- Create new version of an asset
- Sorting assets in Store and Publisher

 Found no major issues.

 [X] Stable - Go ahead and release

 On Sun, Feb 19, 2017 at 4:12 PM, Chandana Napagoda 
 wrote:

> Hi Devs,
>
> WSO2 Governance Registry 5.4.0 RC2 Release Vote.
>
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=13649
>
> The vote will be open for 24 hours or as needed. Please download,
> test and vote. Please refer the release verification guide for detailed
> information on verifying this release.
>
> Source & binary distribution files:
> https://svn.wso2.org/repos/wso2/scratch/G-Reg/5.4.0/RC2
>
> Maven staging repo:
> https://maven.wso2.org/nexus/content/repositories/orgwso2greg-1010
>
> The tag to be voted upon:
> https://github.com/wso2/product-greg/releases/tag/v5.4.0-RC2
>
>
> [+] Stable - go ahead and release
> [-]  Broken - do not release (explain why)
>
> Thanks and Regards
> G-Reg team
>
> --
> *Chandana Napagoda*
> Associate Technical Lead
> WSO2 Inc. - http://wso2.org
>
> *Email  :  chand...@wso2.com **Mobile :
> +94718169299 <+94%2071%20816%209299>*
>
> *Blog  :http://cnapagoda.blogspot.com
>  | http://chandana.napagoda.com
> *
>
> *Linkedin : http://www.linkedin.com/in/chandananapagoda
> *
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Kasun Thennakoon*
 Software Engineer
 WSO2, Inc.
 Mobile:+94 711661919

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


>>>
>>>
>>> --
>>> Rajith Roshan
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94-72-642-8350 <%2B94-71-554-8430>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Chanaka Jayasena
>> Associate Tech Lead,
>> email: chan...@wso2.com; cell: +94 77 4464006 <+94%2077%20446%204006>
>> blog: http://chanaka3d.blogspot.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Chandana Napagoda*
Associate Technical Lead
WSO2 Inc. - http://wso2.org

*Email  :  chand...@wso2.com **Mobile : +94718169299*

*Blog  :http://cnapagoda.blogspot.com  |
http://chandana.napagoda.com *

*Linkedin : http://www.linkedin.com/in/chandananapagoda
*

Re: [Dev] [IS-6] Need clarifications on Unique claim(s) as user identifier in Identity Server

[Johann Nallathamby]

Hi Ayesha,

On Mon, Feb 20, 2017 at 11:49 AM, Ayesha Dissanayaka 
wrote:

> Hi,
>
> In Identity Management we have the concept of unique claims which can only
> have a unique value within a domain.
> With the value of a unique claim we can identify a unique user within a
> domain. While implementing identity management capabilities in IS-6.0 User
> portal we came across below concerns.
>
>- System can have one or more unique claims.
>
> Can't it be zero? W have a globally unique UUID. Must we always have a
unique claim also within a domain? Can't we say a combination of claims
make the user unique? If there isn't anything like that in the system then
the user can't perform recovery. Is that a acceptable? I don't think in amy
practical system we can't find a combination of claims that identify the
user uniquely in the domain.

>
>- All the unique claims doesn't have to be required claims.
>
> Yes.

>
>-
>- At least one unique claim has to be required claim.
>
> If we go with my previous explanation, if one claim isn't enough to
identify the user uniquely then there can be more claims that are required.

>
>-
>
> For authentication and recovery scenarios we need to have a unique
> identifier for users. Currently we use "username" claim. I assume we need
> to provide the flexibility to change this identifier claim.
>
>1. Do we allow client applications to choose this identifier claim
>from unique claims?
>   - Then the IS will have to accept any of the unique claims as the
>   user identifier in authentication and validate against it.
>
> No need to let client applications choose this. We are talking about
account recovery of an account centrally and solely managed by IS, and it
is the sole responsibility of IS to allow its to recover their accounts
securely and efficiently. Applications don't need to specify criteria for
this process and change security requirements for the process.

>
>-
>1. Otherwise should we keep it as a system wide configuration?
>
> Yes, it's a system (tenant) configuration.

>
>1. For the User Portal, we use 'username' claim as the user
>identifier. I have noticed we have hard-coded this claim 
> '*http://wso2.org/claims/username
>*'.
>1. I think we need to get this value from a configuration.
>   2. Is it OK to keep this as a configuration within the User Portal.
>   3. Otherwise where should we keep this?
>   4. Will this identifier be username, for User portal always?
>   Otherwise we need to have the flexibility of changing UI labels 
> according
>   to the identifier without much effort.
>
> Can't this be handled by attribute profile feature? Again the answer
depends on the answer for my previous question, about having a set of
claims that uniquely identify a user in a domain.

>
>1. Should we support authentication and recovery by multiple
>identifiers ( ex: username or email or NIC, each representing an individual
>unique claim)
>
> Password based authentication - yes. Since we take in a password that has
very low probability of being the same of another user within the domain
for the same claim identifier, we can actually allow authentication with
any claim - doesn't necessarily have to be unique.

However for recovery we must identify user uniquely and for that we need to
have a set of claims that identify the user uniquely within a domain. Again
can we use the attribute profile concept here?

Regards,
Johann.

> Appreciate your input on this.
>
> Thanks!
> -Ayesha
>
> --
> *Ayesha Dissanayaka*
> Software Engineer,
> WSO2, Inc : http://wso2.com
> 
> 20, Palmgrove Avenue, Colombo 3
> E-Mail: aye...@wso2.com 
>



-- 
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] [VOTE] Release WSO2 Governance Registry 5.4.0 RC2

[Danesh Kuruppu]

Hi all,

Tested the following with linux environment with mssql mounted setup.

* Getting Started sample.
* Store search(advanced queries) and search history feature.
* Publisher search
* add new rxt and new lifecycle.
* asset CRUD operations and lifecycle operations.
* Reporting sample

[X] Stable - Go ahead and release

Thanks
Danesh

On Mon, Feb 20, 2017 at 1:50 PM, Thushara Kasun Ranawaka <
thusharade...@gmail.com> wrote:

> Hi All,
>
> Tested the following scenarios in standalone setup
>
> Adding custom artifact(with and without version) and related
> operations(versioning, association, lifecycle)
> Adding new association types.
> Getting started guide
> Dependency view and its new operations
>
> [X] Stable - Go ahead and release
>
> Thanks,
> Thushara.
>
>
> On Mon, Feb 20, 2017 at 1:55 PM, Chanaka Jayasena 
> wrote:
>
>> Hi all,
>>
>> Tested following scenarios,
>>
>>
>>- Add new rxt
>>- Create, update, delete assets
>>- Create new version of an asset
>>- Change lifecycle version of an asset
>>- Review and rate assets in store.
>>- Store basic search - tags search, lcState Search, version search,
>>tags search, name search.
>>
>>
>> Found no blockers.
>>
>> [+} Stable - go ahead and release
>>
>> thanks,
>> Chanaka
>>
>>
>>
>> On Mon, Feb 20, 2017 at 10:51 AM, Rajith Roshan  wrote:
>>
>>> Hi all,
>>> Tested following scenarios.
>>>
>>>- Getting started sample
>>>- Bi directional associations
>>>- Life cycle transitions
>>>- Attribute search in publisher
>>>
>>> Found no blockers.
>>>
>>> [+] Stable - go ahead and release
>>>
>>> Thanks!
>>> Rajith
>>>
>>>
>>>
>>> On Mon, Feb 20, 2017 at 10:46 AM, Kasun Thennakoon 
>>> wrote:
>>>
 Hi all,

 Tested following scenarios:

- Adding and then editing user reviews
- Voting on user reviews
- Store notifications when Lifecycle State Change and Information
Update
- Create new version of an asset
- Sorting assets in Store and Publisher

 Found no major issues.

 [X] Stable - Go ahead and release

 On Sun, Feb 19, 2017 at 4:12 PM, Chandana Napagoda 
 wrote:

> Hi Devs,
>
> WSO2 Governance Registry 5.4.0 RC2 Release Vote.
>
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=13649
>
> The vote will be open for 24 hours or as needed. Please download,
> test and vote. Please refer the release verification guide for detailed
> information on verifying this release.
>
> Source & binary distribution files:
> https://svn.wso2.org/repos/wso2/scratch/G-Reg/5.4.0/RC2
>
> Maven staging repo:
> https://maven.wso2.org/nexus/content/repositories/orgwso2greg-1010
>
> The tag to be voted upon:
> https://github.com/wso2/product-greg/releases/tag/v5.4.0-RC2
>
>
> [+] Stable - go ahead and release
> [-]  Broken - do not release (explain why)
>
> Thanks and Regards
> G-Reg team
>
> --
> *Chandana Napagoda*
> Associate Technical Lead
> WSO2 Inc. - http://wso2.org
>
> *Email  :  chand...@wso2.com **Mobile :
> +94718169299 <+94%2071%20816%209299>*
>
> *Blog  :http://cnapagoda.blogspot.com
>  | http://chandana.napagoda.com
> *
>
> *Linkedin : http://www.linkedin.com/in/chandananapagoda
> *
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Kasun Thennakoon*
 Software Engineer
 WSO2, Inc.
 Mobile:+94 711661919

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


>>>
>>>
>>> --
>>> Rajith Roshan
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94-72-642-8350 <%2B94-71-554-8430>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Chanaka Jayasena
>> Associate Tech Lead,
>> email: chan...@wso2.com; cell: +94 77 4464006 <+94%2077%20446%204006>
>> blog: http://chanaka3d.blogspot.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Danesh Kuruppu*
Senior Software Engineer | WSO2

Email: dan...@wso2.com
Mobile: +94 (77) 1690552
Web: WSO2 Inc 
___
Dev mailing list
Dev@wso2.org

Re: [Dev] [VOTE] Release WSO2 Governance Registry 5.4.0 RC2

[Thushara Kasun Ranawaka]

Hi All,

Tested the following scenarios in standalone setup

Adding custom artifact(with and without version) and related
operations(versioning, association, lifecycle)
Adding new association types.
Getting started guide
Dependency view and its new operations

[X] Stable - Go ahead and release

Thanks,
Thushara.


On Mon, Feb 20, 2017 at 1:55 PM, Chanaka Jayasena  wrote:

> Hi all,
>
> Tested following scenarios,
>
>
>- Add new rxt
>- Create, update, delete assets
>- Create new version of an asset
>- Change lifecycle version of an asset
>- Review and rate assets in store.
>- Store basic search - tags search, lcState Search, version search,
>tags search, name search.
>
>
> Found no blockers.
>
> [+} Stable - go ahead and release
>
> thanks,
> Chanaka
>
>
>
> On Mon, Feb 20, 2017 at 10:51 AM, Rajith Roshan  wrote:
>
>> Hi all,
>> Tested following scenarios.
>>
>>- Getting started sample
>>- Bi directional associations
>>- Life cycle transitions
>>- Attribute search in publisher
>>
>> Found no blockers.
>>
>> [+] Stable - go ahead and release
>>
>> Thanks!
>> Rajith
>>
>>
>>
>> On Mon, Feb 20, 2017 at 10:46 AM, Kasun Thennakoon 
>> wrote:
>>
>>> Hi all,
>>>
>>> Tested following scenarios:
>>>
>>>- Adding and then editing user reviews
>>>- Voting on user reviews
>>>- Store notifications when Lifecycle State Change and Information
>>>Update
>>>- Create new version of an asset
>>>- Sorting assets in Store and Publisher
>>>
>>> Found no major issues.
>>>
>>> [X] Stable - Go ahead and release
>>>
>>> On Sun, Feb 19, 2017 at 4:12 PM, Chandana Napagoda 
>>> wrote:
>>>
 Hi Devs,

 WSO2 Governance Registry 5.4.0 RC2 Release Vote.


 This release fixes the following issues:
 https://wso2.org/jira/issues/?filter=13649

 The vote will be open for 24 hours or as needed. Please download, test
 and vote. Please refer the release verification guide for detailed
 information on verifying this release.

 Source & binary distribution files:
 https://svn.wso2.org/repos/wso2/scratch/G-Reg/5.4.0/RC2

 Maven staging repo:
 https://maven.wso2.org/nexus/content/repositories/orgwso2greg-1010

 The tag to be voted upon:
 https://github.com/wso2/product-greg/releases/tag/v5.4.0-RC2


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

 Thanks and Regards
 G-Reg team

 --
 *Chandana Napagoda*
 Associate Technical Lead
 WSO2 Inc. - http://wso2.org

 *Email  :  chand...@wso2.com **Mobile :
 +94718169299 <+94%2071%20816%209299>*

 *Blog  :http://cnapagoda.blogspot.com
  | http://chandana.napagoda.com
 *

 *Linkedin : http://www.linkedin.com/in/chandananapagoda
 *


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


>>>
>>>
>>> --
>>> *Kasun Thennakoon*
>>> Software Engineer
>>> WSO2, Inc.
>>> Mobile:+94 711661919
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Rajith Roshan
>> Software Engineer, WSO2 Inc.
>> Mobile: +94-72-642-8350 <%2B94-71-554-8430>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Chanaka Jayasena
> Associate Tech Lead,
> email: chan...@wso2.com; cell: +94 77 4464006 <+94%2077%20446%204006>
> blog: http://chanaka3d.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev