Re: [Dev] clarification on api publisher on summary tables

[Rukshan Premathunga]

Hi all,

Still we are publishing API creator for API publisher field for all the
event streams. Even in registry, API publisher is not maintain and only
creator field is updated. So can we continue with this behavior or do we
need to any changes to the event stream?

any suggestions?

Thanks and Regards.

On Fri, May 27, 2016 at 5:29 PM, Shavantha Weerasinghe 
wrote:

> Hi Nuwan/Ruckshan
>
> On API Manager if we have 3 separate users with creator/publisher and
> subscriber only user roles, once stats are published to analytics server,
> the summary tables show creator@carbon.super as the API Publisher. Is
> this the expected behavior.
>
> Should the system show the actual owner of the API or the person who
> published it
>
> regards,
> Shavantha Weerasinghe
> Senior Software Engineer QA
> WSO2, Inc.
> lean.enterprise.middleware.
> http://wso2.com
> http://wso2.org
> Tel : 94 11 214 5345
> Fax :94 11 2145300
>
>


-- 
Rukshan Chathuranga.
Software Engineer.
WSO2, Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSOC 2016: Proposal 7

[Dinanjana Gunaratne]

Hello all,
I am facing a problem when trying to create a proxy object. I couldn't find
correct maven dependency to get class
org.apache.synapse.transport.passthru.jmx.TransportView. Can you direct me
to the correct dependency.


On Sat, May 14, 2016 at 8:46 PM, Dinanjana Gunaratne <
dinanjanagunara...@gmail.com> wrote:

> Dear all,
> I have added DynamicReports (which is an implementation based on Jasper
> reports) as the reporting framework for the Flight recorder. It would be
> great if I can have wso2 license headers for refactor. Direct me for
> IntelliJ headers. All changes can be seen here [1]
> 
>
> [1 ]https://github.com/dinanjana/ESBMonitor
>
> On Fri, May 6, 2016 at 10:43 PM, Dinanjana Gunaratne <
> dinanjanagunara...@gmail.com> wrote:
>
>> [1]https://github.com/dinanjana/ESBMonitor
>>
>> On Fri, May 6, 2016 at 10:42 PM, Dinanjana Gunaratne <
>> dinanjanagunara...@gmail.com> wrote:
>>
>>> Hello all,
>>> I have started working on the project. You can have a look on what I am
>>> doing from this repo [1]. Currently I am implementing heap dump creator for
>>> this project. Can you explain me how currently heap dump analyzing take
>>> place with ESB OOM events ? In the current implementation of the flight
>>> recorder this method creates a .bin file with a snapshot of heap memory.
>>>
>>> On Sun, May 1, 2016 at 10:01 PM, Dinanjana Gunaratne <
>>> dinanjanagunara...@gmail.com> wrote:
>>>
 Hello all,
 I have started working on the project. You can have a look on what i
 will be doing on this [1] 
 repo. Meanwhile let me know if there is any coding convention I must adhere
 to. And I chose Jasper reports as the reporting frame work. Hope it is 
 okay.
 [1] https://github.com/dinanjana/ESBMonitor

 On Wed, Apr 27, 2016 at 8:07 AM, Dinanjana Gunaratne <
 dinanjanagunara...@gmail.com> wrote:

> Hi all,
> Thanks for accepting my project proposal. :) Thank you very much on
> helping me to prepare a good proposal. I am looking forward to get started
> with the project ASAP
>
> On Sat, Mar 26, 2016 at 12:16 PM, Isuru Udana  wrote:
>
>> Hi Dinanjana,
>>
>>
>>
>> On Sat, Mar 26, 2016 at 8:31 AM, Dinanjana Gunaratne <
>> dinanjanagunara...@gmail.com> wrote:
>>
>>> Hi Kasun,
>>> So shall I update the draft ? What do you think. I think the best
>>> approach is to make this a separate application. Otherwise it will 
>>> anyways
>>> have an effect on the performance of ESB. Because this tool includes 
>>> some
>>> serious IO operations
>>>
>> Even though we built it as a separate application while we are taking
>> thread-dumps, etc, can lead to a degrade in performance to a great 
>> extent,
>> that's why we need to design it carefully.
>>
>> Thanks.
>>
>>>
>>> On Sat, Mar 26, 2016 at 8:25 AM, Kasun Indrasiri 
>>> wrote:
>>>
 It's fine. But just want to make sure this is added to the project
 plan as we move forward.

 On Sat, Mar 26, 2016 at 8:01 AM, Dinanjana Gunaratne <
 dinanjanagunara...@gmail.com> wrote:

> Hi Kasun ,
> It's now I saw this mail. Can I do the change now ? I guess it's
> too late now. Anyway on your second point I have said that making 
> flight
> recorder a separate application will stop applying any performance
> degradation on ESB. Anyway it would have been better if I have added 
> the
> comparison.Can I do those changes now ?And i am really sorry for the 
> late
> reply.
>
> On Fri, Mar 25, 2016 at 11:54 PM, Kasun Indrasiri 
> wrote:
>
>> Dinanjana, can you please include several use cases related to
>> possible production issues in an ESB (such as out of memory, CPU 
>> spinning,
>> deadlock etc.). Also, running the ESB flight recorder should have 
>> minimal
>> impact on the ESB performance. Hence your proposal should include an 
>> ESB
>> performance comparison with and without flight recorder.
>>
>> The proposal looks good.
>>
>> Thanks,
>> Kasun
>>
>> On Fri, Mar 25, 2016 at 6:37 PM, Dinanjana Gunaratne <
>> dinanjanagunara...@gmail.com> wrote:
>>
>>> Hi Isuru ,
>>> Thanks for the input :)
>>>
>>> On Fri, Mar 25, 2016 at 6:37 PM, Dinanjana Gunaratne <
>>> dinanjanagunara...@gmail.com> wrote:
>>>
 Hi Isuru ,
 Thanks for the input :)

 On Fri, Mar 25, 2016 at 6:34 PM, Isuru Udana 
 wrote:

> Hi Dinanjana,
>
> Proposal looks really good to me. Added several comments as
> well.

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

[Isuru Haththotuwa]

Hi Osura,

On Sun, May 29, 2016 at 12:32 AM, Osura Rathnayake 
wrote:

> Hi Isuru,
>
> Please find the attached project zip. From line 108 to 148 I hard coded
> because I was getting errors with StringTokenizer and I didn't want to
> focus much on that.
> Okay I'm right on writing the actual membership scheme.
>
Thanks. Will have a look.

It would be better if you can commit this to a github repository. By doing
that, your sample is available for anyone to use/refer. Make sure to remove
any sensitive information (passwords, etc.) before doing so.

>
> thanks
>
> On Sat, May 28, 2016 at 10:19 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> These are great findings!
>>
>> Can you please share the sample code that you wrote?
>>
>> The next step would be to start writing the actual membership scheme.
>> Please refer the Kubernetes Membership scheme as a reference.
>>
>>
>> On Sat, May 28, 2016 at 9:06 PM, Osura Rathnayake 
>> wrote:
>>
>>> Hi All,
>>>
>>>
>>>
>>> This is the summary of everything that I have done so far.
>>>
>>>
>>>
>>> Pre requisite: VMs which has WSO2 Application Server running should have
>>> been added to a particular network security group (NSG). In my case it’s
>>> ASNSG
>>>
>>>
>>>
>>> First the java app should be authenticated. Then it query for the
>>> information on ASNSG. Response of that API call includes names of all the
>>> network interfaces that are existed in ASNSG. Then each and every network
>>> interface is queried using their names to get private IP addresses of each
>>> of them. As the final outcome we get a list of IP addresses of VMs which
>>> has WSO2 Application Server running.
>>>
>>>
>>>
>>> *Authentication*
>>>
>>> In order to work with Azure Resource Manager (ARM) REST API, first of
>>> all our app has to be authenticated. ARM provides two methods for this
>>> purpose,
>>>
>>>
>>>
>>> 1) Authenticate using service principal
>>>
>>> 2) Authenticate using organizational account.
>>>
>>>
>>>
>>> I have used the first method that is authenticating using a service
>>> principal.  A Service Principal is an instance of an application that is
>>> within your Active Directory that is allowed access to one or more
>>> resources or an entire resource group. How to set up a service principal is
>>> well described here [1]. Once you successfully set up a service principal,
>>> you will have the following information in hand.
>>>
>>>
>>>
>>> 1)  Client ID
>>>
>>> 2)  Client secret
>>>
>>> 3)  Tenant ID
>>>
>>> Above parameters and Azure subscription ID are used in the java app for
>>> authentication purpose. I have used Active Directory Authentication Library
>>> (ADAL) [2] for authentication. Once the authentication is successful, an
>>> authentication token will be issued and it will be used in the rest of the
>>> program as to make calls to API.
>>>
>>>
>>>
>>> *Getting information on ASNSG*
>>>
>>> For this purpose, [3] API reference is used. As the response we get a
>>> JSON string which includes names of NICs which are available in ASNSG.
>>>
>>>
>>>
>>> *Getting private IP address of each NIC*
>>>
>>> With the NIC names we received from previous API call, we can use this
>>> [4] API reference to get the private IP address of each NIC. And then with
>>> that information we can list out the IP addresses of all the VMs which has
>>> WSO2 Application Server running.
>>>
>>>
>>>
>>> [1]
>>> https://azure.microsoft.com/en-gb/documentation/articles/resource-group-create-service-principal-portal/
>>>
>>> [2] https://github.com/AzureAD/azure-activedirectory-library-for-java
>>>
>>> [3] https://msdn.microsoft.com/en-us/library/azure/mt163654.aspx
>>>
>>> [4] https://msdn.microsoft.com/en-us/library/azure/mt163611.aspx
>>>
>>>
>>>
>>> Thanks
>>>
>>>
>>>
>>> *From:* Imesh Gunaratne [mailto:im...@wso2.com]
>>> *Sent:* Saturday, May 28, 2016 8:53 AM
>>> *To:* Osura Rathnayake
>>> *Cc:* Isuru Haththotuwa; WSO2 Developers' List
>>> *Subject:* Re: [GSOC 16] Initial Project Progress
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Sat, May 28, 2016 at 12:42 AM, Osura Rathnayake 
>>> wrote:
>>>
>>> Hi mentors,
>>>
>>>
>>>
>>> Sorry for the late reply. ARM portal doesn't have certain features like
>>> Active Directory but it doesn't matter because they can be implemented
>>> using classic portal and they work hand in hand. So all the features in
>>> classic plus the new features in ARM can be used if we choose ARM model.
>>> Therefore I think it's fruitful if we stick to ARM model, and the other
>>> important thing is sooner or later Microsoft will develop the ARM fully so
>>> eventually classic model will be obsolete(I think).
>>>
>>>
>>>
>>> +1 We may need to go ahead with what they provide at the moment.
>>>
>>>
>>>
>>> As we discussed in our last hangout, using a main program I could list
>>> out the IP addresses of the VMs where Application Servers are installed.
>>> Please arrange another hangout so that we can discuss the next project goal.
>>>
>>>
>>>
>>> Yes will have a hangout 

[Dev] [Documentation] [DAS] This doc needs improvement

[Amila Maha Arachchi]

Doc and DAS teams,

Please go through the doc [1] and see whether a user can make use of it.
Doc is about analyzing real time stats using DAS. But the instructions ends
after publishing some sample stats to DAS and showing a useless log. Where
is the real time analytics part here???

I am totally lost. So, can you imagine the situation of a normal user?

[1]
https://docs.wso2.com/display/DAS301/Analyzing+Realtime+Service+Statistics

Regards,
Amila.

-- 
*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] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

Hi Osura,

These are great findings!

Can you please share the sample code that you wrote?

The next step would be to start writing the actual membership scheme.
Please refer the Kubernetes Membership scheme as a reference.

On Sat, May 28, 2016 at 9:06 PM, Osura Rathnayake 
wrote:

> Hi All,
>
>
>
> This is the summary of everything that I have done so far.
>
>
>
> Pre requisite: VMs which has WSO2 Application Server running should have
> been added to a particular network security group (NSG). In my case it’s
> ASNSG
>
>
>
> First the java app should be authenticated. Then it query for the
> information on ASNSG. Response of that API call includes names of all the
> network interfaces that are existed in ASNSG. Then each and every network
> interface is queried using their names to get private IP addresses of each
> of them. As the final outcome we get a list of IP addresses of VMs which
> has WSO2 Application Server running.
>
>
>
> *Authentication*
>
> In order to work with Azure Resource Manager (ARM) REST API, first of all
> our app has to be authenticated. ARM provides two methods for this purpose,
>
>
>
> 1) Authenticate using service principal
>
> 2) Authenticate using organizational account.
>
>
>
> I have used the first method that is authenticating using a service
> principal.  A Service Principal is an instance of an application that is
> within your Active Directory that is allowed access to one or more
> resources or an entire resource group. How to set up a service principal is
> well described here [1]. Once you successfully set up a service principal,
> you will have the following information in hand.
>
>
>
> 1)  Client ID
>
> 2)  Client secret
>
> 3)  Tenant ID
>
> Above parameters and Azure subscription ID are used in the java app for
> authentication purpose. I have used Active Directory Authentication Library
> (ADAL) [2] for authentication. Once the authentication is successful, an
> authentication token will be issued and it will be used in the rest of the
> program as to make calls to API.
>
>
>
> *Getting information on ASNSG*
>
> For this purpose, [3] API reference is used. As the response we get a JSON
> string which includes names of NICs which are available in ASNSG.
>
>
>
> *Getting private IP address of each NIC*
>
> With the NIC names we received from previous API call, we can use this [4]
> API reference to get the private IP address of each NIC. And then with that
> information we can list out the IP addresses of all the VMs which has WSO2
> Application Server running.
>
>
>
> [1]
> https://azure.microsoft.com/en-gb/documentation/articles/resource-group-create-service-principal-portal/
>
> [2] https://github.com/AzureAD/azure-activedirectory-library-for-java
>
> [3] https://msdn.microsoft.com/en-us/library/azure/mt163654.aspx
>
> [4] https://msdn.microsoft.com/en-us/library/azure/mt163611.aspx
>
>
>
> Thanks
>
>
>
> *From:* Imesh Gunaratne [mailto:im...@wso2.com]
> *Sent:* Saturday, May 28, 2016 8:53 AM
> *To:* Osura Rathnayake
> *Cc:* Isuru Haththotuwa; WSO2 Developers' List
> *Subject:* Re: [GSOC 16] Initial Project Progress
>
>
>
>
>
>
>
> On Sat, May 28, 2016 at 12:42 AM, Osura Rathnayake 
> wrote:
>
> Hi mentors,
>
>
>
> Sorry for the late reply. ARM portal doesn't have certain features like
> Active Directory but it doesn't matter because they can be implemented
> using classic portal and they work hand in hand. So all the features in
> classic plus the new features in ARM can be used if we choose ARM model.
> Therefore I think it's fruitful if we stick to ARM model, and the other
> important thing is sooner or later Microsoft will develop the ARM fully so
> eventually classic model will be obsolete(I think).
>
>
>
> +1 We may need to go ahead with what they provide at the moment.
>
>
>
> As we discussed in our last hangout, using a main program I could list out
> the IP addresses of the VMs where Application Servers are installed. Please
> arrange another hangout so that we can discuss the next project goal.
>
>
>
> Yes will have a hangout next week, it would be better if you can send
> details in a mail first.
>
>
>
> Thanks
>
>
>
>
>
>
>
> On Wed, May 25, 2016 at 9:08 PM, Osura Rathnayake 
> wrote:
>
> Hi Imesh,
>
>
>
> okay i will find out the differences and update you. meanwhile i will
> check azure sdk for java if it has all the classes we want.
>
>
>
> On Wed, May 25, 2016 at 9:31 AM, Imesh Gunaratne  wrote:
>
>
>
>
>
> On Tue, May 24, 2016 at 10:22 PM, Osura Rathnayake 
> wrote:
>
> Hi mentors,
>
>
>
> As you might already know, Azure has two deployment models , azure classic
> (old portal) and azure resource manager (ARM)(new portal). Unfortunately
> some functionalities of classic is not available in ARM vice versa[1] but
> microsoft is rapidly developing all the functionalities across both models.
> Also certain API references [2] are not available for both the models, for
> an example, for network both classic and ARM API references are avai

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

[Osura Rathnayake]

Hi All,



This is the summary of everything that I have done so far.



Pre requisite: VMs which has WSO2 Application Server running should have been 
added to a particular network security group (NSG). In my case it’s ASNSG



First the java app should be authenticated. Then it query for the information 
on ASNSG. Response of that API call includes names of all the network 
interfaces that are existed in ASNSG. Then each and every network interface is 
queried using their names to get private IP addresses of each of them. As the 
final outcome we get a list of IP addresses of VMs which has WSO2 Application 
Server running.



Authentication

In order to work with Azure Resource Manager (ARM) REST API, first of all our 
app has to be authenticated. ARM provides two methods for this purpose, 



1) Authenticate using service principal

2) Authenticate using organizational account.



I have used the first method that is authenticating using a service principal.  
A Service Principal is an instance of an application that is within your Active 
Directory that is allowed access to one or more resources or an entire resource 
group. How to set up a service principal is well described here [1]. Once you 
successfully set up a service principal, you will have the following 
information in hand.



1)  Client ID

2)  Client secret

3)  Tenant ID

Above parameters and Azure subscription ID are used in the java app for 
authentication purpose. I have used Active Directory Authentication Library 
(ADAL) [2] for authentication. Once the authentication is successful, an 
authentication token will be issued and it will be used in the rest of the 
program as to make calls to API.



Getting information on ASNSG

For this purpose, [3] API reference is used. As the response we get a JSON 
string which includes names of NICs which are available in ASNSG.



Getting private IP address of each NIC

With the NIC names we received from previous API call, we can use this [4] API 
reference to get the private IP address of each NIC. And then with that 
information we can list out the IP addresses of all the VMs which has WSO2 
Application Server running.



[1] 
https://azure.microsoft.com/en-gb/documentation/articles/resource-group-create-service-principal-portal/

[2] https://github.com/AzureAD/azure-activedirectory-library-for-java

[3] https://msdn.microsoft.com/en-us/library/azure/mt163654.aspx

[4] https://msdn.microsoft.com/en-us/library/azure/mt163611.aspx



Thanks



From: Imesh Gunaratne [mailto:im...@wso2.com]
Sent: Saturday, May 28, 2016 8:53 AM
To: Osura Rathnayake
Cc: Isuru Haththotuwa; WSO2 Developers' List
Subject: Re: [GSOC 16] Initial Project Progress







On Sat, May 28, 2016 at 12:42 AM, Osura Rathnayake mailto:osura...@gmail.com> > wrote:

Hi mentors,



Sorry for the late reply. ARM portal doesn't have certain features like Active 
Directory but it doesn't matter because they can be implemented using classic 
portal and they work hand in hand. So all the features in classic plus the new 
features in ARM can be used if we choose ARM model. Therefore I think it's 
fruitful if we stick to ARM model, and the other important thing is sooner or 
later Microsoft will develop the ARM fully so eventually classic model will be 
obsolete(I think).



+1 We may need to go ahead with what they provide at the moment.



As we discussed in our last hangout, using a main program I could list out the 
IP addresses of the VMs where Application Servers are installed. Please arrange 
another hangout so that we can discuss the next project goal.



Yes will have a hangout next week, it would be better if you can send details 
in a mail first.



Thanks







On Wed, May 25, 2016 at 9:08 PM, Osura Rathnayake mailto:osura...@gmail.com> > wrote:

Hi Imesh,



okay i will find out the differences and update you. meanwhile i will check 
azure sdk for java if it has all the classes we want.



On Wed, May 25, 2016 at 9:31 AM, Imesh Gunaratne mailto:im...@wso2.com> > wrote:





On Tue, May 24, 2016 at 10:22 PM, Osura Rathnayake mailto:osura...@gmail.com> > wrote:

Hi mentors,



As you might already know, Azure has two deployment models , azure classic (old 
portal) and azure resource manager (ARM)(new portal). Unfortunately some 
functionalities of classic is not available in ARM vice versa[1] but microsoft 
is rapidly developing all the functionalities across both models. Also certain 
API references [2] are not available for both the models, for an example, for 
network both classic and ARM API references are available but for network 
security groups only classic is available, while network security groups is a 
supported feature in ARM. shall we have a hangout to discuss this matter?



IMO it would be okay to stick to one model. Can you please research on this and 
list out the differences between two models? That would help us to take a 
decision on this.



Thanks



[1] 
https://blog.kloud.com.au/2016/04/05/a

Re: [Dev] [EMM]

[Tharindu Athukorala]

Hi Milan,
Thank you very much for the support. I will get back to you after trying
this. Thank you again

best regards

On Sat, May 28, 2016 at 8:44 PM, Milan Perera  wrote:

> Hi Tharindu,
>
> AFAIK, Android SDK does not have a specific API to encrypt files or
> derectories. However you'll be able to use native java cryptography
> APIs[1] to encrypt files and folder as suggested in [2].
>
> [1]
> https://docs.oracle.com/javase/8/docs/technotes/guides/security/crypto/CryptoSpec.html
> [2] http://stackoverflow.com/a/10275913
>
> Regards,
>
>
> On Saturday, 28 May 2016, Tharindu Athukorala <
> tharindu.athukor...@aiesec.net> wrote:
>
>> Hi Milan,
>> Thank you soo much for the reply. In our application we are trying find a
>> solution for COPE (Corporate Owned Personally Enabled) devices. We thought
>> to use SD cards and use that SD card to store corporate data and encrypt
>> that SD card. Is there any possibility to do that using  the android
>> encryption ?
>>
>> On Sat, May 28, 2016 at 8:12 PM, Milan Perera  wrote:
>>
>>> Hi Tharindu,
>>>
>>> In WSO2 EMM, we have used the native Android encryption capability via a
>>> device policy manager [1] in order to encrypt the storage (only includes
>>> the internal storage).
>>> Once you have given the device administration privilege to the
>>> application, you will be able to invoke this function[2] without any issue.
>>>
>>> However in [2], it is specifically stated that* it does not support
>>> external storage encryption*.
>>>
>>> [1]
>>> https://developer.android.com/reference/android/app/admin/DevicePolicyManager.htm
>>> [2]
>>> https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#setStorageEncryption%28android.content.ComponentName,%20boolean%29
>>>
>>> Regards,
>>>
>>> On Sat, May 28, 2016 at 2:07 PM, Tharindu Athukorala <
>>> tharindu.athukor...@aiesec.net> wrote:
>>>
 Hi all,
 I'm Tharindu from SLIIT an undergraduate of cyber security. I'm trying
 to encrypt and decrypt files from the SD card using AES 256 in android for
 the research work. In WSO2 EMM system you have used a wrapper concept and
 can anyone tell me how this wrapper concept works and what is the
 encryption mechanism you have used ?

 Thank you and best regards,

 --

 *Tharindu Athukorala*


 Contact me: Mobile: +94710848793

 Email: tharindu.athukor...@aiesec.net

 Skype: tharindu.athukorala



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


>>>
>>>
>>> --
>>> *Milan Perera *| Software Engineer
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>> Mobile: +94 77 309 7088 | Work: +94 11 214 5345
>>> Email: mi...@wso2.com | Web: www.wso2.com
>>> 
>>>
>>
>>
>>
>> --
>>
>> *Tharindu Athukorala*
>>
>>
>> Contact me: Mobile: +94710848793
>>
>> Email: tharindu.athukor...@aiesec.net
>>
>> Skype: tharindu.athukorala
>>
>>
>>
>
> --
> *Milan Perera *| Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 77 309 7088 | Work: +94 11 214 5345
> Email: mi...@wso2.com  | Web: www.wso2.com
> 
>
>


-- 

*Tharindu Athukorala*


Contact me: Mobile: +94710848793

Email: tharindu.athukor...@aiesec.net

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

Re: [Dev] Shindig error on DS portal startup, due to connectivity errors to google

[Fazlan Nazeem]

Sure will check.

On Sat, May 28, 2016 at 8:37 PM, Nirmal Fernando  wrote:

> Thanks Deep. @Fazlan please check.
>
> On Sat, May 28, 2016 at 1:22 AM, Deependra Ariyadewa 
> wrote:
>
>> This issue also exists in the  WSO2 API Manager Analytics  SNAPSHOT pack
>> [1]
>>
>> [1] Build WSO2 API Manager Analytics - Distribution (May 27, 2016 3:24:17
>> PM)
>>
>> On Fri, May 27, 2016 at 1:08 AM, Bhathiya Jayasekara 
>> wrote:
>>
>>> Thanks.
>>>
>>> On Fri, May 27, 2016 at 10:37 AM, Megala Uthayakumar 
>>> wrote:
>>>
 We will do a release tonight.

 Thanks

 On Fri, May 27, 2016 at 10:33 AM, Bhathiya Jayasekara <
 bhath...@wso2.com> wrote:

> We still have carbon dashboard 1.0.15 in APIM. Will upgrade. When are
> you planning to release this?
>
> Thanks,
> Bhathiya
>
> On Fri, May 27, 2016 at 10:31 AM, Bhathiya Jayasekara <
> bhath...@wso2.com> wrote:
>
>> +Ruwan
>>
>> On Fri, May 27, 2016 at 10:20 AM, Megala Uthayakumar > > wrote:
>>
>>> Hi,
>>> This fix is available in carbon-dashboards 1.0.17-SNAPSHOT. Is APIM
>>> 2.0.0 SNAPSHOT uses the same version?
>>>
>>> Thanks.
>>>
>>> On Fri, May 27, 2016 at 10:02 AM, Deependra Ariyadewa >> > wrote:
>>>
 This error still exists in the APIM 2.0.0 SNAPSHOT pack built on
 26th May 2016.

 On Thu, May 19, 2016 at 11:54 PM, Megala Uthayakumar <
 meg...@wso2.com> wrote:

> Hi,
>
> We have moved the fix for the google connectivity problem with the
> commit [1].
>
> [1]
> https://github.com/wso2/carbon-dashboards/commit/9e74ed2a788256cc429ffe35b6543c139d4c2ddb
>
> Thanks.
>
> Regards,
> Megala
>
> On Wed, May 18, 2016 at 12:52 PM, Sinthuja Ragendran <
> sinth...@wso2.com> wrote:
>
>> Hi Megala,
>>
>> Please check the shindig-server feature and try to remove the
>> unwanted files from there it self, hence we can omit this behaviour.
>>
>> Thanks,
>> Sinthuja.
>>
>> On Wed, May 18, 2016 at 12:13 PM, Ruwan Abeykoon > > wrote:
>>
>>> >>Can't we fix this during the shinding-server feature
>>> generation?
>>> +1
>>> So that every product using shindig does not have to unzip and
>>> zip the war file to fix it.
>>>
>>> Cheers,
>>> Ruwan
>>>
>>> On Wed, May 18, 2016 at 12:01 PM, Sinthuja Ragendran <
>>> sinth...@wso2.com> wrote:
>>>
 Hi Tanya,

 Can't we fix this during the shinding-server feature generation?

 Thanks,
 Sinthuja.

 On Wed, May 18, 2016 at 11:56 AM, Harsha Kumara <
 hars...@wso2.com> wrote:

> Adding Bhathiya.
>
> We got same exception yesterday in APIM as well. We will need
> to same thing for DS as well.
>
> Thanks,
> Harsha
>
> On Wed, May 18, 2016 at 11:38 AM, Ruwan Abeykoon <
> ruw...@wso2.com> wrote:
>
>> Thanks Tanya for the information. We will follow the same as
>> in DS.
>>
>> On Wed, May 18, 2016 at 11:34 AM, Tanya Madurapperuma <
>> ta...@wso2.com> wrote:
>>
>>> Hi Ruwan,
>>>
>>> Usually this error is thrown as shindig is trying to load
>>> some google analytics apis. So when there is no internet 
>>> connection this
>>> error can be observed.
>>> To get rid of this error we have to remove google related
>>> stuff from shindig features.txt file
>>>
>>> *features-extras/analytics/feature.xml*
>>> *features-extras/com.google.gadgets.analytics/feature.xml*
>>>
>>> But since we don't maintain a shindig fork, we can't do this
>>> from carbon-dashboards level. So in the Dashboard Server level 
>>> we are
>>> replacing the features.txt file with a file which doesn't have 
>>> above 2
>>> entries [1]. We'll have to do the same for apim analytics as 
>>> well.
>>>
>>> [1]
>>> https://github.com/wso2/product-ds/commit/2d763ce1d9f5362d559e9d46eb0bcedf1446ee9e
>>>
>>> Thanks,
>>> Tanya
>>>
>>> On Wed, May 18, 2016 at 11:16 AM, Ruwan Abeykoon <
>>> ruw...@wso2.com> wrote:
>>>
 Hi DS team,
 I am getting the following error in APIM 2.0.0-SNAPSHOT
 which integrate DS features. Any Idea why? can we no

Re: [Dev] [EMM]

[Milan Perera]

Hi Tharindu,

AFAIK, Android SDK does not have a specific API to encrypt files or
derectories. However you'll be able to use native java cryptography
APIs[1] to encrypt files and folder as suggested in [2].

[1]
https://docs.oracle.com/javase/8/docs/technotes/guides/security/crypto/CryptoSpec.html
[2] http://stackoverflow.com/a/10275913

Regards,

On Saturday, 28 May 2016, Tharindu Athukorala <
tharindu.athukor...@aiesec.net> wrote:

> Hi Milan,
> Thank you soo much for the reply. In our application we are trying find a
> solution for COPE (Corporate Owned Personally Enabled) devices. We thought
> to use SD cards and use that SD card to store corporate data and encrypt
> that SD card. Is there any possibility to do that using  the android
> encryption ?
>
> On Sat, May 28, 2016 at 8:12 PM, Milan Perera  > wrote:
>
>> Hi Tharindu,
>>
>> In WSO2 EMM, we have used the native Android encryption capability via a
>> device policy manager [1] in order to encrypt the storage (only includes
>> the internal storage).
>> Once you have given the device administration privilege to the
>> application, you will be able to invoke this function[2] without any issue.
>>
>> However in [2], it is specifically stated that* it does not support
>> external storage encryption*.
>>
>> [1]
>> https://developer.android.com/reference/android/app/admin/DevicePolicyManager.htm
>> [2]
>> https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#setStorageEncryption%28android.content.ComponentName,%20boolean%29
>>
>> Regards,
>>
>> On Sat, May 28, 2016 at 2:07 PM, Tharindu Athukorala <
>> tharindu.athukor...@aiesec.net
>> > wrote:
>>
>>> Hi all,
>>> I'm Tharindu from SLIIT an undergraduate of cyber security. I'm trying
>>> to encrypt and decrypt files from the SD card using AES 256 in android for
>>> the research work. In WSO2 EMM system you have used a wrapper concept and
>>> can anyone tell me how this wrapper concept works and what is the
>>> encryption mechanism you have used ?
>>>
>>> Thank you and best regards,
>>>
>>> --
>>>
>>> *Tharindu Athukorala*
>>>
>>>
>>> Contact me: Mobile: +94710848793
>>>
>>> Email: tharindu.athukor...@aiesec.net
>>>
>>> Skype: tharindu.athukorala
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org 
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Milan Perera *| Software Engineer
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> Mobile: +94 77 309 7088 | Work: +94 11 214 5345
>> Email: mi...@wso2.com 
>>  | Web: www.wso2.com
>> 
>>
>
>
>
> --
>
> *Tharindu Athukorala*
>
>
> Contact me: Mobile: +94710848793
>
> Email: tharindu.athukor...@aiesec.net
>
> Skype: tharindu.athukorala
>
>
>

-- 
*Milan Perera *| Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 77 309 7088 | Work: +94 11 214 5345
Email: mi...@wso2.com  | Web: www.wso2.com

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

Re: [Dev] Shindig error on DS portal startup, due to connectivity errors to google

[Nirmal Fernando]

Thanks Deep. @Fazlan please check.

On Sat, May 28, 2016 at 1:22 AM, Deependra Ariyadewa  wrote:

> This issue also exists in the  WSO2 API Manager Analytics  SNAPSHOT pack
> [1]
>
> [1] Build WSO2 API Manager Analytics - Distribution (May 27, 2016 3:24:17
> PM)
>
> On Fri, May 27, 2016 at 1:08 AM, Bhathiya Jayasekara 
> wrote:
>
>> Thanks.
>>
>> On Fri, May 27, 2016 at 10:37 AM, Megala Uthayakumar 
>> wrote:
>>
>>> We will do a release tonight.
>>>
>>> Thanks
>>>
>>> On Fri, May 27, 2016 at 10:33 AM, Bhathiya Jayasekara >> > wrote:
>>>
 We still have carbon dashboard 1.0.15 in APIM. Will upgrade. When are
 you planning to release this?

 Thanks,
 Bhathiya

 On Fri, May 27, 2016 at 10:31 AM, Bhathiya Jayasekara <
 bhath...@wso2.com> wrote:

> +Ruwan
>
> On Fri, May 27, 2016 at 10:20 AM, Megala Uthayakumar 
> wrote:
>
>> Hi,
>> This fix is available in carbon-dashboards 1.0.17-SNAPSHOT. Is APIM
>> 2.0.0 SNAPSHOT uses the same version?
>>
>> Thanks.
>>
>> On Fri, May 27, 2016 at 10:02 AM, Deependra Ariyadewa 
>> wrote:
>>
>>> This error still exists in the APIM 2.0.0 SNAPSHOT pack built on
>>> 26th May 2016.
>>>
>>> On Thu, May 19, 2016 at 11:54 PM, Megala Uthayakumar <
>>> meg...@wso2.com> wrote:
>>>
 Hi,

 We have moved the fix for the google connectivity problem with the
 commit [1].

 [1]
 https://github.com/wso2/carbon-dashboards/commit/9e74ed2a788256cc429ffe35b6543c139d4c2ddb

 Thanks.

 Regards,
 Megala

 On Wed, May 18, 2016 at 12:52 PM, Sinthuja Ragendran <
 sinth...@wso2.com> wrote:

> Hi Megala,
>
> Please check the shindig-server feature and try to remove the
> unwanted files from there it self, hence we can omit this behaviour.
>
> Thanks,
> Sinthuja.
>
> On Wed, May 18, 2016 at 12:13 PM, Ruwan Abeykoon 
> wrote:
>
>> >>Can't we fix this during the shinding-server feature
>> generation?
>> +1
>> So that every product using shindig does not have to unzip and
>> zip the war file to fix it.
>>
>> Cheers,
>> Ruwan
>>
>> On Wed, May 18, 2016 at 12:01 PM, Sinthuja Ragendran <
>> sinth...@wso2.com> wrote:
>>
>>> Hi Tanya,
>>>
>>> Can't we fix this during the shinding-server feature generation?
>>>
>>> Thanks,
>>> Sinthuja.
>>>
>>> On Wed, May 18, 2016 at 11:56 AM, Harsha Kumara <
>>> hars...@wso2.com> wrote:
>>>
 Adding Bhathiya.

 We got same exception yesterday in APIM as well. We will need
 to same thing for DS as well.

 Thanks,
 Harsha

 On Wed, May 18, 2016 at 11:38 AM, Ruwan Abeykoon <
 ruw...@wso2.com> wrote:

> Thanks Tanya for the information. We will follow the same as
> in DS.
>
> On Wed, May 18, 2016 at 11:34 AM, Tanya Madurapperuma <
> ta...@wso2.com> wrote:
>
>> Hi Ruwan,
>>
>> Usually this error is thrown as shindig is trying to load
>> some google analytics apis. So when there is no internet 
>> connection this
>> error can be observed.
>> To get rid of this error we have to remove google related
>> stuff from shindig features.txt file
>>
>> *features-extras/analytics/feature.xml*
>> *features-extras/com.google.gadgets.analytics/feature.xml*
>>
>> But since we don't maintain a shindig fork, we can't do this
>> from carbon-dashboards level. So in the Dashboard Server level 
>> we are
>> replacing the features.txt file with a file which doesn't have 
>> above 2
>> entries [1]. We'll have to do the same for apim analytics as 
>> well.
>>
>> [1]
>> https://github.com/wso2/product-ds/commit/2d763ce1d9f5362d559e9d46eb0bcedf1446ee9e
>>
>> Thanks,
>> Tanya
>>
>> On Wed, May 18, 2016 at 11:16 AM, Ruwan Abeykoon <
>> ruw...@wso2.com> wrote:
>>
>>> Hi DS team,
>>> I am getting the following error in APIM 2.0.0-SNAPSHOT
>>> which integrate DS features. Any Idea why? can we not print 
>>> those errors
>>> due to outside dependencies?
>>>
>>> ---
>>>
>>> achines/jdk1.8.0_31.jdk/Contents/Home/jre/lib/libinstrument.dylib.
>>> One of the two

Re: [Dev] [EMM]

[Tharindu Athukorala]

Hi Milan,
Thank you soo much for the reply. In our application we are trying find a
solution for COPE (Corporate Owned Personally Enabled) devices. We thought
to use SD cards and use that SD card to store corporate data and encrypt
that SD card. Is there any possibility to do that using  the android
encryption ?

On Sat, May 28, 2016 at 8:12 PM, Milan Perera  wrote:

> Hi Tharindu,
>
> In WSO2 EMM, we have used the native Android encryption capability via a
> device policy manager [1] in order to encrypt the storage (only includes
> the internal storage).
> Once you have given the device administration privilege to the
> application, you will be able to invoke this function[2] without any issue.
>
> However in [2], it is specifically stated that* it does not support
> external storage encryption*.
>
> [1]
> https://developer.android.com/reference/android/app/admin/DevicePolicyManager.htm
> [2]
> https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#setStorageEncryption%28android.content.ComponentName,%20boolean%29
>
> Regards,
>
> On Sat, May 28, 2016 at 2:07 PM, Tharindu Athukorala <
> tharindu.athukor...@aiesec.net> wrote:
>
>> Hi all,
>> I'm Tharindu from SLIIT an undergraduate of cyber security. I'm trying to
>> encrypt and decrypt files from the SD card using AES 256 in android for the
>> research work. In WSO2 EMM system you have used a wrapper concept and can
>> anyone tell me how this wrapper concept works and what is the encryption
>> mechanism you have used ?
>>
>> Thank you and best regards,
>>
>> --
>>
>> *Tharindu Athukorala*
>>
>>
>> Contact me: Mobile: +94710848793
>>
>> Email: tharindu.athukor...@aiesec.net
>>
>> Skype: tharindu.athukorala
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Milan Perera *| Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 77 309 7088 | Work: +94 11 214 5345
> Email: mi...@wso2.com  | Web: www.wso2.com
> 
>



-- 

*Tharindu Athukorala*


Contact me: Mobile: +94710848793

Email: tharindu.athukor...@aiesec.net

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

Re: [Dev] [EMM]

[Milan Perera]

Hi Tharindu,

In WSO2 EMM, we have used the native Android encryption capability via a
device policy manager [1] in order to encrypt the storage (only includes
the internal storage).
Once you have given the device administration privilege to the application,
you will be able to invoke this function[2] without any issue.

However in [2], it is specifically stated that* it does not support
external storage encryption*.

[1]
https://developer.android.com/reference/android/app/admin/DevicePolicyManager.htm
[2]
https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#setStorageEncryption%28android.content.ComponentName,%20boolean%29

Regards,

On Sat, May 28, 2016 at 2:07 PM, Tharindu Athukorala <
tharindu.athukor...@aiesec.net> wrote:

> Hi all,
> I'm Tharindu from SLIIT an undergraduate of cyber security. I'm trying to
> encrypt and decrypt files from the SD card using AES 256 in android for the
> research work. In WSO2 EMM system you have used a wrapper concept and can
> anyone tell me how this wrapper concept works and what is the encryption
> mechanism you have used ?
>
> Thank you and best regards,
>
> --
>
> *Tharindu Athukorala*
>
>
> Contact me: Mobile: +94710848793
>
> Email: tharindu.athukor...@aiesec.net
>
> Skype: tharindu.athukorala
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Milan Perera *| Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 77 309 7088 | Work: +94 11 214 5345
Email: mi...@wso2.com  | Web: www.wso2.com

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

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

[Jasintha Dasanayake]

Hi All

Actually the original issue is , ESB 5.0.0 server cannot start in Developer
Studio with carbon server 4.4 in DevS 3.8.0 as well as 4.1.0 ( this was
reported by several  people) , I also able to reproduce this issue with
DevS 3.8.0 and ESB 5.0.0 Alpa , I am getting the following error in DevS
 console when server is starting

"Invalid initial heap size: -XmsMEM_OPTS=-Xms256m -Xmx1024m

Error: Could not create the Java Virtual Machine.

Error: A fatal exception has occurred. Program will exit.
"
I debug the code and found the root cause for this error ,

  VM parameters has been defined in the carbon.definition.xml [1] as follows


org.wso2.carbon.bootstrap.Bootstrap
${carbon.home}
-Xms256m -Xmx1024m -XX:MaxPermSize=256m
-XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath="${carbon.home}/repository/logs/heap-dump.hprof"
-Dcom.sun.management.jmxremote
-Djava.endorsed.dirs="${carbon.home}/lib/endorsed"
-Djava.io.tmpdir="${carbon.home}/tmp"
-Dcatalina.base="${carbon.home}/lib/tomcat" -Dwso2.server.standalone=true
-Dcarbon.registry.root=/ -Dcarbon.home="${carbon.home}"
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Dcarbon.config.dir.path="${carbon.home}/repository/conf"
-Djava.util.logging.config.file="${carbon.home}/repository/conf/etc/logging-bridge.properties"
-Dcomponents.repo="${carbon.home}/repository/components/plugins"
-Dconf.location="${carbon.home}/repository/conf"
-Dcom.atomikos.icatch.file="${carbon.home}/lib/transactions.properties"
-Dcom.atomikos.icatch.hide_init_file_path=true
-Dorg.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=false
-Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
-Dcom.sun.jndi.ldap.connect.pool.authentication=simple
-Dcom.sun.jndi.ldap.connect.pool.timeout=3000
-Dorg.terracotta.quartz.skipUpdateCheck=true
-Djava.security.egd=file:/dev/./urandom -Dfile.encoding=UTF8
-Djava.net.preferIPv4Stack=true -Dcom.ibm.cacheLocalHost=true
-DworkerNode=false

carbon.libs
${carbon.debug}



There is a class called "CarbonServerScriptParser"[2] , it has been used to
read the server startup sh line by line and try to figure out  the these  -Xms
-Xmx -XX:MaxPermSize  three values from server sh , it has the  following
logic to find out these values

FileReader fileReader = new FileReader(scriptFile);

BufferedReader reader = new BufferedReader(fileReader);


 String line = reader.readLine();

  while (line != null) {

if (line.contains(MIN_MEMORY_STRING)) {

String[] array = line.split(" ");

for (String string : array) {

if (string.contains(MIN_MEMORY_STRING)) {

vmParams.put(MIN_MEMORY_STRING,string.trim().substring(MIN_MEMORY_STRING
.length()));

}

}

  }

According to above logic it's read line by line and use "string.contains(
MIN_MEMORY_STRING)" method to match and find above VM argument values.
Above Min Memory VM augment  is defined in the ESB 5.0.0 server startup
file in the following way

JVM_MEM_OPTS="-Xms256m -Xmx1024m"

so when pass this line result will be "MEM_OPTS="-Xms256m"  , then original
VM param value  which is define in the carbon.definition.xml file, will be
overwritten using this value , (this is happening in there server imple
class[3] ( method  getVmArguments()) As a result of this above exception is
printed to the console

However IMO what we are trying to do here is not necessary, because eclipse
has a built in UI to configure these VM arguments before the server start,
so we shouldn't need to get it from server startup script , if a user want
to change those default values users can easily configure it using eclipse
it self  furthermore  we have done this for port configuration similar we
can do it for VM arguments configuration

Thanks and Regards
/Jasintha


[1] -
https://github.com/wso2/developer-studio/blob/developer-studio-3.8.0/server/org.wso2.developerstudio.eclipse.carbonserver44/serverdefinition/carbon.definition.xml

[2]-
https://github.com/wso2/developer-studio/blob/developer-studio-3.8.0/server/org.wso2.developerstudio.eclipse.carbonserver.base/src/org/wso2/developerstudio/eclipse/carbonserver/base/utils/CarbonServerScriptParser.java

[3]-
https://github.com/wso2/developer-studio/blob/developer-studio-3.8.0/server/org.wso2.developerstudio.eclipse.carbonserver.base/src/org/wso2/developerstudio/eclipse/carbonserver/base/impl/CarbonServerBehaviour.java



On Sat, May 28, 2016 at 7:26 AM, Awanthika Senarath 
wrote:

> Thanks Susankha,
>
> [+ Kavith]
>
> Will have a look at this,
>
>
>
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>
> On Sat, May 28, 2016 at 4:31 AM, Susankha Nirmala 
> wrote:
>
>>
>>
>> On Fri, May 27, 2016 at 4:01 PM, Susankha Nirmala 
>> wrote:
>>
>>> I was able to start ESB 5.0.0 using DevStudio 3.8.0 (with carbonserver
>>> 4.4) with Java 1.7 and 1.8. Because, as I explained, in the DevS 3.8 we are
>>> passing "-Xms256m -Xmx1024m -XX:MaxPermSize=256m" VM parameters(refer [1]).
>>> Attached the screenshots to the mail.
>>>
>>>  @ Awanthika,
>>>
>>> You can pass 

[Dev] [EMM]

[Tharindu Athukorala]

Hi all,
I'm Tharindu from SLIIT an undergraduate of cyber security. I'm trying to
encrypt and decrypt files from the SD card using AES 256 in android for the
research work. In WSO2 EMM system you have used a wrapper concept and can
anyone tell me how this wrapper concept works and what is the encryption
mechanism you have used ?

Thank you and best regards,

-- 

*Tharindu Athukorala*


Contact me: Mobile: +94710848793

Email: tharindu.athukor...@aiesec.net

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