Re: [Dev] Error : java.lang.NoClassDefFoundError: org/testng/IAlterSuiteListener when upgrading the carbon versions

[Kamidu Punchihewa]

Hi Ruwan,

Thanks you very much for the suggestion. Got the issue sorted by excluding
the duplicate dependancies.

Thanks and Best Regards,

On Fri, Mar 9, 2018 at 8:44 PM, Ruwan Abeykoon <ruw...@wso2.com> wrote:

> Hi Kamidu,
> Seem like some dependency jar has transitive dependency to testng, which
> should not.
>
> Please check if any testng is reported in follwing command.
>
> mvn dependency:tree
>
> On Fri, Mar 9, 2018 at 6:00 PM, Kamidu Punchihewa <sachi...@wso2.com>
> wrote:
>
>> Hi Devs,
>>
>> I am in the process of updating the following carbon dependency versions
>> on carbon appmgt component,
>>
>>- carbon-kernel version to 4.4.24
>>- carbon-commons version to 4.6.21
>>- carbon-identity version to 5.11.120
>>- identity-inbound-auth-oauth version to 5.6.51
>>- carbon-multitenancy version to 4.6.8
>>- carbon-registry version to 4.6.28
>>- carbon-apimgt versiob to 6.2.146
>>
>> When the new versions are applied successfully. The following error
>> occurred while building the component,
>>
>> [ERROR] Failed to execute goal 
>> org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>> (default-test) on project org.wso2.carbon.appmgt.hostobjects: Execution
>> default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test
>> failed: There was an error in the forked process
>>
>> [ERROR] java.lang.NoClassDefFoundError: org/testng/IAlterSuiteListener
>>
>> [ERROR] at java.lang.ClassLoader.defineClass1(Native Method)
>>
>> [ERROR] at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
>>
>> [ERROR] at java.security.SecureClassLoader.defineClass(SecureClassLoade
>> r.java:142)
>>
>> [ERROR] at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
>>
>> [ERROR] at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
>>
>> [ERROR] at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
>>
>> [ERROR] at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
>>
>> [ERROR] at java.security.AccessController.doPrivileged(Native Method)
>>
>> [ERROR] at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
>>
>> [ERROR] at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>>
>> [ERROR] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
>>
>> [ERROR] at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>>
>> [ERROR] at java.lang.Class.forName0(Native Method)
>>
>> [ERROR] at java.lang.Class.forName(Class.java:348)
>>
>> [ERROR] at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoad
>> er.java:370)
>>
>> [ERROR] at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.
>> java:404)
>>
>> [ERROR] at java.util.ServiceLoader$1.next(ServiceLoader.java:480)
>>
>> [ERROR] at org.testng.TestNG.addServiceLoaderListeners(TestNG.java:899)
>>
>> [ERROR] at org.testng.TestNG.initializeConfiguration(TestNG.java:834)
>>
>> [ERROR] at org.testng.TestNG.run(TestNG.java:948)
>>
>> [ERROR] at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGEx
>> ecutor.java:115)
>>
>> [ERROR] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.ex
>> ecuteMulti(TestNGDirectoryTestSuite.java:205)
>>
>> [ERROR] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.ex
>> ecute(TestNGDirectoryTestSuite.java:108)
>>
>> [ERROR] at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestN
>> GProvider.java:111)
>>
>> [ERROR] at org.apache.maven.surefire.booter.ForkedBooter.invokeProvider
>> InSameClassLoader(ForkedBooter.java:203)
>>
>> [ERROR] at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInPro
>> cess(ForkedBooter.java:155)
>>
>> [ERROR] at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBoo
>> ter.java:103)
>>
>> [ERROR] Caused by: java.lang.ClassNotFoundException:
>> org.testng.IAlterSuiteListener
>>
>> [ERROR] at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>>
>> [ERROR] at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>>
>> [ERROR] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
>>
>> [ERROR] at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>>
>> [ERROR] ... 27 more
>>
>> [ERROR] -> [Help 1]
>>
>> Any idea what can cause this issue and what steps can be taken to resolve
>> this issue?
>> Your inputs in this manner is much appreciated.
>>
>> Thanks and Best Regards,

[Dev] Error : java.lang.NoClassDefFoundError: org/testng/IAlterSuiteListener when upgrading the carbon versions

[Kamidu Punchihewa]

Hi Devs,

I am in the process of updating the following carbon dependency versions on
carbon appmgt component,

   - carbon-kernel version to 4.4.24
   - carbon-commons version to 4.6.21
   - carbon-identity version to 5.11.120
   - identity-inbound-auth-oauth version to 5.6.51
   - carbon-multitenancy version to 4.6.8
   - carbon-registry version to 4.6.28
   - carbon-apimgt versiob to 6.2.146

When the new versions are applied successfully. The following error
occurred while building the component,

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
project org.wso2.carbon.appmgt.hostobjects: Execution default-test of goal
org.apache.maven.plugins:maven-surefire-plugin:2.18:test failed: There was
an error in the forked process

[ERROR] java.lang.NoClassDefFoundError: org/testng/IAlterSuiteListener

[ERROR] at java.lang.ClassLoader.defineClass1(Native Method)

[ERROR] at java.lang.ClassLoader.defineClass(ClassLoader.java:763)

[ERROR] at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)

[ERROR] at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)

[ERROR] at java.net.URLClassLoader.access$100(URLClassLoader.java:73)

[ERROR] at java.net.URLClassLoader$1.run(URLClassLoader.java:368)

[ERROR] at java.net.URLClassLoader$1.run(URLClassLoader.java:362)

[ERROR] at java.security.AccessController.doPrivileged(Native Method)

[ERROR] at java.net.URLClassLoader.findClass(URLClassLoader.java:361)

[ERROR] at java.lang.ClassLoader.loadClass(ClassLoader.java:424)

[ERROR] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)

[ERROR] at java.lang.ClassLoader.loadClass(ClassLoader.java:357)

[ERROR] at java.lang.Class.forName0(Native Method)

[ERROR] at java.lang.Class.forName(Class.java:348)

[ERROR] at
java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:370)

[ERROR] at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404)

[ERROR] at java.util.ServiceLoader$1.next(ServiceLoader.java:480)

[ERROR] at org.testng.TestNG.addServiceLoaderListeners(TestNG.java:899)

[ERROR] at org.testng.TestNG.initializeConfiguration(TestNG.java:834)

[ERROR] at org.testng.TestNG.run(TestNG.java:948)

[ERROR] at
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115)

[ERROR] at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:205)

[ERROR] at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:108)

[ERROR] at
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:111)

[ERROR] at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)

[ERROR] at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)

[ERROR] at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)

[ERROR] Caused by: java.lang.ClassNotFoundException:
org.testng.IAlterSuiteListener

[ERROR] at java.net.URLClassLoader.findClass(URLClassLoader.java:381)

[ERROR] at java.lang.ClassLoader.loadClass(ClassLoader.java:424)

[ERROR] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)

[ERROR] at java.lang.ClassLoader.loadClass(ClassLoader.java:357)

[ERROR] ... 27 more

[ERROR] -> [Help 1]

Any idea what can cause this issue and what steps can be taken to resolve
this issue?
Your inputs in this manner is much appreciated.

Thanks and Best Regards,

-- 
Kamidu Sachith Punchihewa
*Senior Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>

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,
retransmit, 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] [Architecture] [VOTE] Release WSO2 IoT Server 3.2.0 RC2

[Kamidu Punchihewa]

Hi all,

I have tested following functionalities on a single node deplyment:

   - Enrolled an android device and perform operations in BYOD mode.
   - Enrolled an iOS device and perform operations.
   - Check the notifications and notification removal and mark as read
   functionalities.
   - Create and publish iOS and Android restriction policies.

[+1] Stable - Go ahead and release

Thanks and Best Regards,



On Tue, Feb 27, 2018 at 1:24 PM, Madhawa Perera  wrote:

> Hi all,
>
> I have tested following functionalities:
>
> 1. Android device enrolment and dis-enrollment
> 2. Android device operation and policy as admin user:
> - Device Lock
> - Change Lock Code
> - Ring
> - Location
> - Camera restriction policy
> 3. iOS device enrollment and dis-enrollment
> 4. iOS device operation and policy as admin user:
> - Ring
> - Notification
> - Camera restriction policy
>
> Found no issues.
>
> +1 Stable - go ahead and release.
>
> Thank you
> Best Regards,
> Madhawa
>
> On Tue, Feb 27, 2018 at 6:37 AM, Charitha Goonetilleke  > wrote:
>
>> Hi All,
>>
>> Successfully tested the following :
>>
>>1. Add API based device type with MQTT transport.
>>2. Enroll and communicate with the agent.
>>3. Renewed token using refresh token grant type.
>>4. Send operation to agent and receive operation response.
>>5. Publish operation response to analytics
>>
>> [+] Stable - Go ahead and release
>>
>> Thanks & regards,
>> /charithag
>>
>> On Tue, Feb 27, 2018 at 10:18 AM, Nuwan Jayawardene 
>> wrote:
>>
>>> Successfully tested the following :
>>>
>>>
>>>1. Android BYOD Device enrollment
>>>2. Invoked following operations: Ring, Device Lock, Location, Mute,
>>>Change Lock code, Enterprise wipe, Wipe data
>>>3. Passcode policy for BYOD
>>>4. Restriction policy for BYOD
>>>
>>> I am +1 for this release
>>>
>>>
>>> Thanks and regards
>>>
>>>
>>> On Tue, Feb 27, 2018 at 7:08 AM, Ruwan Yatawara  wrote:
>>>
 Successfully tested the following :

 1. Android Device Enrollment
 2  Invoking Ring, Message, Location Operation
 3. Configuring Geo Alerts
 3. Adding Stationary, Exit and Entry Alerts
 4. Adding a new Device Type

 I am +1 to release.


 Thanks and Regards,

 Ruwan Yatawara

 Technical Lead,
 WSO2 Inc.

 email : ruw...@wso2.com
 mobile : +94 77 9110413
 http://ruwansrants.blogspot.com/
 https://500px.com/ruwan_ace
 https://medium.com/@ruwanyatawara


 On Mon, Feb 26, 2018 at 2:17 AM, Rasika Perera 
 wrote:

> Hi Devs,
>
> We are pleased to announce the release candidate of WSO2 IoT Server 3
> .2.0.
>
> This is the second release candidate (RC) of the WSO2 IoT Server 3.2.0
> release.
>
> This release carries 275+ issue fixes [1-12] over the last GA (3.1.0)
> release.
>
> Reported Issues:
>
>- https://github.com/wso2/product-iots/issues
>
> Source and distribution packages:
>
>- https://github.com/wso2/product-iots/releases/tag/v3.2.0-RC2
>
> Tag to be voted upon:
>
>- https://github.com/wso2/product-iots/releases/tag/v3.2.0-RC2
>
> Please download, test, and vote. The README file under the
> distribution contains guide and instructions on how to try it out locally.
>
> [+] Stable - Go ahead and release
> [-] Broken - Do not release (explain why)
>
> [1] https://github.com/wso2/product-iots/milestone/3?closed=1
> [2] https://github.com/wso2/product-iots/milestone/4?closed=1
> [3] https://github.com/wso2/product-iots/milestone/5?closed=1
> [4] https://github.com/wso2/product-iots/milestone/6?closed=1
> [5] https://github.com/wso2/product-iots/milestone/7?closed=1
> [6] https://github.com/wso2/product-iots/milestone/11?closed=1
> [7] https://github.com/wso2/product-iots/milestone/12?closed=1
> [8] https://github.com/wso2/product-iots/milestone/13?closed=1
> [9] https://github.com/wso2/product-iots/milestone/14?closed=1
> [10] https://github.com/wso2/product-iots/milestone/18?closed=1
> [11] https://github.com/wso2/product-iots/milestone/19?closed=1
> [12] https://github.com/wso2/product-iots/milestone/20?closed=1
>
> Regards,
> The WSO2 IoT Team.
>
> --
> With Regards,
>
> *Rasika Perera*
> Senior Software Engineer
> LinkedIn: http://lk.linkedin.com/in/rasika90
>
> 
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>


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


>>>
>>>
>>> --
>>> *Nuwan Jayawardene*
>>> *Software Engineering intern*
>>> *WSO2, 

Re: [Dev] [VOTE] Release WSO2 IoT Server 3.2.0 RC1

[Kamidu Punchihewa]

I have tested and verified the following on a MacBookPro without any load
balancers using a self singed SSL certificate :

Created a user and role
Enrolled an Android device
Create and publish an Android policy
Applied the following operations to the enrolled device,

   - Send Notification
   - Location
   - Ring
   - Clear Passcode
   - Enterprise Wipe
   - Device Lock
   - Wipe Data

Check the Geo Dashboard and the UI for information and verify the received
information.
Test the re-enrollment process of the same device with another user.
Test and verify the Group Management.
Test and verify the Role and Permission Management.
Test and verify the Certificate Management.

No issues found.
[x] Stable - go ahead and release

Regards,
Inosh


On Mon, Feb 5, 2018 at 12:49 PM, Inosh Perera  wrote:

> Tested and verified the following:
>
> Created a user and role
> Enrolled an iOS device
>
> Applied the following operations and policies,
> Send Notification
> Location
> Ring
> Clear Passcode
> Enterprise Wipe
> Device Lock
> Wipe Data
> Verify Location information in UI againt the device location
> Verify device information in UI againt the device
> Verify app list
> Passcode Policy
> Restrictions
> WiFi Settings
> Email Settings
> AirPlay Settings
> LDAP Setting
> Calendar
> Calendar Subscritption
> Cellular Network Settings
> VPN
> Manage Domains
>
> No issues found.
> [x] Stable - go ahead and release
>
> Regards,
> Inosh
>
>
>
> On Tue, Jan 30, 2018 at 11:52 AM, Rasika Perera  wrote:
>
>> Hi Devs,
>>
>> We are pleased to announce the release candidate of WSO2 IoT Server 3.2.0
>> .
>>
>> This is the first release candidate (RC) of the WSO2 IoT Server 3.2.0
>> release.
>>
>> This release carries 275 issue fixes [1-12] over the last GA (3.1.0)
>> release.
>>
>> Reported Issues:
>>
>>- https://github.com/wso2/product-iots/issues
>>
>> Source and distribution packages:
>>
>>- https://github.com/wso2/product-iots/releases/tag/v3.2.0-RC1
>>
>> Tag to be voted upon:
>>
>>- https://github.com/wso2/product-iots/releases/tag/v3.2.0-RC1
>>
>> Please download, test, and vote. The README file under the distribution
>> contains guide and instructions on how to try it out locally.
>>
>> [+] Stable - Go ahead and release
>> [-] Broken - Do not release (explain why)
>>
>> This vote will be open for 72 hours or as needed.
>>
>> [1] https://github.com/wso2/product-iots/milestone/3?closed=1
>> [2] https://github.com/wso2/product-iots/milestone/4?closed=1
>> [3] https://github.com/wso2/product-iots/milestone/5?closed=1
>> [4] https://github.com/wso2/product-iots/milestone/6?closed=1
>> [5] https://github.com/wso2/product-iots/milestone/7?closed=1
>> [6] https://github.com/wso2/product-iots/milestone/11?closed=1
>> [7] https://github.com/wso2/product-iots/milestone/12?closed=1
>> [8] https://github.com/wso2/product-iots/milestone/13?closed=1
>> [9] https://github.com/wso2/product-iots/milestone/14?closed=1
>> [10] https://github.com/wso2/product-iots/milestone/18?closed=1
>> [11] https://github.com/wso2/product-iots/milestone/19?closed=1
>> [12] https://github.com/wso2/product-iots/milestone/20?closed=1
>>
>> Regards,
>> The WSO2 IoT Team.
>>
>> --
>> With Regards,
>>
>> *Rasika Perera*
>> Senior Software Engineer
>> LinkedIn: http://lk.linkedin.com/in/rasika90
>>
>> 
>>
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>>
>
>
>
> --
> Inosh Perera
> Senior Software Engineer, WSO2 Inc.
> Tel: 077813 7285, 0785293686
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Kamidu Sachith Punchihewa
*Senior Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>

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,
retransmit, 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] Bug when selecting all in policy management window of IOT 3.1.0/update ll

[Kamidu Punchihewa]

Hi Inosh,

Current policy API support publishing and unpublishing multiple policies at
ones hence this is a UI bug we need to address.

Thanks and Best Regards,


On Wed, Jan 24, 2018 at 10:44 AM, Rasika Perera  wrote:

> Hi Lasahan,
>
> This is a bug. Please report and create a git issue in [1] to track this.
>
> [1] https://github.com/wso2/product-iots/issues
>
> On Wed, Jan 24, 2018 at 9:48 AM, Inosh Perera  wrote:
>
>> Hi Lashan,
>>
>> This seems to me like a bug.
>> @Geeth, is there any limitation of policy APIs when it comes to
>> unpublishing multiple policies at once?
>>
>> Regards,
>> Inosh
>>
>> On Wed, Jan 24, 2018 at 9:26 AM, Lashan Faliq  wrote:
>>
>>> If you click select and then chose a policy you get the following
>>> options.
>>>
>>>
>>> But if you click select and then select all those buttons don’t appear
>>> initially. They appear when you click on a policy once after choosing
>>> select all.
>>>
>>>
>>> Is this the expected behavior?
>>> --
>>> *Lashan Faliq*
>>> Software Engineering Intern
>>>
>>> Email : lash...@wso2.com
>>> Mobile : +94776382757 <+94%2077%20638%202757>
>>> web : http://wso2.com
>>>
>>> [image: https://wso2.com/signature] 
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "WSO2 IoT Team Group" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to iot-group+unsubscr...@wso2.com.
>>> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>>>
>>
>>
>>
>> --
>> Inosh Perera
>> Senior Software Engineer, WSO2 Inc.
>> Tel: 077813 7285, 0785293686
>>
>
>
>
> --
> With Regards,
>
> *Rasika Perera*
> Senior Software Engineer
> LinkedIn: http://lk.linkedin.com/in/rasika90
>
> 
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Kamidu Sachith Punchihewa
*Senior Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>

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,
retransmit, 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] [IoT] Changing Geo Location Enabling Configuration

[Kamidu Punchihewa]

Hi Rasika,

+ 1 for filter out required operations responses that the user needs to get
the related analytics. IMO this will improve the UX even better than just
allowing or disallowing all the operation whether the information is needed
to the user or not.
@Charitha, good suggestion on configurations.

Thanks and Best Regards,

On Mon, Jan 22, 2018 at 1:37 PM, Rasika Perera  wrote:

> Hi All,
>
> Please find inline comments.
>
> @Ruwan:
>
>> 
>>   true
>>   true
>> 
>> IMO, this wording makes a bit more sense. Also, let's make sure to
>> include explanations as to what these params enable.
>
> Looks good to me. However; `Operation Analytics` too make sense to me when
> we consider it as a term for analytics on top of device operations.
>
> @Imesh: Thanks for confirming the UX aspect of the new configuration.
>
> @Inosh:
>
>> I assume in the default configuration we will keep both these values to
>> false since by default we would not need the publish info to DAS. Also,
>> when you say publish operation response, does it mean we are publishing all
>> operation info such as application list, device info and policy responses?
>> If it's only device info, naming the config to PublishDeviceInfoResponse
>> would make more sense IMO.
>
> Yes, be default it will be false. With the current implementation we only
> publishers operation response. +1 let's change it to the
> PublishDeviceInfoResponse.
>
> @Charitha
>
>>  Also since it is useful to publish Operation response payloads to
>> Analytics for further processing, shall we add that capability to the IoTS?
>> If so we might need to introduce a way to filter out required operations
>> which needs to send responses to the Analytics. So I would like to suggest
>> to change above configuration as follows to accommodate that.
>
>  +1 for the idea. Let's make the it to publish any operation response as
> suggested.
>
> Best Regards,
> ~Rasika
>
> On Mon, Jan 22, 2018 at 12:53 PM, Charitha Goonetilleke <
> charit...@wso2.com> wrote:
>
>> Hi Rasika & all,
>>
>> BTW, with our current implementation we are publishing operation response
>> of DeviceInfo if *PublishOperationResponse* is enabled. So shall we
>> changed it as *PublishDeviceInfoResponse* ? Also since it is useful to
>> publish Operation response payloads to Analytics for further processing,
>> shall we add that capability to the IoTS? If so we might need to introduce
>> a way to filter out required operations which needs to send responses to
>> the Analytics. So I would like to suggest to change above configuration as
>> follows to accommodate that.
>>
>> 
>>   true
>>   true
>>   
>>   true
>>   
>>   BATTERY_LEVEL
>>   CHECK_LOCK_STATUS
>>   
>>   
>> 
>>
>> Also if we want to publish responses for all operations, we can set it as
>> follows:
>>
>>
>> 
>>   true
>>   true
>>   
>>   true
>>   
>>   *
>>   
>>   
>> 
>>
>> In order to received operation responses, we also need to have Event
>> receiver and event stream in Analytics side.
>>
>> WDYT?
>>
>> Thanks & Regards,
>> /charithag
>>
>>
>> On Mon, Jan 22, 2018 at 12:46 PM, Inosh Perera  wrote:
>>
>>> Hi Rasika,
>>>
>>> +1,
>>> I assume in the default configuration we will keep both these values to
>>> false since by default we would not need the publish info to DAS. Also,
>>> when you say publish operation response, does it mean we are publishing all
>>> operation info such as application list, device info and policy responses?
>>> If it's only device info, naming the config to PublishDeviceInfoResponse
>>> would make more sense IMO.
>>>
>>> Regards,
>>> Inosh
>>>
>>> On Mon, Jan 22, 2018 at 12:36 PM, Rasika Perera 
>>> wrote:
>>>
 Hi All,

 In IoT Server v3.1.0 geo location services is enabled with the
 following configuration;

 
   true
   true>>> nOperationResponse>
 

 ​With the new feature developments; In latest IoT Server(master
 branch); now we also allow publishing device-info responses through the
 same configuration.

 
   true
   true
 

 However; there might be use cases for enabling *geo location services* 
 *without*
 *publishing all the device-info* into IoT-Analytics server. Hence, As
 per the discussion with Charitha; I am planning to change the above
 configuration as below;

 
   true
   true
 

 WDYT? Appreciate your comments and ideas.

 Best Regards,
 ~Rasika

 --
 With Regards,

 *Rasika Perera*
 Senior Software Engineer
 LinkedIn: http://lk.linkedin.com/in/rasika90

 

 WSO2 Inc. www.wso2.com
 lean.enterprise.middleware

>>>
>>>
>>>
>>> --
>>> Inosh Perera
>>> Senior Software Engineer, WSO2 Inc.
>>> Tel: 077813 7285, 

Re: [Dev] Image persisting and retrieval mechanism for WSO2 IoT Server

[Kamidu Punchihewa]

Hi Nuwan,

 am +1 for the second option of retrieving the image as a binary stream
too. There are approaches which can be used and at the moment in use also
to represent an image using the binary information. IMO your concern
regarding this option will not be an issue.

Thanks and Best Regards,


On Tue, Jan 16, 2018 at 11:41 AM, Ruwan Yatawara  wrote:

> I am +1 for the second option of retrieving the image as a binary stream.
>
> Given the fact that images can be of varying sizes (talking about
> high-resolution ones, here), and Sidhdhi not having any image processing
> capabilities as of this moment, I do not see a clear advantage in using a
> SIdhdhi stream for storage and retrieval.
>
> Thanks and Regards,
>
> Ruwan Yatawara
>
> Technical Lead,
> WSO2 Inc.
>
> email : ruw...@wso2.com
> mobile : +94 77 9110413
> http://ruwansrants.blogspot.com/
> https://500px.com/ruwan_ace
> https://medium.com/@ruwanyatawara
>
>
> On Tue, Jan 16, 2018 at 10:52 AM, Nuwan Jayawardene 
> wrote:
>
>> Hi all,
>>
>> I'm currently working on a project to add image storing and retrieval
>> capabilities to the WSO2 IoT Server.
>>
>> To achieve this I have implemented the following;
>> 1) Added a separate DAO Table with a field with LONGBLOB data type for
>> storing.
>> 2) Added storage capabilities in the database for an image sent as a *File
>> *in the form of a *BinaryStream*.
>>
>> As of now, I've written unit tests and the test images are getting stored
>> successfully in the database.
>>
>> The problem lies in how to successfully retrieve the stored data. For
>> this, I have come across 2 possible approaches.
>> 1) *Retrieve as a File - *The notable downside I realized with this
>> solution is that each time a new Image is retrieved, a new file will be
>> created. Therefore measures would have to be taken to persist new files
>> while purging older obsolete ones.
>> 2) *Retrieve as BinaryStream - *Although this requires no persistent
>> memory usage and the data will only be retrieved on call and issues may
>> come up when representing that data from a UI end. Further analysis is
>> required for this approach.
>> 3) *Retrieve as FileOutputStream - *This is my preferred method and the
>> one recommended mostly in forums and tutorials.
>>
>> One other approach suggested to me was to use a *Siddhi Stream for both
>> storage and retrieval* purposes. This would further allow for analytics
>> to be performed on the data which not be very much possible with the
>> earlier mentioned approaches.
>>
>> Suggestions and Feedback are appreciated.
>> Thanks and regards!
>>
>> --
>> *Nuwan Jayawardene*
>> *Software Engineering Intern*
>> *WSO2, Inc.:http://wso2.com *
>> *lean.enterprise.middleware*
>> *Mobile  :- +94 71 1813299 <+94%2071%20181%203299>*
>>
>>
>>- *Linkedin* *:- **https://www.linkedin.com/in/nuwa
>>**njaya/
>>*
>>- * *
>>
>>
> --
> You received this message because you are subscribed to the Google Groups
> "WSO2 IoT Team Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to iot-group+unsubscr...@wso2.com.
> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>



-- 
Kamidu Sachith Punchihewa
*Senior Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>

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,
retransmit, 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] [Architecture] [VOTE] Release of WSO2 IoT Server 3.1.0 RC version 4

[Kamidu Punchihewa]

Hi all,

I tested the below mentioned as a super tenant user and tenant admin:

   1. User Management
   2. Policy Managment
   3. Role and Permission Managment
   4. Configuration Managment.
   5. IOS Device enrollment and policy publishing
   6. VFL Enrollment and Analytics
   7. Android mobile enrollment, policy, and operations.
   8. Disenrolling an Android device
   9. Android sense enrollment and analytics.

No issues were found.

[+] Stable - go ahead and release.

Thanks and Best Regards,

On Sun, Aug 13, 2017 at 10:13 PM, Megala Uthayakumar 
wrote:

> Hi,
>
> I tested followings
>
>- Mobile Device and App Management Quick Start guide with android.
>- User Management and Role Management functionalities through device
>management console.
>- Android device enrollment as a normal user. Tested with some
>operations as well.
>- Android sense enrollment as a normal user. Was able to see the
>relevant graphs.
>
> Did not encounter any issues. Hence,
> [+] Stable - Go ahead and release.
>
> Thanks.
>
> Regards,
> Megala
>
> On Fri, Aug 11, 2017 at 7:06 PM, Milan Perera  wrote:
>
>> Hi Devs,
>>
>> We are pleased to announce the release candidate version 4 of WSO2 IoT Server
>> 3.1.0.
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>>
>> Known issues : https://github.com/wso2/product-iots/issues-RC4
>> 
>>
>> Source and binary distribution files:
>> https://github.com/wso2/product-iots/releases/tag/v3.1.0-RC4
>>
>> The tag to be voted upon:
>> https://github.com/wso2/product-iots/tree/v3.1.0-RC4
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thank you
>>
>> Regards,
>> --
>> *Milan Perera *| Senior 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
>> 
>> 
>>
>
>
>
> --
> Megala Uthayakumar
>
> Software Engineer
> Mobile : 0779967122
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Kamidu Sachith Punchihewa
*Senior Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


Please Note that I have dyslexia and it may results in few misspelled words
in the content.
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,
retransmit, 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] [VOTE] Release of WSO2 IoT Server 3.1.0 RC version 2

[Kamidu Punchihewa]

Hi All,

I have tested the following scenarios with super tenant user and a non
super tenant user.

   - User Registration
   - Android Sense enrollment, Sensor data pushing
   - Role Management
   - Recovery and reset password
   - User Management
   - Android operations
   - Android enrollment
   - Android grouping
   - Android Policy
   - App install

Found no issues.

[+] Stable - go ahead and release.

Thanks and Best Regards,

On Tue, Jul 25, 2017 at 5:56 PM, Menaka Jayawardena  wrote:

> Hi all,
>
> I tested the following scenarios.
>
> *Android Enterprise Install:*
>
> *> Super Tenant mode: Admin User*
>
>
>1. Enrolled an Android device as the admin user.
>2. Create and publish an Android App.
>3. Installed the app to the admin user.
>
>
> *> Super Tenant mode: Normal user.*
>
>
>1. Created a new user with proper permissions.
>2. Enrolled an Android Device to that user.
>3. Installed the application to the user.
>
> *> Multitenant Mode.*
>
>
>1. Create a new Tenant.
>2. Enrolled an Android Device to the new Tenant user.
>3. Create and published a new Android App.
>4. Installed the app.
>
>
>
> *Android Sense. *
> 1. Enrolled an Android Sense device.
> 2. Started the data publishing and verified in the UI.
>
> Found no issues.
>
> [+ Stable] Go ahead and Release.
>
> Thanks and Regards,
> Menaka
>
>
> On Tue, Jul 25, 2017 at 5:27 PM, Hasunie Adikari  wrote:
>
>> Hi all,
>>
>> I have tested following scenarios for Windows 10.
>>
>> 1. Device enrollment.
>> 2. Add windows operations
>> 3. Create windows policy and apply to the device.
>> 4. Edit Windows policy and done apply changes.
>> 5. Create more policies and set priority and then apply to the device.
>> 6. tested notification pane.
>>
>> Found no issues.
>>
>> [+]Stable - go ahead and release
>>
>>
>>
>>
>>
>>
>>
>> On Tue, Jul 25, 2017 at 5:03 PM, Pasindu Jayaweera 
>> wrote:
>>
>>> Hi all,
>>> I have tested the following scenarios for Android.
>>>
>>>- Device enrollment
>>>- Device grouping
>>>- Device location
>>>- Device status update
>>>- Device search
>>>- Operations (Mute, Message, Ring, Enterprise-Wipe)
>>>- Policy (Restriction policy)
>>>- App install
>>>- Web-clip install
>>>
>>> Found no issues.
>>>
>>> [+] Stable - go ahead and release.
>>>
>>>
>>>
>>> On Mon, Jul 24, 2017 at 12:28 AM, Madhawa Perera 
>>> wrote:
>>>
 Hi Devs,

 We are pleased to announce the release candidate version 2 of WSO2 IoT
 Server 3.1.0.

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

 Known issues : https://github.com/wso2/produc
 t-iots/issues?q=is%3Aopen+is%3Aissue+label%3A3.1.0-RC1

 Source and binary distribution files:
 https://github.com/wso2/product-iots/releases/tag/v3.1.0-RC2

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

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

 Thank you
 Best Regards,
 WSO2 IoT Team

 --
 Madhawa Perera
 *Software Engineer*
 Mobile : +94 (0) 773655496 <+94%2077%20365%205496>
 <%2B94%20%280%29%20773%20451194>
 madha...@wso2.com


 --
 You received this message because you are subscribed to the Google
 Groups "WSO2 IoT Team Group" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to iot-group+unsubscr...@wso2.com.
 For more options, visit https://groups.google.com/a/wso2.com/d/optout.

>>>
>>>
>>>
>>> --
>>> *Pasindu Jayaweera*
>>> Software Engineer | WSO2 Inc
>>> Mobile: +94 718187375 <+94%2071%20818%207375>
>>> Blog: blog.pasindujayaweera.com
>>> 
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Hasunie Adikari*
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>> blog http://hasuniea.blogspot.com | https://medium.com/@Hasunie/
>> Mobile:+94713350904 <+94%2071%20335%200904>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Menaka Jayawardena*
> *Software Engineer - WSO2 Inc*
> *Tel : 071 350 5470*
> *LinkedIn: https://lk.linkedin.com/in/menakajayawardena
> *
> *Blog: https://menakamadushanka.wordpress.com/
> *
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 

Re: [Dev] New device type for IOTS ( Laptop agent )

[Kamidu Punchihewa]

Hi Lahiru,

I stringly belive that this device can be used to monitor and manage both
laptops and desktops so can we change the device type name to some thing
more genaralized.

And at the enterprise level where people manage and monitor computers they
intent to ask for the following features as well,

   - Installing patches
   

   - Installing software
   

   - Managing software licenses
   

   - Monitoring software usage statistics
   - Managing USB device usage
   - Taking control of remote desktops
   - Manage data Encryption

IMHO I think we can include most of the above features and it will be in
our best interest to include those or at least include them in our roadmap.

Thanks and Best Regards,

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>

Please Note that I have dyslexia and it may results in few misspelled words
in the content.

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,
retransmit, 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.

On Thu, Jul 6, 2017 at 8:17 PM, Lahiru Madushanka 
wrote:

> Hi Waruna,
>
> We will have some notification mechanisms in IOTS for infra / team lead
> level users.
> Ex:-  RAM capacity of device profile X is 8GB, when avg RAM usage of IOT
> group + profile X machines reach 7GB IOT team leads and infra team must
> receive notifications.
>
> Sure, I will update this thread with the progress.
>
> Thanks all of you guys for the suggestions. I gathered lot more use cases
> and different viewpoints.
>
> Thanks,
> Lahiru
>
> On Thu, Jul 6, 2017 at 12:13 PM, Waruna Jayaweera 
> wrote:
>
>> Hi Lahiru,
>>
>> Few Suggestions. You can also add alerts mechanism like [1] based on
>> analysed data. As an example if laptop cpu utilization is more than 90%
>> then send email to operation user.
>>
>> As others said you can reuse most of existing components for dashboard
>> and analysis. Your sample use cases are applied for any device types as we
>> can use same way to do predicative maintenance in iot devices. If we have
>> new device type , send some attributes to server and take some decisions.
>> So you can come up with documentation as if as how we can reuse those
>> components to support similar use cases in any device type/agent.
>>
>> [1]https://docs.wso2.com/display/DAS310/Creating+Alerts
>>
>> Thanks,
>> Waruna
>>
>>
>>
>> On Thu, Jul 6, 2017 at 11:04 AM, Lahiru Madushanka 
>> wrote:
>>
>>> Hi Harshan,
>>>
>>> Sorry for the unclarity of my initial statement. This is a continuation
>>> of "Laptop" device type developed by Thisari.
>>> Yeah the process is same as you explained.
>>>
>>> Thanks
>>>
>>> On Thu, Jul 6, 2017 at 10:16 AM, Harshan Liyanage 
>>> wrote:
>>>
 Hi Lahiru,

 Could you please clarify why we need a new device-type in this
 scenario? It looks like a feature on-top of "PC" or "Laptop" device-type.
 Analytics/ML part can be separated from the device-type. What we need to do
 is to just get the required data like RAM, CPU, HDD usage etc from that
 particular device type and push them into DAS. This is somewhat similar to
 what we are currently doing with the Android device-type. I'm wondering why
 we can't use the same approach here.

 Thanks,

 Harshan Liyanage
 EMM/IoT TG
 Mobile: *+94765672894*
 Email: hars...@wso2.com
 Blog : http://harshanliyanage.blogspot.com/
 *WSO2, Inc. :** wso2.com *
 lean.enterprise.middleware.

 On Wed, Jul 5, 2017 at 10:57 PM, Pasindu Jayaweera 
 wrote:

> Hi Lahiru,
> Q.) Other than pushing data from the laptop, will there be any
> operations or policies than can be applied from the server-side?
>
> Q) What could be the agent's behavior;
>
> a.) when the laptop is out of the network?
>
> b.) when the laptop has multiple operating systems?
>
>
> When designing analytics views and creating ML plans, I would like to
> suggest to make them in such a way that those units can be plugged not 
> only
> with the 

Re: [Dev] WSO2 Committers += Lakshani Gamage

[Kamidu Punchihewa]

congratz Lakshani !.

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>

Please Note that I have dyslexia and it may results in few misspelled words
in the content.

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,
retransmit, 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.

On Tue, Mar 21, 2017 at 2:21 AM, Rasika Perera  wrote:

> Congratulations Lakshani! Keep it up good works!
>
> On Tue, Mar 14, 2017 at 4:47 PM, Chamalee De Silva 
> wrote:
>
>> Congrats Lakshani !!!
>>
>> On Tue, Mar 14, 2017 at 12:32 PM, Harshan Liyanage 
>> wrote:
>>
>>> Congratz Lakshani 
>>>
>>> Harshan Liyanage
>>> EMM/IoT TG
>>> Mobile: *+94765672894*
>>> Email: hars...@wso2.com
>>> Blog : http://harshanliyanage.blogspot.com/
>>> *WSO2, Inc. :** wso2.com *
>>> lean.enterprise.middleware.
>>>
>>> On Tue, Mar 14, 2017 at 11:43 AM, Menaka Jayawardena 
>>> wrote:
>>>
 Congratz Lakshani!

 On Tue, Mar 14, 2017 at 9:42 AM, Rushmin Fernando 
 wrote:

> Hi All,
>
> It's my pleasure to welcome Lakshani Gamage as a WSO2 Committer.
>
> Lakshani had been a valuable contributor to the App Manager team and
> she is currently a member of the IoT team. In recognition of her
> contribution, dedication, and commitment she has been voted as a WSO2
> committer.
>
> Lakshani, welcome aboard and keep up the good work!
>
> Regards,
>
> --
> *Best Regards*
>
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc.  - Lean . Enterprise . Middleware
>
> mobile : +94775615183
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Menaka Jayawardena*
 *Software Engineer - WSO2 Inc*
 *Tel : 071 350 5470*
 *LinkedIn: https://lk.linkedin.com/in/menakajayawardena
 *
 *Blog: https://menakamadushanka.wordpress.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
>>>
>>>
>>
>>
>> --
>> Thanks & Regards,
>>
>> *Chamalee De Silva*
>> Software Engineer
>> *WS**O2* Inc. :http://wso2.com/
>>
>> Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
>> mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> With Regards,
>
> *Rasika Perera*
> Software Engineer
> LinkedIn: http://lk.linkedin.com/in/rasika90
>
> 
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Web clip feature not available in IoT

[Kamidu Punchihewa]

Hi Dulitha,

We have notes that also, Thank you for pointing out this. This was result
in when isolating mobile app management from rest of the app management
with IoTS Release.
Currently we are working on total mobile relate app management for IoT
server 3.0.1.
Please follow the Jira ticket[1] to keep track of the process.

[1] .https://wso2.org/jira/browse/IOTS-499

Thanks and Best Regards,

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>

Please Note that I have dyslexia and it may results in few misspelled words
in the content.

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,
retransmit, 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.

On Fri, Mar 3, 2017 at 10:36 AM, Dulitha Wijewantha 
wrote:

> Hi guys,
> Web clip feature that was available in the previous version is not
> available in the IoT 3.0.0 version.
>
> Cheers~
>
> --
> Dulitha Wijewantha (Chan)
> Software Engineer - Mobile Development
> WSO2 Inc
> Lean.Enterprise.Middleware
>  * ~Email   duli...@wso2.com *
> *  ~Mobile +94712112165 <+94%2071%20211%202165>*
> *  ~Website   dulitha.me *
> *  ~Twitter @dulitharw *
>   *~Github @dulichan *
>   *~SO @chan *
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 IoT Server 3.0.0 RC2

[Kamidu Punchihewa]

Hi all,

I have tested the followings.

   - Adding users and roles.
  - Verify using both devicemgt cnsole and carbon console.
   - Assigning permissions to roles.
  - Verify using both devicemgt cnsole and carbon console.
   - Enroll Android devices.
   - Enroll Androidsense devices.
   - Verify the device views
  - Android device view
  - Androidsense device view
  - IOS device view
   - Device Search
   - Goe Dashboard
  - For Android devices
  - For Androidsense devices

[+] Stable - go ahead and release.

Thanks and Best Regards

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Sat, Jan 21, 2017 at 10:01 AM, Sameera Gunarathne 
wrote:

> Hi,
>
> I have tested followings:
>
>- Creating and updating device groups
>- Group sharing among roles
>- Group Policy appliance for android devices
>- Group actions listing based on group owner permissions
>
> [+] Stable - go ahead and release.
>
> Thanks & Regards,
> Sameera.
>
> On Sat, Jan 21, 2017 at 9:14 AM, Geeth Munasinghe  wrote:
>
>> Hi all,
>>
>> I have tested the followings.
>>
>>- Adding users and roles.
>>- Assigning permissions to roles.
>>- Enroll Android devices.
>>- Creating device groups.
>>- Assigning devices to groups.
>>- Creating policies.
>>- Editing policies.
>>- Changing policy priorities.
>>- Applying changed policies to devices.
>>- Device Search
>>
>> [+] Stable - go ahead and release.
>>
>> Thanks
>> Geeth
>>
>> On Sat, Jan 21, 2017 at 8:04 AM, Hasunie Adikari 
>> wrote:
>>
>>> Hi,
>>>
>>> I have tested following scenarios,
>>>
>>>- Enroll Windows 10(version 1511,1607) and Windows 8.1 Devices
>>>- Add Device lock, ring, wipe, location, lock-reset, reboot
>>>operations.
>>>- Add Passcode, Camera restriction and Storage encryption policies.
>>>- Dis-enroll device
>>>- Dis enroll device and re enroll the device from different user.
>>>- Create new user with permissions.
>>>- Enroll the device for that new user and execute operations and
>>>policies for that user.
>>>- Enroll 3 Android Devices and 3 Windows Devices and grouping them.
>>>- Check Notification pane by adding notifications.
>>>
>>> [+] Stable - go ahead and release.
>>>
>>> Reagards
>>> Hasunie
>>>
>>>
>>> On Sat, Jan 21, 2017 at 6:13 AM, Chathura Dilan 
>>> wrote:
>>>
 Hi,

 I've tested

- Android app enrollment installation and un-installation, policies
and operations
- App Management


  [+] Stable - go ahead and release


 On Sat, Jan 21, 2017 at 5:18 AM, Jasintha Dasanayake  wrote:

> Hi All
>
> I have tested the following flows using the virtual firearm plugin :
>
>- Operation flows
>- Grouping devices
>- Applying and updating policy for individual & grouped devices
>- Realtime analytics
>
> [+] Stable-go ahead and release
>
> Regards
> /Jasintha
>
>
> On Sat, Jan 21, 2017 at 2:27 AM, Ayyoob Hamza  wrote:
>
>> Hi All,
>>
>> I have tested following:
>>
>>- Tested below flows using the reference device types
>>implementation(Virtual firealarm, Connected cup, Raspberry pi).
>>- Operation flow
>>   - Policy
>>   - Batch Analytics
>>   - Real time analytics
>>- Tested Android Device Management APIs
>>- Tested maven archtype for tooling
>>- Created a new device type by generating through the the maven
>>arch type.
>>- Tested Operation flow
>>   - Batch Analytics
>>   - Realtime analytics
>>- Tested the distributed setup (Mqtt Gateway, Http Gateway,
>>Device Type Publisher, Key Manager, Analytics, Mysql).
>>- Tested Android Apis in a distributed environment.
>>   - Virtual firealarm Enrollment and operation flow
>>- Role Management.
>>
>> [+] Stable-go ahead and release.
>>
>> Regards,
>> Ayyoob
>>
>> ___
>> Architecture mailing list
>> 

Re: [Dev] [VOTE] Release WSO2 Enterprise Mobility Manager 2.2.0 RC1

[Kamidu Punchihewa]

Hi Devs,

[+Looping Security Champions and Product Leads]
We are closing the vote due to the missing security reports.

Thanks and Best Regards,

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Tue, Nov 1, 2016 at 10:34 AM, Dulanja Liyanage <dula...@wso2.com> wrote:

> -1. Security reports not provided.
>
> On Mon, Oct 31, 2016 at 9:02 PM, Kamidu Punchihewa <sachi...@wso2.com>
> wrote:
>
>> Hi Devs,
>>
>> This is the release candidate of WSO2 Enterprise Mobility Manager 2.2.0
>>
>> Please download EMM 2.2.0 RC1 and test the functionality and vote. Vote
>> will be open for 72 hours or as needed.
>> Know issues: https://wso2.org/jira/issues/?filter=13384
>> Fixes provided : https://wso2.org/jira/issues/?filter=13582
>>
>> Source & binary distribution files:
>> https://github.com/wso2/product-emm/releases/tag/v2.2.0-RC1
>>
>> The tag to be voted upon:
>> https://github.com/wso2/product-emm/tree/release-2.2.0-RC1
>>
>>
>> [+] Stable - go ahead and release
>> [-]  Broken - do not release (explain why)
>>
>> Thanks and Regards,
>>
>> WSO2 IOT Team
>>
>> Kamidu Sachith Punchihewa
>> *Software Engineer*
>> WSO2, Inc.
>> lean . enterprise . middleware
>> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>>
>>
>> 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, retransmit, 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
>>
>>
>
>
> --
> Thanks & Regards,
> Dulanja Liyanage
> Lead, Platform Security Team
> WSO2 Inc.
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 Enterprise Mobility Manager 2.2.0 RC1

[Kamidu Punchihewa]

Hi Devs,

This is the release candidate of WSO2 Enterprise Mobility Manager 2.2.0

Please download EMM 2.2.0 RC1 and test the functionality and vote. Vote
will be open for 72 hours or as needed.
Know issues: https://wso2.org/jira/issues/?filter=13384
Fixes provided : https://wso2.org/jira/issues/?filter=13582

Source & binary distribution files:
https://github.com/wso2/product-emm/releases/tag/v2.2.0-RC1

The tag to be voted upon:
https://github.com/wso2/product-emm/tree/release-2.2.0-RC1


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

Thanks and Regards,

WSO2 IOT Team

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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] [VOTE] Release WSO2 Carbon Kernel 4.4.10 RC1

[Kamidu Punchihewa]

Hi All,

Built and tested the following with the EMM 2.2.0-SNAPSHOT. The release
behave as expected,Hence voting [+1][stable].


   - User Management in EMM
   - Device Management
   - Certificate Management
   - Policy Management.

Please note that the above sections were tested utilizing the environments
given below,

Ubuntu xenial (16.04) 64bit.
> 8GB RAM
> Mozilla Firefox 49.0.2 and Google Chrome 54.0.2840.59
>

Thanks and Best Regards,

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Mon, Oct 31, 2016 at 11:47 AM, Malintha Fernando 
wrote:

> Hi All,
>
> Built and tested following features with EMM 2.2.0 and found no issues.
> Hence voting [+1][stable].
>
>- Creating a new user roles and adding publisher permissions.
>- Login to EMM console with new user
>- Enrolling a device and pushing a policy
>- Creating a tenant and login to EMM console
>
>
> Thanks & Regards,
> Malintha
>
> On Fri, Oct 28, 2016 at 11:55 PM, Thusitha Thilina Dayaratne <
> thusit...@wso2.com> wrote:
>
>> Hi Devs,
>>
>> This is the 1st release candidate of WSO2 Carbon Kernel 4.4.10.
>>
>> This release fixes the following issues
>> *https://wso2.org/jira/issues/?filter=13580
>> *
>>
>> Please download and test your products with kernel 4.4.10 RC1 and vote. The
>> vote will be open for 72 hours or as longer as needed.
>>
>> Source and binary distribution files:
>> https://github.com/wso2/carbon-kernel/archive/v4.4.10-rc1.zip
>> http://svn.wso2.org/repos/wso2/people/thusithad/4.4.10/wso2c
>> arbon-4.4.10.zip
>>
>> Maven staging repository
>> *https://maven.wso2.org/nexus/content/repositories/orgwso2carbon-1042
>> *
>>
>> The tag to be voted upon :
>> https://github.com/wso2/carbon-kernel/releases/tag/v4.4.10-rc1
>>
>> [ ] Broken - Do not release (explain why)
>> [ ] Stable  - Go ahead and release
>>
>> Thank you
>> Platform Team
>> --
>> Thusitha Dayaratne
>> Software Engineer
>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>
>> Mobile  +94712756809
>> Blog  alokayasoya.blogspot.com
>> Abouthttp://about.me/thusithathilina
>> 
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Malintha Fernando
> Software Engineer
> WSO2 Inc. | http://wso2.com
> Mobile : +94 718874922
> Blog : http://blog.malintha.org
>
> Lean . Enterprise . Middleware
>
>
>
>
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 EMM 2.2.0-BETA2 is Released.

[Kamidu Punchihewa]

Hi All,

Please find the missing download link below,
*https://github.com/wso2/product-emm/releases/download/v2.2.0-BETA2/wso2emm-2.2.0-BETA2.zip
<https://github.com/wso2/product-emm/releases/download/v2.2.0-BETA2/wso2emm-2.2.0-BETA2.zip>*


Sorry for the inconvenience made.

Thanks and Best Regards,

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Wed, Oct 19, 2016 at 12:19 AM, Kamidu Punchihewa <sachi...@wso2.com>
wrote:

> WSO2 Enterprise Mobility Manager 2.2.0-BETA2 is released!
>
> WSO2 Enterprise Mobility Manager (WSO2 EMM) is a 100% open source,
> comprehensive platform that addresses mobile computing challenges which
> enterprises face today. WSO2 EMM supports iOS, Android & Windows devices
> and helps organizations deal with both "corporate-owned,
> personally-enabled" (COPE) devices and employee owned devices with the
> "bring-your-own-device" (BYOD) ownership schemes.
>
> Built on a generic device management framework (i.e. WSO2 Connected Device
> Management Framework) that can be extended to support many other device
> platforms, WSO2 EMM offers better scalability with its rich architecture,
> supporting horizontal as well as vertical scaling of associated components.
> Whether it is device configuration management, policy enforcement,
> app-management, device data security or compliance monitoring, WSO2 EMM
> offers a single enterprise grade platform for all your mobile computing
> needs.
>
>
>
> *Please find the additional bug fixes and Improvements introduced in this
> release :*
> Bug Fixes
>
>- [EMM-1620 <https://wso2.org/jira/browse/EMM-1620>] - Enrolment iOS
>10 error
>
>
>- [EMM-1129 <https://wso2.org/jira/browse/EMM-1129>] - Unable to log
>in to EMM console after configuring SSO
>- [EMM-1185 <https://wso2.org/jira/browse/EMM-1185>] - Sort policies
>by platform and status is not functioning
>- [EMM-1249 <https://wso2.org/jira/browse/EMM-1249>] - Unnecessary
>Jaggery related logs are printed on the console during the server start-up
>- [EMM-1321 <https://wso2.org/jira/browse/EMM-1321>] - WindowLeaked
>exception in Android agent
>- [EMM-1333 <https://wso2.org/jira/browse/EMM-1333>] - Users created
>through EMM console can not be given permission to login to AppStore
>- [EMM-1342 <https://wso2.org/jira/browse/EMM-1342>] - When policy
>bundle apply, existing policy should revoke
>- [EMM-1420 <https://wso2.org/jira/browse/EMM-1420>] - Profile doesn't
>get applied when device is locked
>- [EMM-1445 <https://wso2.org/jira/browse/EMM-1445>] - "Mobile App"
>permission for "store-admin" role should be assigned by default
>- [EMM-1461 <https://wso2.org/jira/browse/EMM-1461>] - Edit, Delete,
>Change Password option buttons on top of the User views in User Management
>page, will not show the option in word however the API name is shown in the
>browser
>- [EMM-1515 <https://wso2.org/jira/browse/EMM-1515>] - Irregular
>failures for Register Oauth App, Access Token Generation and Device
>Registration calls when the concurrency reaches at around 10 threads
>- [EMM-1523 <https://wso2.org/jira/browse/EMM-1523>] - Device
>Monitoring Dashboard not found (EMM analytics dashboard)
>- [EMM-1530 <https://wso2.org/jira/browse/EMM-1530>] - During load
>test - Failed to authenticate the incoming request due to error in
>permission initialization - For the actually working API methods
>- [EMM-1587 <https://wso2.org/jira/browse/EMM-1587>] - Unneccessary
>details included in user enrollment invitation email body
>- [EMM-1596 <https://wso2.org/jira/browse/EMM-1596>] -
>NullPointerException thrown when editing a user of secondary user store
>- [EMM-1601 <https://wso2.org/jira/browse/EMM-1601>] - Sorting doesn't
>apply for enrolled devices according to sorting options
>- [EMM-1619 <https://wso2.org/jira/browse/E

Re: [Dev] [EMM]Issues in calling admin services as a tenant user from a jaggery app

[Kamidu Punchihewa]

Hi Megala,

If you have found out the issue and solution. Please do the necessary
change and do a round of testing. If everything works as expected please
send a pull request to the carbon kernel.
@Kernal Team How we can get the this released for the EMM 2.2.0 release ?

Thanks and Best Regards,

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Wed, Oct 19, 2016 at 11:07 AM, Megala Uthayakumar 
wrote:

> Hi All,
>
> I am working on a jira [1] which is related with an exception that is
> thrown when trying to add a user/role in tenant mode using EMM console.
> This is particularly happens when we call the admin service to get the
> secondary user store configurations related to particular tenant [2].
> Following is the root cause behind this exception,
>
> *Caused by: java.lang.SecurityException: Illegal access attempt to cache ]
> owned by tenant*
> *{[test.com ],[1]} by tenant {[test.com
> ],[-1234]}*
>
> When trying to access the cache, the caller's tenant id has changed to
> super-tenant id, although tenant domain is correct. I tried to start the
> tenant flow before calling the admin service, but still I got the same
> error. While debugging I found, [3] is the point where the tenant domain is
> set to correct domain, while the tenant id still set to super-tenant id.
> Locally I changed that particular line as per below,
>
> PrivilegedCarbonContext.getThreadLocalCarbonContext().setTenantDomain(
> userTenantDomain,*true*);
>
> After that I could get the secondary user-store configurations related to
> that particular tenant. Is this a bug from carbon-level or is there any
> work-around to avoid this? Any comments or suggestions on this regard is
> highly appreciated.
>
> [1] https://wso2.org/jira/browse/EMM-1762
> [2] https://github.com/wso2/carbon-device-mgt/blob/master/
> components/device-mgt/org.wso2.carbon.device.mgt.ui/src/
> main/resources/jaggeryapps/devicemgt/app/modules/
> business-controllers/user.js#L607
> [3] https://github.com/wso2/carbon-kernel/blob/v4.4.9/
> core/org.wso2.carbon.server.admin/src/main/java/org/wso2/
> carbon/server/admin/module/handler/AuthenticationHandler.java#L93
>
> Thanks.
>
> Regards,
> Megala
> --
> Megala Uthayakumar
>
> Software Engineer
> Mobile : 0779967122
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 EMM 2.2.0-BETA2 is Released.

[Kamidu Punchihewa]

WSO2 Enterprise Mobility Manager 2.2.0-BETA2 is released!

WSO2 Enterprise Mobility Manager (WSO2 EMM) is a 100% open source,
comprehensive platform that addresses mobile computing challenges which
enterprises face today. WSO2 EMM supports iOS, Android & Windows devices
and helps organizations deal with both "corporate-owned,
personally-enabled" (COPE) devices and employee owned devices with the
"bring-your-own-device" (BYOD) ownership schemes.

Built on a generic device management framework (i.e. WSO2 Connected Device
Management Framework) that can be extended to support many other device
platforms, WSO2 EMM offers better scalability with its rich architecture,
supporting horizontal as well as vertical scaling of associated components.
Whether it is device configuration management, policy enforcement,
app-management, device data security or compliance monitoring, WSO2 EMM
offers a single enterprise grade platform for all your mobile computing
needs.



*Please find the additional bug fixes and Improvements introduced in this
release :*
Bug Fixes

   - [EMM-1620 ] - Enrolment iOS 10
   error


   - [EMM-1129 ] - Unable to log in
   to EMM console after configuring SSO
   - [EMM-1185 ] - Sort policies by
   platform and status is not functioning
   - [EMM-1249 ] - Unnecessary
   Jaggery related logs are printed on the console during the server start-up
   - [EMM-1321 ] - WindowLeaked
   exception in Android agent
   - [EMM-1333 ] - Users created
   through EMM console can not be given permission to login to AppStore
   - [EMM-1342 ] - When policy
   bundle apply, existing policy should revoke
   - [EMM-1420 ] - Profile doesn't
   get applied when device is locked
   - [EMM-1445 ] - "Mobile App"
   permission for "store-admin" role should be assigned by default
   - [EMM-1461 ] - Edit, Delete,
   Change Password option buttons on top of the User views in User Management
   page, will not show the option in word however the API name is shown in the
   browser
   - [EMM-1515 ] - Irregular
   failures for Register Oauth App, Access Token Generation and Device
   Registration calls when the concurrency reaches at around 10 threads
   - [EMM-1523 ] - Device Monitoring
   Dashboard not found (EMM analytics dashboard)
   - [EMM-1530 ] - During load test
   - Failed to authenticate the incoming request due to error in permission
   initialization - For the actually working API methods
   - [EMM-1587 ] - Unneccessary
   details included in user enrollment invitation email body
   - [EMM-1596 ] -
   NullPointerException thrown when editing a user of secondary user store
   - [EMM-1601 ] - Sorting doesn't
   apply for enrolled devices according to sorting options
   - [EMM-1619 ] - Unable to sort
   according to platform and status for policies
   - [EMM-1629 ] -
   EventAdapterConfigHelper error at server startup
   - [EMM-1637 ] - SQLException
   observed in MySQL Dsetup
   - [EMM-1639 ] - Continous
   clicking of a notification header redirects to a 404 Page
   - [EMM-1649 ] - iOS agent
   unregistration fails
   - [EMM-1654 ] - Difficult to view
   the OK button on device when the message has few characters
   - [EMM-1656 ] - Platform
   Configurations - Android Configurations Save page does not do any
   interaction action while the configuration is saved
   - [EMM-1657 ] - Unable to change
   the password of logged in user in EMM Console
   - [EMM-1658 ] - A user with only
   'login' and 'view users' permissions can change passwords of admin users in
   EMM Console
   - [EMM-1660 ] - Device
   Information Page load error at the first loading after device registration
   - Windows
   - [EMM-1661 ] - Unable to change
   the password of a user of secondary user store in EMM Console
   - [EMM-1662 ] - [UI] Change of
   name of the highest priority policy doesn't affect the name under Policy
   Compliance at first
   - [EMM-1663 

[Dev] No SCM URL was provided to perform the release Issue when releasing carbon-device-mgt-plugins

[Kamidu Punchihewa]

Hi All,

I am getting this issue while releasing the "carbon-device-mgt-plugins". I
have tried releasing few time with different repository locations and after
getting a new session also. Still getting this error.

As given below the SCM URL is available on the pom file.


https://github.com/wso2/carbon-device-mgt-plugins.git

scm:git:https://github.com/wso2/carbon-device-mgt-plugins.git


scm:git:https://github.com/wso2/carbon-device-mgt-plugins.git
HEAD


Please find the console out put given below,

[INFO] Scanning for projects...
[INFO]

[INFO] Reactor Build Order:
[INFO]
[INFO] WSO2 Carbon - Device Management Plugins Parent
[INFO] WSO2 Carbon - Mobile Plugins
[INFO] WSO2 Carbon - Mobile Plugins
[INFO] WSO2 Carbon - Mobile Device Management Impl
[INFO] WSO2 Carbon - Mobile Plugins
[INFO] WSO2 Carbon - Mobile Device Management Android Impl
[INFO] WSO2 Carbon - Android JAX-RS API
[INFO] WSO2 Carbon - Mobile Android UI
[INFO] WSO2 Carbon - Mobile Plugins
[INFO] WSO2 Carbon - Mobile Device Management Windows Impl
[INFO] WSO2 Carbon - Windows JAX-RS API
[INFO] WSO2 Carbon - Mobile Windows UI
[INFO] WSO2 Carbon - EMM Server UI
[INFO] WSO2 Carbon - Startup Handler That Prints MDM End-User Web-App URL
[INFO] WSO2 Carbon - IoT Plugins
[INFO] WSO2 Carbon - Arduino Plugin
[INFO] WSO2 Carbon - IoT Server Android Sense Analytics capp
[INFO] WSO2 Carbon - IoT Base Plugin
[INFO] WSO2 Carbon - IoT Device Management Common Impl
[INFO] WSO2 Carbon - AndroidSense DeviceType Plugin
[INFO] WSO2 Carbon - Android Sense API
[INFO] WSO2 Carbon - IoT Server Android Sense UI
[INFO] WSO2 Carbon - Arduino Plugin
[INFO] WSO2 Carbon - IoT Server Arduino Management Plugin
[INFO] WSO2 Carbon - IoT Server Arduino Service API
[INFO] WSO2 Carbon - IoT Server Arduino UI
[INFO] WSO2 Carbon - IoT Server Arduino Analytics capp
[INFO] WSO2 Carbon - Arduino Plugin
[INFO] WSO2 Carbon - IoT Server RaspberryPi Management Plugin
[INFO] WSO2 Carbon - IoT Server RaspberryPi UI
[INFO] WSO2 Carbon - IoT Server RaspberryPi API
[INFO] WSO2 Carbon - IoT Server Raspberrypi Analytics capp
[INFO] WSO2 Carbon - Device Mgt Input Adaptor Extensions Module
[INFO] WSO2 Carbon - Arduino Plugin
[INFO] WSO2 Carbon - IoT Server VirtualFireAlarm Management Plugin
[INFO] WSO2 Carbon - IoT Server Virtual Firealarm UI
[INFO] WSO2 Carbon - IoT Server VirtualFireAlarm Advanced Agent
[INFO] WSO2 Carbon - IoT Server VirtualFireAlarm Agent
[INFO] WSO2 Carbon - IoT Server VirtualFireAlarm API
[INFO] WSO2 Carbon - IoT Server SCEP Server API
[INFO] WSO2 Carbon - IoT Server UI
[INFO] WSO2 Carbon - Device Mgt Output MQTT Adaptor Module
[INFO] WSO2 Carbon - Device Mgt Output MQTT Adaptor Module
[INFO] WSO2 Carbon - Event Output UI Adapter Module
[INFO] WSO2 - Webapp for UI Output Event Adapter
[INFO] WSO2 Carbon - Device Mgt Input Adaptor Module - Http
[INFO] WSO2 Carbon - Device Mgt Input Adaptor Module - MQTT
[INFO] WSO2 Carbon - Device Mgt Input Adaptor Module - XMPP
[INFO] WSO2 Carbon - IoT Analytics Scripts
[INFO] WSO2 Carbon - IoT Server  Analytics C-APP
[INFO] WSO2 Carbon - Mobile Plugins Extensions
[INFO] WSO2 Carbon - App Manager WSO2 MDM OSGI Connector Component
[INFO] WSO2 Carbon - Device Management EMM Plugins Feature
[INFO] WSO2 Carbon - Device Management EMM Base Plugin Feature
[INFO] WSO2 Carbon - Mobile Device Management Feature
[INFO] WSO2 Carbon - Device Management Android Plugin Feature
[INFO] WSO2 Carbon - Android Device Management Feature
[INFO] WSO2 Carbon - Device Management Windows Plugin Feature
[INFO] WSO2 Carbon - Windows Device Management Feature
[INFO] WSO2 Carbon - Device Management IoT Plugins Feature
[INFO] WSO2 Carbon - IoT Server IoT Analytics Feature
[INFO] WSO2 Carbon - IoT Server Analytics Feature
[INFO] WSO2 Carbon - IoT Server Android Sense Device Feature
[INFO] WSO2 Carbon - IoT Server Android Sense Feature
[INFO] WSO2 Carbon - IoT Server Arduino Device Feature
[INFO] WSO2 Carbon - IoT Server Arduino Feature
[INFO] WSO2 Carbon - IoT Server RaspberryPi Device Feature
[INFO] WSO2 Carbon - IoT Server RaspberryPi Feature
[INFO] WSO2 Carbon - IoT Server VirtualFireAlarm Device Feature
[INFO] WSO2 Carbon - IoT Server VirtualFireAlarm Feature
[INFO] WSO2 Carbon - Device Management IoT Base Plugin Feature
[INFO] WSO2 Carbon - IoT Device Management Feature
[INFO] WSO2 Carbon - IoT Device Management Feature
[INFO] IoT Server Device types
[INFO] IoT Server Device types Feature
[INFO] WSO2 Carbon - Device Management Extensions
[INFO] WSO2 Carbon - App management MDM OSGI Connector
[INFO]

[INFO]

[INFO] Building WSO2 Carbon - Device Management Plugins Parent
2.2.4-SNAPSHOT
[INFO]

[INFO]
[INFO] --- maven-release-plugin:2.5.1:clean (default-cli) @
carbon-device-mgt-plugins-parent ---
[INFO] Cleaning up after release...

Re: [Dev] Alert UI Improvements in Device Management/EMM/IOT products

[Kamidu Punchihewa]

Hi Thusith,

Thank you and +1 for the idea.
@RasikaP, @SajithAR shall we proceed with this soon as the EMM 2.2.0 is out.
WDYT?

Thanks and Best Regards,

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Fri, Oct 14, 2016 at 10:13 AM, Rasika Perera <rasi...@wso2.com> wrote:

> This is a great, Hopefully we can propagate this up to UUF level?
>> AFAIK we don't have a Modal Dialog Unit (or a Fragment) written for UUF.
>
> +1, I think this is a part of the reusable base component rather on the
> framework of the UUF. Let's add this into the default base component.​
>
> On Fri, Oct 14, 2016 at 12:29 AM, Thusitha Kalugamage <thusi...@wso2.com>
> wrote:
>
>> Hi Kamindu,
>>
>> This is a great, Hopefully we can propagate this up to UUF level?
>> AFAIK we don't have a Modal Dialog Unit (or a Fragment) written for UUF.
>>
>> @SajithaAR, @RasikaP can we make good use of this?
>>
>> Regards,
>>
>> On Wed, Oct 12, 2016 at 6:46 PM, Kamidu Punchihewa <sachi...@wso2.com>
>> wrote:
>>
>>> Hi All,
>>>
>>> When developing or improving the user interfaces of EMM , IOT server or
>>> device management please utilize the newly introduced "cdmf.unit.ui.modal"
>>> for all the alerts and modal related implementations.
>>>
>>> Please find a simple example of how to utilize the above unit for modal
>>> creation and manipulations.
>>> You can utilize the "modalDialog" functions once you import the unit to
>>> your page by adding the below line on the .hbs file.
>>>
>>> After which utilize the described functions below in the client side
>>> scripts:
>>>
>>> *modalDialog.header("Sample Modal Dialog");*
>>>>
>>> You can use the above method to define the modal header or tile the
>>> input which can be simple text or a HTML content.
>>>
>>> *modalDialog.content("Sample Modal Content");*
>>>>
>>> You can use the above method to define the modal content or tile the
>>> input which can be simple text or a HTML content.
>>>
>>>  *modalDialog.footer("All Right Received");*
>>>>
>>> You can use the above method to define the modal footer or tile the
>>> input which can be simple text or a HTML content. If there are a set of
>>> buttons you need to include, you can use this method and provide the
>>> buttons as HTML content. Else you can use the method given below.
>>>
>>> *modalDialog.footerButtons(object);*
>>>>
>>> You need to provide the input as given below.
>>> This will provide you a footer with buttons which contains the basic
>>> styling from wso2 theme.
>>>
>>> In order to show the modal dialog there are 3 options to select from
>>> which are as below:
>>>
>>>
>>>- *modalDialog.show()*
>>>   - This will result in a normal modal content without any icons in
>>>   the title
>>>- *modalDialog.showAsError()*
>>>   - This will result in a modal dialog with an error icon in the
>>>   title
>>>- *modalDialog.showAsWarning()*
>>>   - This will result in a modal dialog with a warning icon in the
>>>   title
>>>
>>>
>>> Thanks and Best Regards,
>>> Kamidu Sachith Punchihewa
>>> *Software Engineer*
>>> WSO2, Inc.
>>> lean . enterprise . middleware
>>> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>>>
>>>
>>> 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 t

[Dev] Releasing carbon-store 4.4.x-kernal.

[Kamidu Punchihewa]

Hi Sameera,

Can you Please release carbon store's app manager branch [1].
@Megala can you verify the fixes are merage to the branch and test the
component when released.

[1] https://github.com/wso2/carbon-store/tree/app-manager-4.4.x-kernel

Thanks and Best Regards,
Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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

[Dev] Alert UI Improvements in Device Management/EMM/IOT products

[Kamidu Punchihewa]

Hi All,

When developing or improving the user interfaces of EMM , IOT server or
device management please utilize the newly introduced "cdmf.unit.ui.modal"
for all the alerts and modal related implementations.

Please find a simple example of how to utilize the above unit for modal
creation and manipulations.
You can utilize the "modalDialog" functions once you import the unit to
your page by adding the below line on the .hbs file.

After which utilize the described functions below in the client side
scripts:

*modalDialog.header("Sample Modal Dialog");*
>
You can use the above method to define the modal header or tile the input
which can be simple text or a HTML content.

*modalDialog.content("Sample Modal Content");*
>
You can use the above method to define the modal content or tile the input
which can be simple text or a HTML content.

 *modalDialog.footer("All Right Received");*
>
You can use the above method to define the modal footer or tile the input
which can be simple text or a HTML content. If there are a set of buttons
you need to include, you can use this method and provide the buttons as
HTML content. Else you can use the method given below.

*modalDialog.footerButtons(object);*
>
You need to provide the input as given below.
This will provide you a footer with buttons which contains the basic
styling from wso2 theme.

In order to show the modal dialog there are 3 options to select from which
are as below:


   - *modalDialog.show()*
  - This will result in a normal modal content without any icons in the
  title
   - *modalDialog.showAsError()*
  - This will result in a modal dialog with an error icon in the title
   - *modalDialog.showAsWarning()*
  - This will result in a modal dialog with a warning icon in the title


Thanks and Best Regards,
Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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] [EMM] Registry Exception thrown at EMM publisher/store login

[Kamidu Punchihewa]

Hi Sameera,

This is a know issue with EMM 2.2.0-beta pack. You can track the progress
of the issue by following the Jira ticket[1].

[1] https://wso2.org/jira/browse/EMM-1669

Thanks and Best Regards,

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Thu, Oct 6, 2016 at 3:14 PM, Sameera Gunarathne 
wrote:

> Hi all,
>
> After login to the EMM app publisher/store we can see the following error:
>
> [2016-10-03 13:51:00,155] ERROR 
> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry}
> -  Registry Exception occurred while executing the query
> org.wso2.carbon.registry.core.exceptions.RegistryException: Invalid value
> "8" for parameter "parameterIndex" [90008-175]
> at org.wso2.carbon.registry.core.jdbc.dataaccess.SQLQueryProcessor.
> executeQuery(SQLQueryProcessor.java:239)
> at org.wso2.carbon.registry.core.jdbc.queries.QueryProcessorManager.
> executeQuery(QueryProcessorManager.java:137)
> at org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.
> executeQuery(EmbeddedRegistry.java:2283)
> at org.wso2.carbon.registry.core.caching.CacheBackedRegistry.executeQuery(
> CacheBackedRegistry.java:480)
> at org.wso2.carbon.registry.core.session.UserRegistry.
> executeQueryInternal(UserRegistry.java:1757)
> at org.wso2.carbon.registry.core.session.UserRegistry.access$
> 3500(UserRegistry.java:61)
> at org.wso2.carbon.registry.core.session.UserRegistry$36.run(
> UserRegistry.java:1705)
> at org.wso2.carbon.registry.core.session.UserRegistry$36.run(
> UserRegistry.java:1702)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.wso2.carbon.registry.core.session.UserRegistry.
> executeQuery(UserRegistry.java:1702)
> at org.wso2.carbon.appmgt.impl.APIConsumerImpl.getAllTags(
> APIConsumerImpl.java:843)
> at 
> org.wso2.carbon.appmgt.impl.UserAwareAPIConsumer.getAllTags(UserAwareAPIConsumer.java:39)
> ..
>
> After some debugging it seems to be both APIM feature and APPM feature
> trying to execute same query at the registry path /_system/config/
> repository/components/org.wso2.carbon.registry/queries/tag-summary [1].
> Since they are different queries [2] & [3] when loading the APPM
> publisher/store components it triggers this error. Then I built
> carbon-appmgt locally by giving a different path to store query scripts.
> Then the issue is fixed. Seems like if it can be done to either of the
> components this issue can be fixed. Any help or suggestions highly
> appreciated.
>
> [1]
>
> [2] - https://github.com/wso2/carbon-apimgt/blob/
> d37855ec3551c97c70166d990504801b2d72d18b/components/apimgt/
> org.wso2.carbon.apimgt.impl/src/main/java/org/wso2/carbon/apimgt/impl/
> AbstractAPIManager.java#L210
>
> [3] - https://github.com/wso2/carbon-appmgt/blob/master/
> components/org.wso2.carbon.appmgt.impl/src/main/java/org/
> wso2/carbon/appmgt/impl/AbstractAPIManager.java#L152
>
> Thanks & Regards,
> --
> Sameera Gunarathne
> Software Engineer, WSO2 Inc. http://wso2.com
> 
> Email: samee...@wso2.com
> Mobile: +94714155561
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] how can I install GoDaddy SSL certificates for a new WSO2 keystore

[Kamidu Punchihewa]

Hi Brian,

You follow the below steps and add your Go daddy SSL certificate to the key
store.


>- Convert the downloaded ssl certificates from your vendor to .pem
>files.
>
> openssl x509 -in  -out 
> Example:
> openssl x509 -in your-domain-com-apache.crt -out your-domain-com-apache.pem
> openssl x509 -in your-domain-com-ee.crt -out your-domain-com-ee.pem
>
>- Create a certificate chain with the root and intermediate
>certifications.
>
> cat   ... >> 
> Example:
> cat your-domain-com-apache.pem your-domain-com-ee.pem >>
> clientcertchain.pem
> cat your-domain-com-apache.crt your-domain-com-ee.crt >>
> clientcertchain.crt
>
>- Export the SSL certificate chain file as a PKCS12 file with
>"wso2carbon" as the alias.
>
> openssl pkcs12 -export -out .p12 -inkey .key -in ia.crt
> -CAfile clientcertchain.pem -name ""
> Example:
> openssl pkcs12 -export -out KEYSTORE.p12 -inkey ia.key -in ia.crt -CAfile
> clientcertchain.pem -name "wso2carbon"
>


For more information on certificate chaning with wso2 server please reffer
to the article [1]. Please not the same communication mechanism we use for
device communication using exsisting SSL certificates, can be applied to
basic server communications too.

[1].
http://wso2.com/library/tutorials/2016/06/how-to-configure-device-communication-with-an-existing-ssl-certificate-with-wso2-enterprise-mobility-manager/

Thanks and Best Regards,

Thanks and Best Regards,

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Sat, Oct 1, 2016 at 2:52 PM, Brian Saltzman 
wrote:

> the SSL zip file from GoDaddy contains two files
>
>- GoDaddy Certificate Bundles - G2 With Cross to G1, includes Root
>(gd_bundle-g2-g1.crt)
>- randomfile.crt (I'm assuming that is the ExternalCARoot file.)
>
> go daddy has a intermediate crt files here: https://certs.godaddy.
> com/repository
>
> from WSO2 docs they explain how to do this for Comodo CA
>
> https://docs.wso2.com/display/Carbon420/Creating+New+Keystores#
> CreatingNewKeystores-Step3:ImportCA-signedcertificatestokeystore
>
> keytool -import -trustcacerts -alias ExternalCARoot -file
> AddTrustExternalCARoot.crt -keystore newkeystore.jks -storepass mypassword
>
> keytool -import -trustcacerts -alias TrustCA -file COMODORSAAddTrustCA.crt
> -keystore newkeystore.jks -storepass mypassword
>
> keytool -import -trustcacerts -alias SecureServerCA -file
> COMODORSADomainValidationSecureServerCA.crt -keystore newkeystore.jks
> -storepass mypassword
>
> Please provide keytool commands to install GoDaddy certs and if I need two
> intermediate files and which ones from the intermediate link or if I can
> just use the bundle file.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [EMM] Why we are using 404 for "No Content" responses ?

[Kamidu Punchihewa]

Hi All,

Agreed with Geeth and Harshan, When it come to the OOB User interface of
EMM the request with an 404 is detect as an error and your is prompted with
an error message since the error handling is handling in a Central
controller witch acts in general so if there are no error occurred in the
sever side best approach not to return status code in 400 - 499 range.

Thanks & Best Regards,

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Wed, Jun 15, 2016 at 12:18 AM, Harshan Liyanage  wrote:

> +1
>
> Harshan Liyanage
> Senior Software Engineer
> Mobile: *+94724423048*
> Email: hars...@wso2.com
> Blog : http://harshanliyanage.blogspot.com/
> *WSO2, Inc. :** wso2.com *
> lean.enterprise.middleware.
>
> On Tue, Jun 14, 2016 at 1:42 PM, Geeth Munasinghe  wrote:
>
>> Hi all,
>>
>> I think we should make relevant changes in APIs to send 200 status code
>> for no content responses. This should only be done if the request is with
>> query or form params, but not for request with path parameters (Which is an
>> exact resource, should return 404).
>>
>> Thanks
>> Geeth
>>
>>
>> *G. K. S. Munasinghe*
>> *Senior Software Engineer,*
>> *WSO2, Inc. http://wso2.com  *
>> *lean.enterprise.middleware.*
>>
>> email: ge...@wso2.com
>> phone:(+94) 777911226
>>
>> On Tue, Jun 14, 2016 at 11:48 PM, Harshan Liyanage 
>> wrote:
>>
>>> Hi Geeth,
>>>
>>> Agreed. In such cases I guess sending 200 with empty body will be more
>>> appropriate because there are some cases where the server responds with 204
>>> when the service does not return data (i.e in some DELETE, POST requests).
>>>
>>> Thanks,
>>>
>>> Harshan Liyanage
>>> Senior Software Engineer
>>> Mobile: *+94724423048*
>>> Email: hars...@wso2.com
>>> Blog : http://harshanliyanage.blogspot.com/
>>> *WSO2, Inc. :** wso2.com *
>>> lean.enterprise.middleware.
>>>
>>> On Tue, Jun 14, 2016 at 12:42 PM, Geeth Munasinghe 
>>> wrote:
>>>
 Hi Ayyoob

 On Tue, Jun 14, 2016 at 11:01 PM, Ayyoob Hamza  wrote:

> Yes I agree with Harshan,
>
> It is a question about whether we are looking this as a resource or an
> endpoint. We should look at the url in the resource context(restful
> approach) even though it is built on top of http. Therefore IMO we need to
> think that we are mapping a resource to the url and therefore suitable
> response would be 404.
>
>
 /devices/{device_idenitifier} - this should return 404 if requested for
 non-existence device. I have no argument about it. But my concern is at
 /devices?{query_parameter}. This is different. Actual resource is /devices,
 but it returns no content due to filtering criteria associated with query
 parameters, That is, in my opinion is a valid request which deserves a 200
 or 204 response code.

 Thanks
 Geeth


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

Re: [Dev] [OAuth] Error happens in EMM intermittently

[Kamidu Punchihewa]

Hi Kasun,

Please follow the mail thread "*[DEV][IS] Getting an Unique index or
primary key violation exception*".
Discussion related to the above intermittent issue was conducted earlier in
the above mail thread.

Thanks and Best Regards,

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Wed, May 18, 2016 at 10:47 AM, Kasun Dananjaya Delgolla 
wrote:

> Hi All,
>
> We're getting the following error in the EMM intermittently. Any idea why
> this happens?
>
> [2016-05-18 10:13:25,673] ERROR
> {org.wso2.carbon.identity.oauth2.OAuth2Service} -  Error occurred while
> issuing the access token for Client ID : pXPA6a6U9T047rd6vneb4NWtTfUa, User
> ID null, Scope : [PRODUCTION] and Grant Type : refresh_token
> org.wso2.carbon.identity.oauth2.IdentityOAuth2Exception: Error when
> storing the access token for consumer key : pXPA6a6U9T047rd6vneb4NWtTfUa
> at
> org.wso2.carbon.identity.oauth2.dao.TokenMgtDAO.storeAccessToken(TokenMgtDAO.java:246)
> at
> org.wso2.carbon.identity.oauth2.dao.TokenMgtDAO.invalidateAndCreateNewToken(TokenMgtDAO.java:1085)
> at
> org.wso2.carbon.identity.oauth2.token.handlers.grant.RefreshGrantHandler.issue(RefreshGrantHandler.java:259)
> at
> org.wso2.carbon.identity.oauth2.token.AccessTokenIssuer.issue(AccessTokenIssuer.java:196)
> at
> org.wso2.carbon.identity.oauth2.OAuth2Service.issueAccessToken(OAuth2Service.java:196)
> at
> org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.getAccessToken(OAuth2TokenEndpoint.java:245)
> at
> org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.issueAccessToken(OAuth2TokenEndpoint.java:111)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at
> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:188)
> at
> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:104)
> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:204)
> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:101)
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:94)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> at
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:249)
> at
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:248)
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:222)
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:153)
> at
> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:171)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:289)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:209)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:265)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at
> org.wso2.carbon.ui.filters.CSRFPreventionFilter.doFilter(CSRFPreventionFilter.java:88)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at
> 

Re: [Dev] Changing the Primary Keystore password in IS 5.0.0 SP1.

[Kamidu Punchihewa]

Hi Omindu,

Thank you. I change the both password and key password to the same value
and the Issues is fixed.

Thanks and Best Regards.

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Tue, Apr 26, 2016 at 11:37 AM, Omindu Rathnaweera <omi...@wso2.com>
wrote:

> Hi Kamindu,
>
> This can happen when the keystore and the private key password are not the
> same (see [1]). Can you try changing the private key password to match the
> keystore password and check? You can follow [2] to change the private key
> password.
>
> [1] - https://wso2.org/jira/browse/CARBON-14975
> [2] -
> http://xacmlinfo.org/2014/05/26/how-to-keystore-changing-java-key-store-passwords/
>
> Regards,
> Omindu.
>
> On Tue, Apr 26, 2016 at 10:57 AM, Kamidu Punchihewa <sachi...@wso2.com>
> wrote:
>
>> Hi Tharindu,
>>
>> I debugged the mentioned class and checked the runtime values for the two
>> variables below as suggested:
>>
>>- keystorePath
>>- keystorePassword
>>
>> For both the variables the correct values were assigned at runtime. The
>> correct key store was assigned to the variables along with the new password
>> provided.
>> Any idea why the above mentioned error occurred even when the correct
>> password is provided?
>>
>> Thanks and Best Regards,
>>
>> Kamidu Sachith Punchihewa
>> *Software Engineer*
>> WSO2, Inc.
>> lean . enterprise . middleware
>> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>>
>>
>> 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, retransmit, 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.
>>
>> On Mon, Apr 25, 2016 at 7:04 PM, Tharindu Edirisinghe <tharin...@wso2.com
>> > wrote:
>>
>>> Hi Kamidu,
>>>
>>> If you have correctly set the new password in identity.xml file's
>>> *EntitlementSettings*, can you remote debug the
>>> *org.wso2.carbon.identity.entitlement* 's *4.2.2 *version to find out
>>> the actual cause.
>>>
>>> The particular class is
>>>
>>>
>>> *src/main/java/org/wso2/carbon/identity/entitlement/internal/EntitlementServiceComponent.java*
>>> You may need to check the values read for following variables in the
>>> class.
>>>
>>> //read the keystore and password used for ssl
>>> communication from config
>>> String keystorePath = IdentityUtil.getProperty(
>>> ThriftConfigConstants.PARAM_KEYSTORE_LOCATION);
>>> String keystorePassword = IdentityUtil.getProperty(
>>> ThriftConfigConstants.PARAM_KEYSTORE_PASSWORD);
>>>
>>> Regards,
>>> TharinduE
>>>
>>> On Mon, Apr 25, 2016 at 5:56 PM, Kamidu Punchihewa <sachi...@wso2.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I have a IS 5.0.0 SP1 pack and i have change the default password of
>>>> the key store and changed the following config files accordingly.
>>>>
>>>>- /repository/conf/identity.xml.
>>>>- /repository/conf/carbon.xml
>>>>- /repository/conf/axis2/axis2.xml
>>>>- /repository/conf/security/cipher-tool.properties
>>>>- /repository/conf/security/secret-conf.properties
>>>

Re: [Dev] Changing the Primary Keystore password in IS 5.0.0 SP1.

[Kamidu Punchihewa]

Hi Tharindu,

I debugged the mentioned class and checked the runtime values for the two
variables below as suggested:

   - keystorePath
   - keystorePassword

For both the variables the correct values were assigned at runtime. The
correct key store was assigned to the variables along with the new password
provided.
Any idea why the above mentioned error occurred even when the correct
password is provided?

Thanks and Best Regards,

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Mon, Apr 25, 2016 at 7:04 PM, Tharindu Edirisinghe <tharin...@wso2.com>
wrote:

> Hi Kamidu,
>
> If you have correctly set the new password in identity.xml file's
> *EntitlementSettings*, can you remote debug the
> *org.wso2.carbon.identity.entitlement* 's *4.2.2 *version to find out the
> actual cause.
>
> The particular class is
>
>
> *src/main/java/org/wso2/carbon/identity/entitlement/internal/EntitlementServiceComponent.java*
> You may need to check the values read for following variables in the
> class.
>
> //read the keystore and password used for ssl
> communication from config
> String keystorePath = IdentityUtil.getProperty(
> ThriftConfigConstants.PARAM_KEYSTORE_LOCATION);
> String keystorePassword = IdentityUtil.getProperty(
> ThriftConfigConstants.PARAM_KEYSTORE_PASSWORD);
>
> Regards,
> TharinduE
>
> On Mon, Apr 25, 2016 at 5:56 PM, Kamidu Punchihewa <sachi...@wso2.com>
> wrote:
>
>> Hi,
>>
>> I have a IS 5.0.0 SP1 pack and i have change the default password of the
>> key store and changed the following config files accordingly.
>>
>>- /repository/conf/identity.xml.
>>- /repository/conf/carbon.xml
>>- /repository/conf/axis2/axis2.xml
>>- /repository/conf/security/cipher-tool.properties
>>- /repository/conf/security/secret-conf.properties
>>- /repository/conf/security/cipher-text.properties
>>-
>>
>> /repository/deployment/server/jaggeryapps/dashboard/authentication/auth_config.json
>>-
>>
>> /repository/deployment/server/webapps/authenticationendpoint/WEB-INF/classes/TenantConfig.properties
>>
>> At Server startup the following error occurred.
>> Is there are any more changes to be done?
>>
>> *Error Log :*
>>
>> [2016-04-25 17:51:39,207] ERROR
>> {org.wso2.carbon.identity.entitlement.internal.EntitlementServiceComponent}
>> -  Error in initializing thrift transport
>> org.apache.thrift.transport.TTransportException: Error creating the
>> transport
>> at
>> org.apache.thrift.transport.TSSLTransportFactory.createSSLContext(TSSLTransportFactory.java:201)
>> at
>> org.apache.thrift.transport.TSSLTransportFactory.getServerSocket(TSSLTransportFactory.java:102)
>> at
>> org.wso2.carbon.identity.entitlement.internal.EntitlementServiceComponent.startThriftEntitlementService(EntitlementServiceComponent.java:329)
>> at
>> org.wso2.carbon.identity.entitlement.internal.EntitlementServiceComponent.startThriftServices(EntitlementServiceComponent.java:300)
>> at
>> org.wso2.carbon.identity.entitlement.internal.EntitlementServiceComponent.activate(EntitlementServiceComponent.java:162)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>> at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(In

[Dev] Changing the Primary Keystore password in IS 5.0.0 SP1.

[Kamidu Punchihewa]

Hi,

I have a IS 5.0.0 SP1 pack and i have change the default password of the
key store and changed the following config files accordingly.

   - /repository/conf/identity.xml.
   - /repository/conf/carbon.xml
   - /repository/conf/axis2/axis2.xml
   - /repository/conf/security/cipher-tool.properties
   - /repository/conf/security/secret-conf.properties
   - /repository/conf/security/cipher-text.properties
   -
   
/repository/deployment/server/jaggeryapps/dashboard/authentication/auth_config.json
   -
   
/repository/deployment/server/webapps/authenticationendpoint/WEB-INF/classes/TenantConfig.properties

At Server startup the following error occurred.
Is there are any more changes to be done?

*Error Log :*

[2016-04-25 17:51:39,207] ERROR
{org.wso2.carbon.identity.entitlement.internal.EntitlementServiceComponent}
-  Error in initializing thrift transport
org.apache.thrift.transport.TTransportException: Error creating the
transport
at
org.apache.thrift.transport.TSSLTransportFactory.createSSLContext(TSSLTransportFactory.java:201)
at
org.apache.thrift.transport.TSSLTransportFactory.getServerSocket(TSSLTransportFactory.java:102)
at
org.wso2.carbon.identity.entitlement.internal.EntitlementServiceComponent.startThriftEntitlementService(EntitlementServiceComponent.java:329)
at
org.wso2.carbon.identity.entitlement.internal.EntitlementServiceComponent.startThriftServices(EntitlementServiceComponent.java:300)
at
org.wso2.carbon.identity.entitlement.internal.EntitlementServiceComponent.activate(EntitlementServiceComponent.java:162)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
at
org.wso2.carbon.identity.thrift.authentication.internal.ThriftAuthenticationServiceComponent.activate(ThriftAuthenticationServiceComponent.java:69)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at

Re: [Dev] Device Enrollment Failed - WSO2 EMM 2.0

[Kamidu Punchihewa]

Hi Suresh,

Can you kindly provide the new mailto configuration.

Thnaks,

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Wed, Mar 23, 2016 at 5:11 PM, Suresh Kumar <suresh_ku...@fulcrumww.com>
wrote:

> Hi Sachith
>
>
> I tried as you mentioned, changed the 'axis2_client.xml' instead of
> axis2.xml however I'm getting following exception, Kindly help out
>
>
> [2016-03-23 16:52:38,756] ERROR
> {org.wso2.carbon.device.mgt.core.email.sender.EmailServiceProviderImpl} -
> Error in delivering the message, subject: 'Enroll your Device
>  with WSO2 MDM', to: 'sureshkrish...@gmail.com'
> org.apache.axis2.AxisFault: The system cannot infer the transport
> information from the mailto:sureshkrish...@gmail.com URL.
> at
> org.apache.axis2.description.ClientUtils.inferOutTransport(ClientUtils.java:81)
> at
> org.apache.axis2.client.OperationClient.prepareMessageContext(OperationClient.java:288)
> at
> org.apache.axis2.description.OutOnlyAxisOperationClient.executeImpl(OutOnlyAxisOperation.java:249)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
> at
> org.apache.axis2.client.ServiceClient.fireAndForget(ServiceClient.java:511)
> at
> org.apache.axis2.client.ServiceClient.fireAndForget(ServiceClient.java:488)
> at
> org.wso2.carbon.device.mgt.core.email.sender.EmailServiceProviderImpl$EmailSender.run(EmailServiceProviderImpl.java:109)
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown
> Source)
> at java.util.concurrent.FutureTask.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown
> Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
> Source)
> at java.lang.Thread.run(Unknown Source)
>
> Thanks
>
> Suresh K
> --
> *From:* Suresh Kumar
> *Sent:* Wednesday, March 23, 2016 4:24 PM
> *To:* Kamidu Punchihewa
>
> *Subject:* Re: Device Enrollment Failed - WSO2 EMM 2.0
>
>
> Thanks Sachith , I will try and i will update.
>
>
>
>
> --
> *From:* Kamidu Punchihewa <sachi...@wso2.com>
> *Sent:* Wednesday, March 23, 2016 4:16 PM
> *To:* Suresh Kumar
> *Subject:* Re: Device Enrollment Failed - WSO2 EMM 2.0
>
> Hi Suresh,
>
> Please move the mailto configuration to axis2_client.xml from axis2.xml.
>
> You can find a sample configuration given below.
>
> *
> *class="org.apache.axis2.transport.mail.MailTransportSender">*
>
> @gmail.com
>> <cdm.w...@gmail.com>*
>
> @gmail.com
>> <cdm.w...@gmail.com>*
>
> 
>
> *smtp.gmail.com
>> <http://smtp.gmail.com>*
>
> *587*
>
> *true*
>
> *true *
>
> * *
>
>
> Feel free to raise any double regarding wso2 EMM. You can utilities
> dev@wso2.org public mail to discuss any topic related to wso2 products.
>
> Thanks and Best Regards,
>
> Kamidu Sachith Punchihewa
> *Software Engineer*
> WSO2, Inc.
> lean . enterprise . middleware
> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>
>
> 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, retransmit, 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.
>
> On Wed, Mar 23, 2016 at 1:53 PM, Suresh Kumar <suresh_ku...@fulcrumww.com>
> wrote:
>
>> Hi Sachith
>>
>>
>> Nice talking with you , Let me explain the problem which i'm facing
&g

Re: [Dev] WSO2 Enterprise Mobility Manager 2.0.1 is released

[Kamidu Punchihewa]

Hi All,

Adding architecture group.

Thanks and Regards,

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Wed, Mar 16, 2016 at 11:18 AM, Kamidu Punchihewa <sachi...@wso2.com>
wrote:

> WSO2 Enterprise Mobility Manager 2.0.1 is released!
>
> WSO2 Enterprise Mobility Manager (WSO2 EMM) is a 100% open source,
> comprehensive platform that addresses mobile computing challenges which
> enterprises face today. WSO2 EMM supports iOS, Android & Windows devices
> and helps organizations deal with both "corporate-owned,
> personally-enabled" (COPE) devices and employee owned devices with the
> "bring-your-own-device" (BYOD) ownership schemes.
>
> Built on a generic device management framework (i.e. WSO2 Connected Device
> Management Framework) that can be extended to support many other device
> platforms, WSO2 EMM offers better scalability with its rich architecture,
> supporting horizontal as well as vertical scaling of associated components.
> Whether it is device configuration management, policy enforcement,
> app-management, device data security or compliance monitoring, WSO2 EMM
> offers a single enterprise grade platform for all your mobile computing
> needs.
>
>
> What features are on offer?
>
> Mobile Device Management (MDM)
>
>
>-
>
>Self-service device enrollment and management with WSO2 EMM end-user
>console for iOS, Android and Windows devices
>-
>
>Integrates to enterprise identity systems for device ownership: LDAP,
>Microsoft AD
>-
>
>Policy-driven device and profile management for security, data, and
>device features (Camera, Password Policy)
>-
>
>Deploy policies over-the-air
>-
>
>Compliance monitoring for applied policies on devices.
>-
>
>Role-based access control (RBAC) for device management
>-
>
>Securely wipe enterprise configurations using Enterprise wipe
>-
>
>Track locations of enrolled devices
>-
>
>Retrieve device information
>-
>
>Configure network settings
>-
>
>Facilitate device-owner operations such as registering and
>unregistering devices, installing, rating, sorting mobile apps, etc
>
>
> Mobile App Management
>
>
>-
>
>App approval process through a lifecycle
>-
>
>Provision and de-provisioning apps to enrolled devices
>-
>
>Provision apps to enrolled devices based on roles
>-
>
>Provision apps to multiple enrolled devices per user
>-
>
>Retrieve list of apps
>-
>
>Install new apps and update existing apps on iOS devices via REST
>APIs, enabling automation of application installation/updates for third
>party systems / vendors
>-
>
>Install Web clips on devices. Shortcuts to a web app can be installed
>on a device via this feature
>-
>
>Enterprise App Store
>-
>
>Discover mobile apps through an Enterprise App Store
>-
>
>Self-provisioning of mobile apps to devices
>-
>
>Rating and Sorting Applications
>
>
> Device and Data Security
>
>
>-
>
>Enforce built-in security features of passcode protection
>-
>
>Encryption of data storage
>-
>
>Device lock and reset
>-
>
>Managed APIs to perform administrative functions
>
>
> iOS Features
>
>
>-
>
>Self-service device enrollment and management with WSO2 EMM end-user
>console via iOS agent or Web interface for versions up to iOS 9 SDK
>-
>
>Facilitate remote notifications via Apple Push Notification Service
>(APNS)
>-
>
>New iOS Version Support
>-
>
>Tracking iOS Device
>-
>
>Configuring cellular network settings
>-
>
>Device profile management
>-
>
>Retrieving device info
>-
>
>Device lock
>-
>
>Automatic WiFi configuration
>

[Dev] WSO2 Enterprise Mobility Manager 2.0.1 is released

[Kamidu Punchihewa]

WSO2 Enterprise Mobility Manager 2.0.1 is released!

WSO2 Enterprise Mobility Manager (WSO2 EMM) is a 100% open source,
comprehensive platform that addresses mobile computing challenges which
enterprises face today. WSO2 EMM supports iOS, Android & Windows devices
and helps organizations deal with both "corporate-owned,
personally-enabled" (COPE) devices and employee owned devices with the
"bring-your-own-device" (BYOD) ownership schemes.

Built on a generic device management framework (i.e. WSO2 Connected Device
Management Framework) that can be extended to support many other device
platforms, WSO2 EMM offers better scalability with its rich architecture,
supporting horizontal as well as vertical scaling of associated components.
Whether it is device configuration management, policy enforcement,
app-management, device data security or compliance monitoring, WSO2 EMM
offers a single enterprise grade platform for all your mobile computing
needs.


What features are on offer?

Mobile Device Management (MDM)


   -

   Self-service device enrollment and management with WSO2 EMM end-user
   console for iOS, Android and Windows devices
   -

   Integrates to enterprise identity systems for device ownership: LDAP,
   Microsoft AD
   -

   Policy-driven device and profile management for security, data, and
   device features (Camera, Password Policy)
   -

   Deploy policies over-the-air
   -

   Compliance monitoring for applied policies on devices.
   -

   Role-based access control (RBAC) for device management
   -

   Securely wipe enterprise configurations using Enterprise wipe
   -

   Track locations of enrolled devices
   -

   Retrieve device information
   -

   Configure network settings
   -

   Facilitate device-owner operations such as registering and unregistering
   devices, installing, rating, sorting mobile apps, etc


Mobile App Management


   -

   App approval process through a lifecycle
   -

   Provision and de-provisioning apps to enrolled devices
   -

   Provision apps to enrolled devices based on roles
   -

   Provision apps to multiple enrolled devices per user
   -

   Retrieve list of apps
   -

   Install new apps and update existing apps on iOS devices via REST APIs,
   enabling automation of application installation/updates for third party
   systems / vendors
   -

   Install Web clips on devices. Shortcuts to a web app can be installed on
   a device via this feature
   -

   Enterprise App Store
   -

   Discover mobile apps through an Enterprise App Store
   -

   Self-provisioning of mobile apps to devices
   -

   Rating and Sorting Applications


Device and Data Security


   -

   Enforce built-in security features of passcode protection
   -

   Encryption of data storage
   -

   Device lock and reset
   -

   Managed APIs to perform administrative functions


iOS Features


   -

   Self-service device enrollment and management with WSO2 EMM end-user
   console via iOS agent or Web interface for versions up to iOS 9 SDK
   -

   Facilitate remote notifications via Apple Push Notification Service
   (APNS)
   -

   New iOS Version Support
   -

   Tracking iOS Device
   -

   Configuring cellular network settings
   -

   Device profile management
   -

   Retrieving device info
   -

   Device lock
   -

   Automatic WiFi configuration
   -

   AirPlay
   -

   Restrictions (60+ operations are supported)
   -

   Enterprise WIPE
   -

   Setup APN
   -

   Setup LDAP
   -

   Setup email accounts
   -

   Setup CalDav
   -

   Calendar subscription
   -

   Passcode policy
   -

   Clear passcode
   -

   App installation and update
   -

   Retrieve app list
   -

   Web clip installation
   -

   Supports App management
   -

   Setup email accounts
   -

   Subscribe for Calendar via iOS device with the option to auto-sync with
   the WSO2 EMM server for items and contacts via Calendaring Extensions to
   WebDAV (CalDAV)
   -

   Ring devices
   -

   Send messages


Android Features


   -

   Self-service device enrollment and management with WSO2 EMM end-user
   console via Android agent (Android 4.0.3 Ice Cream Sandwich MR1 up to 5.0
   Lollipop)
   -

   Supports App management
   -

   Device location tracking
   -

   Retrieving device info
   -

   Changing lock code
   -

   Restricting camera
   -

   OTA WiFi configuration
   -

   Enterprise WIPE
   -

   Configuring encryption settings
   -

   Pass code policy configuration and clear pass code policy
   -

   Device master reset
   -

   Mute device
   -

   Ring device
   -

   Send messages to device
   -

   Install/uninstall store and enterprise applications
   -

   Retrieve apps installed on the device
   -

   Install Web clips on the device
   -

   Support GCM/LOCAL connectivity modes


Windows Features



   -

   Self-service device enrollment and management with WSO2 EMM end-user
   console Via 'workplace' (Windows 8.1)
   -

   Passcode policy
   -

   Restriction on camera
   -

   

Re: [Dev] GSoC [CDMF] [EMM] Device Policy Merging Project for WS02

[Kamidu Punchihewa]

Hi Tchuenkam,

In order to Build WSO2 EMM you need to build the repository[1].
You can choose the  version 2.0.0 branch for the latest stable version or
the master branch which is current branch user development for the EMM
2.1.0 release.
You can find the executable in *product-mdm/modules/distribution/target.*
Please unzip the *wso2mdm-2.0.1-SNAPSHOT.zip *file.
You can find the wso2server.sh in *wso2mdm-2.0.1-SNAPSHOT/bin* directory.
Please do refer to the WSO2 EMM documentation[2] for more information.

[1] https://github.com/wso2/product-mdm
[2] https://docs.wso2.com/display/EMM200/WSO2+Enterprise+Mobility+Manager
<https://docs.wso2.com/display/EMM200/WSO2+Enterprise+Mobility+Manager>

Thanks and Best Regards,

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Sat, Mar 5, 2016 at 1:06 AM, tchuenkam ulrich <ulrichmo...@gmail.com>
wrote:

>
> Hi developer, I cloned the repo[1] as suggested and did build the whole
> system.
> Had some failed tests http://pastebin.com/urxHccnH
>
> I ended up building the system while skipping the tests.
> Reading back the instructions you gave tells me that I needed to build only
> WSO2 EMM.
>
> Given that i have a local copy of the entire repo[1], if i want to build
> only the WSO2 EMM
> repo, which folder do i reference .
>
> After building WSO2 EMM how do i go about to execute it ?
>
> While exploring the content of repo[1], I saw this subcontent[2] that
> makes mention of how
> to run WSO2 EMM. If the description here is meant for the WSO2 EMM, then
> I have a number
> of questions to ask directly.
>
> *Questions *
>
> 1 From which bin directory do i reference the *wso2server.sh or
> wso2server.bat scripts ?*
>
> [1] https://github.com/wso2/product-mdm
> [2] https://github.com/wso2/product-mdm/tree/master/modules/distribution
> Thanks
>
> On Fri, Mar 4, 2016 at 9:42 AM, tchuenkam ulrich <ulrichmo...@gmail.com>
> wrote:
>
>> Thanks for the prompt response !!!
>>
>>
>> Will go through the above instructions and revert to you !!
>>
>> On Fri, Mar 4, 2016 at 8:11 AM, Kamidu Punchihewa <sachi...@wso2.com>
>> wrote:
>>
>>> Hi Tchuenkam,
>>>
>>> Thank you for your interest in this project.
>>> In order to get a better picture of the project make sure to build WSO2
>>> EMM from the git repository [1].
>>> Enrolled a device and a publish multiple policies against the device and
>>> study the current behavior of the policies.
>>> Change the policy priority and apply changes for the devices and study
>>> the current behavior of the policies.
>>> You are expected to change the behavior a mentioned below
>>>
>>> When there are multiple policies are active for a given device,
>>> If policies contain restrictions for the same attribute/behavior from
>>> the active policies the highest priority needs to be applied.
>>>
>>> Example :
>>> Policy A : Enables camera usage, it's the current number 2 priority.
>>> Policy B : Disables camera usage,  it's the current number 1 priority.
>>> The camera must be disabled since the high priority policy dose not
>>> enables the usage of camera.
>>>
>>>
>>> If Multiple policies have restrictions over different
>>> attributes/behavior all these restrictions need to be merge and apply to
>>> the device.
>>>
>>> Example :
>>> Policy A : Disable camera usage,  it's the current number 1 priority.
>>> Policy B :  Enables camera usage and Apply a pass code pattern , it's
>>> the current number 2 priority.
>>> The camera must be disabled since the high priority policy dose not
>>> enables the usage of camera, In the same time the given pass code pattern
>>> must be active too.
>>>
>>>
>>>
>>> While working with WSO2 EMM, if you found any bugs or improvements feel
>>> free to let us know by using the oxygen tank[2].
>>>
>>>

[Dev] [IS] Unexpected Behaviour In IS When Loging.

[Kamidu Punchihewa]

Hi IS Team,

When Using an AD with multiple organisation units as the user store, users
can login with the Doman Friendly user name.
For example there are two users in two different organisation units as
given below.

   - STAFF.WSO2.COM/user
   - MOBILE.WSO2.COM/user

Both of these users can login just using "user" as the username.
Is this the expected behaviour?
If this is the expected behavior, is there a way to identify the correct
user from these two users when they use the Domain friendly username to
login?

Thanks and Best Regards.
Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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] Fwd: [Encoding Special Charactors] Throws an Character Out Of Range exception

[Kamidu Punchihewa]

Hi, Ruwan,

Currently both escape and unescape methods are depricated.IMO using
depricated methods is not advisable.
WDYT?

Thanks and Regards,

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Thu, Feb 25, 2016 at 8:11 AM, Ruwan Abeykoon <ruw...@wso2.com> wrote:

> Hi Kamidu,
> Have we tried "escape" and "unescape" described on the same article?
>
> Cheers,
>
>
> On Wed, Feb 24, 2016 at 11:44 AM, Kamidu Punchihewa <sachi...@wso2.com>
> wrote:
>
>> Hi Dakshitha/Jerad,
>>
>> Any thoughts on the above situation ?
>>
>> Thanks and Regards.
>> Kamidu Sachith Punchihewa
>> *Software Engineer*
>> WSO2, Inc.
>> lean . enterprise . middleware
>> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>>
>>
>> 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, retransmit, 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.
>>
>> -- Forwarded message --
>> From: Kamidu Punchihewa <sachi...@wso2.com>
>> Date: Mon, Feb 15, 2016 at 11:40 AM
>> Subject: [Dev][Encoding Special Charactors] Throws an Character Out Of
>> Range exception
>> To: WSO2 Developers' List <dev@wso2.org>
>>
>>
>> Hi All,
>>
>> When Encoding String including special / Latin characters throws an
>> Character Out Of Range exception when we use *encodeURIComponent and
>> decodeURIComponent* methods which was recommended to used behalf of  *escape
>> and unescape* since there are deprecated.
>> Using *escape and unescape* does not cause the above issues and Mozilla
>> Developer Network Publication[1] still encourage to use *escape and
>> unescape *alone with the *encodeURIComponent and decodeURIComponent. *
>>
>> Recommended Approach is given below.
>>
>> function utf8_to_b64(str) {
>> return window.btoa(escape(encodeURIComponent(str)));}
>> function b64_to_utf8(str) {
>> return decodeURIComponent(unescape(window.atob(str)));}
>>
>>
>> If we replace *escape and unescape with **encodeURIComponent and
>> decodeURIComponent *the functions seems recursive as given below.
>>
>> function utf8_to_b64(str) {
>> return window.btoa(encodeURIComponent(encodeURIComponent(str)));
>> }
>> function b64_to_utf8(str) {
>> return decodeURIComponent(decodeURIComponent(window.atob(str)));
>> }
>>
>> Which is the most appropriate way of utilising the above function?
>>
>> [1].https://developer.mozilla.org/en-US/docs/Web/API/WindowBase64/btoa
>>
>> Thanks & Best Regards.
>> Kamidu Sachith Punchihewa
>> *Software Engineer*
>> WSO2, Inc.
>> lean . enterprise . middleware
>> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>>
>>
>> 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, retransmit, 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
>>
>>
>
>
> --
>
> *Ruwan Abeykoon*
> *Architect,*
> *WSO2, Inc. http://wso2.com <http://wso2.com/> *
> *lean.enterprise.middleware.*
>
> email: ruw...@wso2.com
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Fwd: [Encoding Special Charactors] Throws an Character Out Of Range exception

[Kamidu Punchihewa]

Hi Dakshitha/Jerad,

Any thoughts on the above situation ?

Thanks and Regards.
Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

-- Forwarded message --
From: Kamidu Punchihewa <sachi...@wso2.com>
Date: Mon, Feb 15, 2016 at 11:40 AM
Subject: [Dev][Encoding Special Charactors] Throws an Character Out Of
Range exception
To: WSO2 Developers' List <dev@wso2.org>


Hi All,

When Encoding String including special / Latin characters throws an
Character Out Of Range exception when we use *encodeURIComponent and
decodeURIComponent* methods which was recommended to used behalf of  *escape
and unescape* since there are deprecated.
Using *escape and unescape* does not cause the above issues and Mozilla
Developer Network Publication[1] still encourage to use *escape and
unescape *alone with the *encodeURIComponent and decodeURIComponent. *

Recommended Approach is given below.

function utf8_to_b64(str) {
return window.btoa(escape(encodeURIComponent(str)));}
function b64_to_utf8(str) {
return decodeURIComponent(unescape(window.atob(str)));}


If we replace *escape and unescape with **encodeURIComponent and
decodeURIComponent *the functions seems recursive as given below.

function utf8_to_b64(str) {
return window.btoa(encodeURIComponent(encodeURIComponent(str)));
}
function b64_to_utf8(str) {
return decodeURIComponent(decodeURIComponent(window.atob(str)));
}

Which is the most appropriate way of utilising the above function?

[1].https://developer.mozilla.org/en-US/docs/Web/API/WindowBase64/btoa

Thanks & Best Regards.
Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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] [GSoC 2016] [CDMF] Calculate Device Health Status using Analytics and API Calls

[Kamidu Punchihewa]

Hi Nuwan,

According to the pm file provided you are working with a outdated version
of the master branch.Please update your fork or clone to the latest and try
again.

Thanks & Best Regards.

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Tue, Feb 23, 2016 at 5:55 PM, Nuwan Sameera <nuwansameer...@gmail.com>
wrote:

> hI,
>pom.xml file.
>
> Thanks and Regards,
> Nuwan Sameera
>
> On Tue, Feb 23, 2016 at 5:53 PM, Nuwan Sameera <nuwansameer...@gmail.com>
> wrote:
>
>> Hi,
>>
>> Error log :  "*Failed to execute goal on project
>> org.wso2.carbon.device.mgt.mobile.impl: Could not resolve dependencies for
>> project
>> org.wso2.carbon.devicemgt-plugins:org.wso2.carbon.device.mgt.mobile.impl:bundle:2.0.3-SNAPSHOT:
>> The following artifacts could not be resolved:
>> org.wso2.carbon.devicemgt:org.wso2.carbon.device.mgt.common:jar:1.0.3-SNAPSHOT,
>> org.wso2.carbon.devicemgt:org.wso2.carbon.device.mgt.extensions:jar:1.0.3-SNAPSHOT,
>> org.wso2.carbon.devicemgt:org.wso2.carbon.policy.mgt.common:jar:1.0.3-SNAPSHOT,
>> org.wso2.carbon.devicemgt:org.wso2.carbon.policy.mgt.core:jar:1.0.3-SNAPSHOT:
>> Could not find artifact
>> org.wso2.carbon.devicemgt:org.wso2.carbon.device.mgt.common:jar:1.0.3-SNAPSHOT
>> in wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/
>> <http://maven.wso2.org/nexus/content/groups/wso2-public/>*"
>>
>> On Tue, Feb 23, 2016 at 4:22 PM, Kamidu Punchihewa <sachi...@wso2.com>
>> wrote:
>>
>>> Hi Nuwan,
>>>
>>> This can be an issue with your network connection.
>>> In order to provide you with a solid solution can you provide me the the
>>> followings.
>>>
>>>- Parent POM file of the repository.
>>>- Error Log
>>>
>>> Thanks and Regards.
>>>
>>> Kamidu Sachith Punchihewa
>>> *Software Engineer*
>>> WSO2, Inc.
>>> lean . enterprise . middleware
>>> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>>>
>>>
>>> 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, retransmit, 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.
>>>
>>> On Tue, Feb 23, 2016 at 3:39 PM, Nuwan Sameera <nuwansameer...@gmail.com
>>> > wrote:
>>>
>>>> Hi,
>>>> Same error occurred. I try to build by deleting ".m2/org/wso2"
>>>> folder. Bud carbon-device-mgt-plugins given same error. Please help me.
>>>>
>>>> Thanks and Regards,
>>>> Nuwan Sameera.
>>>>
>>>> On Tue, Feb 23, 2016 at 2:09 PM, Kamidu Punchihewa <sachi...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Nirmal,
>>>>>
>>>>> Nuwan must be able to  build carbon-device-mgt-plugins master
>>>>> branch without building any other repositories.Since all the snapshot
>>>>> versions are in the snapshot nexus.Sorry for the inconvenience.
>>>>> @Nuwan, Please make sure you have an active and working network
>>>>> connection before building.In order to make sure nexus repository that
>>>>> cached in the local repository updated to the latest versions and changes
>>>>> from the nexus use *mvn clean install -U* or Use a clean local
>>>>> repository to o

Re: [Dev] [GSoC 2016] [CDMF] Calculate Device Health Status using Analytics and API Calls

[Kamidu Punchihewa]

Hi Nuwan,

This can be an issue with your network connection.
In order to provide you with a solid solution can you provide me the the
followings.

   - Parent POM file of the repository.
   - Error Log

Thanks and Regards.

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Tue, Feb 23, 2016 at 3:39 PM, Nuwan Sameera <nuwansameer...@gmail.com>
wrote:

> Hi,
> Same error occurred. I try to build by deleting ".m2/org/wso2" folder.
> Bud carbon-device-mgt-plugins given same error. Please help me.
>
> Thanks and Regards,
> Nuwan Sameera.
>
> On Tue, Feb 23, 2016 at 2:09 PM, Kamidu Punchihewa <sachi...@wso2.com>
> wrote:
>
>> Hi Nirmal,
>>
>> Nuwan must be able to  build carbon-device-mgt-plugins master
>> branch without building any other repositories.Since all the snapshot
>> versions are in the snapshot nexus.Sorry for the inconvenience.
>> @Nuwan, Please make sure you have an active and working network
>> connection before building.In order to make sure nexus repository that
>> cached in the local repository updated to the latest versions and changes
>> from the nexus use *mvn clean install -U* or Use a clean local
>> repository to overcome the above issue.
>>
>> Kamidu Sachith Punchihewa
>> *Software Engineer*
>> WSO2, Inc.
>> lean . enterprise . middleware
>> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>>
>>
>> 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, retransmit, 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.
>>
>> On Tue, Feb 23, 2016 at 11:50 AM, Kamidu Punchihewa <sachi...@wso2.com>
>> wrote:
>>
>>> Hi Nirmal,
>>>
>>> Nuwan is trying to build the master version of the repositories which
>>> includes snapshot versions which is not yet released.
>>> To avoid these Nuwan needs to use the latest release version of CDMF[1]
>>> rather than the master branch which is under development.
>>>
>>> [1] https://github.com/wso2/carbon-device-mgt/tree/v1.0.3
>>>
>>> Thanks and Regards.
>>>
>>> Kamidu Sachith Punchihewa
>>> *Software Engineer*
>>> WSO2, Inc.
>>> lean . enterprise . middleware
>>> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>>>
>>>
>>> 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, retransmit, 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.
>>>
>>> On Mon, Feb 22, 2016 at 5:22 PM, Nirmal Fernando <nir...@wso2.com>
>>> wrote:
>>>
>>>> Hi Hasunie,
>>>>
>>>> Why do we need to build these? Why aren't these jars there in Nexus?
>>>>
>>>> On Mon, Feb 22, 2016 at 5:04 PM, Hasunie Adikari <hasu...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Nuwan,
>>>>>

Re: [Dev] [GSoC 2016] [CDMF] Calculate Device Health Status using Analytics and API Calls

[Kamidu Punchihewa]

Hi Nirmal,

Nuwan must be able to  build carbon-device-mgt-plugins master
branch without building any other repositories.Since all the snapshot
versions are in the snapshot nexus.Sorry for the inconvenience.
@Nuwan, Please make sure you have an active and working network connection
before building.In order to make sure nexus repository that cached in the
local repository updated to the latest versions and changes from the nexus
use *mvn clean install -U* or Use a clean local repository to overcome the
above issue.

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Tue, Feb 23, 2016 at 11:50 AM, Kamidu Punchihewa <sachi...@wso2.com>
wrote:

> Hi Nirmal,
>
> Nuwan is trying to build the master version of the repositories which
> includes snapshot versions which is not yet released.
> To avoid these Nuwan needs to use the latest release version of CDMF[1]
> rather than the master branch which is under development.
>
> [1] https://github.com/wso2/carbon-device-mgt/tree/v1.0.3
>
> Thanks and Regards.
>
> Kamidu Sachith Punchihewa
> *Software Engineer*
> WSO2, Inc.
> lean . enterprise . middleware
> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>
>
> 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, retransmit, 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.
>
> On Mon, Feb 22, 2016 at 5:22 PM, Nirmal Fernando <nir...@wso2.com> wrote:
>
>> Hi Hasunie,
>>
>> Why do we need to build these? Why aren't these jars there in Nexus?
>>
>> On Mon, Feb 22, 2016 at 5:04 PM, Hasunie Adikari <hasu...@wso2.com>
>> wrote:
>>
>>> Hi Nuwan,
>>>
>>> First of all you need to build repositories in [1],[2],[3],[4] in
>>> mentioned order.That will be resolve the issue which you have faced.
>>>
>>>
>>> On Mon, Feb 22, 2016 at 3:12 PM, Nuwan Sameera <nuwansameer...@gmail.com
>>> > wrote:
>>>
>>>> Hi,
>>>>I tried to build carbon-device-mgt-plugins master branch. But there
>>>> is a problem.
>>>>
>>>> Following error occured.
>>>>
>>>> *""Could not resolve dependencies for project
>>>> org.wso2.carbon.devicemgt-plugins:org.wso2.carbon.device.mgt.mobile.impl:bundle:2.0.3-SNAPSHOT:
>>>> The following artifacts could not be resolved:
>>>> org.wso2.carbon.devicemgt:org.wso2.carbon.device.mgt.common:jar:1.0.3-SNAPSHOT,
>>>> org.wso2.carbon.devicemgt:org.wso2.carbon.device.mgt.extensions:jar:1.0.3-SNAPSHOT,
>>>> org.wso2.carbon.devicemgt:org.wso2.carbon.policy.mgt.common:jar:1.0.3-SNAPSHOT,
>>>> org.wso2.carbon.devicemgt:org.wso2.carbon.policy.mgt.core:jar:1.0.3-SNAPSHOT:
>>>> Failure to find
>>>> org.wso2.carbon.devicemgt:org.wso2.carbon.device.mgt.common:jar:1.0.3-SNAPSHOT
>>>> in http://maven.wso2.org/nexus/content/groups/wso2-public/
>>>> <http://maven.wso2.org/nexus/content/groups/wso2-public/> was cached in the
>>>> local repository""*
>>>>
>>>> Please help.
>>>>
>>>> Best Regards,
>>>> Nuwan Sameera.
>>>>
>>>> On Mon, Feb 22, 2016 at 9:58 AM, Nuwan Sameera <
>>>> nuwansameer...@gmail.com> wrote:
>>>>
>>>>> Hi,
>>>>>Thank You all.
>>>>>
>>>>> Regards,
>>>>> Nuwan Sameera.
>>>>>
>>>>> On Mo

Re: [Dev] [GSoC 2016] [CDMF] Calculate Device Health Status using Analytics and API Calls

[Kamidu Punchihewa]

Hi Nirmal,

Nuwan is trying to build the master version of the repositories which
includes snapshot versions which is not yet released.
To avoid these Nuwan needs to use the latest release version of CDMF[1]
rather than the master branch which is under development.

[1] https://github.com/wso2/carbon-device-mgt/tree/v1.0.3

Thanks and Regards.

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Mon, Feb 22, 2016 at 5:22 PM, Nirmal Fernando  wrote:

> Hi Hasunie,
>
> Why do we need to build these? Why aren't these jars there in Nexus?
>
> On Mon, Feb 22, 2016 at 5:04 PM, Hasunie Adikari  wrote:
>
>> Hi Nuwan,
>>
>> First of all you need to build repositories in [1],[2],[3],[4] in
>> mentioned order.That will be resolve the issue which you have faced.
>>
>>
>> On Mon, Feb 22, 2016 at 3:12 PM, Nuwan Sameera 
>> wrote:
>>
>>> Hi,
>>>I tried to build carbon-device-mgt-plugins master branch. But there
>>> is a problem.
>>>
>>> Following error occured.
>>>
>>> *""Could not resolve dependencies for project
>>> org.wso2.carbon.devicemgt-plugins:org.wso2.carbon.device.mgt.mobile.impl:bundle:2.0.3-SNAPSHOT:
>>> The following artifacts could not be resolved:
>>> org.wso2.carbon.devicemgt:org.wso2.carbon.device.mgt.common:jar:1.0.3-SNAPSHOT,
>>> org.wso2.carbon.devicemgt:org.wso2.carbon.device.mgt.extensions:jar:1.0.3-SNAPSHOT,
>>> org.wso2.carbon.devicemgt:org.wso2.carbon.policy.mgt.common:jar:1.0.3-SNAPSHOT,
>>> org.wso2.carbon.devicemgt:org.wso2.carbon.policy.mgt.core:jar:1.0.3-SNAPSHOT:
>>> Failure to find
>>> org.wso2.carbon.devicemgt:org.wso2.carbon.device.mgt.common:jar:1.0.3-SNAPSHOT
>>> in http://maven.wso2.org/nexus/content/groups/wso2-public/
>>>  was cached in the
>>> local repository""*
>>>
>>> Please help.
>>>
>>> Best Regards,
>>> Nuwan Sameera.
>>>
>>> On Mon, Feb 22, 2016 at 9:58 AM, Nuwan Sameera >> > wrote:
>>>
 Hi,
Thank You all.

 Regards,
 Nuwan Sameera.

 On Mon, Feb 22, 2016 at 9:11 AM, Milan Perera  wrote:

> Hi Nuwan,
>
> Please use the master branch since it is the latest.
>
> Thanks,
>
> On Mon, Feb 22, 2016 at 8:53 AM, Hasunie Adikari 
> wrote:
>
>> Hi Nuwan,
>>
>> Thank you for your interest in this project.You need to build
>> following repositories accordingly.
>>
>> [1] https://github.com/wso2/carbon-device-mgt
>> [2] https://github.com/wso2/carbon-device-mgt-plugins
>> [3] https://github.com/wso2/product-cdm
>> [4] https://github.com/wso2/product-mdm
>>
>>
>> On Mon, Feb 22, 2016 at 7:30 AM, Nuwan Sameera <
>> nuwansameer...@gmail.com> wrote:
>>
>>> Hello,
>>>There are many branches in carbon-device-mgt. What is the branch
>>> I need to build.
>>>
>>> Thanks
>>> Regards.
>>> Nuwan Sameera.
>>>
>>> On Sun, Feb 21, 2016 at 2:02 PM, Nuwan Sameera <
>>> nuwansameer...@gmail.com> wrote:
>>>
 Hello,

   I'm Y.G.Nuwan Sameera. I am third year student of University
 of Moratuwa. I am interesting to work above project. How I need to 
 start my
 work.

 Thanks,
 Regards,
 Nuwan Sameera.

>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Hasunie Adikari*
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>> blog http://hasuniea.blogspot.com
>> Mobile:+94715139495
>>
>> ___
>> 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
> 

Re: [Dev] [GSoC 2016][CDMF] [EMM] Location and Time-based Device Policy Enforcement

[Kamidu Punchihewa]

Hi Tharida.

Project deliverable "Extension point for current EMM policy module
with location
and time based policy publishing capability" includes followings,


   - Location based policy enforcement component.
   - A component which enables the location base policy monitoring and
  enforcements including statics.This need to be a extension to thee
  component which enabled device policies currently
   - Time based location component.
   - A component which enables the time base policy monitoring and
  enforcements including statics.This need to be a extension to thee
  component which enabled device policies currently
   - Location and time based policy configuration UI.
   - This is to enable users to configure and maintain the locations and
  time frames.The UI must have the ability to monitor the policies which is
  active in the device and compliance status.Above features must follow the
  current pattern used for policy monitoring and Policy Management in WSO2
  EMM.

Thanks and Best Regards.

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Mon, Feb 22, 2016 at 11:52 AM, Tharinda Ehelepola <tharinda...@gmail.com>
wrote:

> Hi Kamidu,
>
> Thanks for the quick response. Now I have a brief idea about project
> scope. Can I know about the deliverable in the project. It is not that much
> clear for me.
>
> Thanks and Regards,
> Tharinda.
>
> On Mon, Feb 22, 2016 at 11:45 AM, Tharinda Ehelepola <tharin...@wso2.com>
> wrote:
>
>
>> -- Forwarded message --
>> From: Kamidu Punchihewa <sachi...@wso2.com>
>> Date: Mon, Feb 22, 2016 at 10:25 AM
>> Subject: Re: [Dev][GSoC 2016][CDMF] [EMM] Location and Time-based Device
>> Policy Enforcement
>> To: Tharinda Ehelepola <tharin...@wso2.com>
>> Cc: dev <dev@wso2.org>, Kasun Dananjaya Delgolla <kas...@wso2.com>,
>> Prabath Abeysekera <praba...@wso2.com>, Geeth Munasinghe <ge...@wso2.com>
>>
>>
>> Hi Tharinda
>>
>> Thank you for your interest in this project.
>> In order to get a better picture of the project make sure to build WSO@
>> EMM including CDMF framework using the git repositories listed in [1], [2]
>> and [3] in the mentioned order.
>> Enrolled a device and a publish a sample policy against the device and
>> study the current behavior of the policy.
>> You are expected to change the behavior a mentioned below.
>>
>> Given policy must be activated automatically when the device enters a
>> predefined area.
>> Given policy must be deactivated when a device leaves a predefined area.
>> Given policy must be activated automatically in the given time frame.
>> Stats of the current policy, whether its active or inactive need to be
>> visible in the dashboard.
>> Policy compliance monitoring to the given device must be activated when a
>> policy is activated.
>>
>> While working with WSO2 EMM, if you found any bugs or improvements feel
>> free to let us know by using the oxygen tank[4].
>>
>> [1] https://github.com/wso2/carbon-device-mgt
>> [2] https://github.com/wso2/carbon-device-mgt-plugins
>> [3] https://github.com/wso2/product-mdm
>> [4] https://wso2.org/jira/secure/Dashboard.jspa
>>
>> Thanks and Best Regards.
>>
>> Kamidu Sachith Punchihewa
>> *Software Engineer*
>> WSO2, Inc.
>> lean . enterprise . middleware
>> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>>
>>
>> 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, retransmit, disseminate, or otherwise use the information
>> contained in this communication. Internet communications ca

Re: [Dev] [GSoC 2016][CDMF] [EMM] Location and Time-based Device Policy Enforcement

[Kamidu Punchihewa]

Hi Tharinda

Thank you for your interest in this project.
In order to get a better picture of the project make sure to build WSO@ EMM
including CDMF framework using the git repositories listed in [1], [2] and
[3] in the mentioned order.
Enrolled a device and a publish a sample policy against the device and
study the current behavior of the policy.
You are expected to change the behavior a mentioned below.

Given policy must be activated automatically when the device enters a
predefined area.
Given policy must be deactivated when a device leaves a predefined area.
Given policy must be activated automatically in the given time frame.
Stats of the current policy, whether its active or inactive need to be
visible in the dashboard.
Policy compliance monitoring to the given device must be activated when a
policy is activated.

While working with WSO2 EMM, if you found any bugs or improvements feel
free to let us know by using the oxygen tank[4].

[1] https://github.com/wso2/carbon-device-mgt
[2] https://github.com/wso2/carbon-device-mgt-plugins
[3] https://github.com/wso2/product-mdm
[4] https://wso2.org/jira/secure/Dashboard.jspa

Thanks and Best Regards.

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Sun, Feb 21, 2016 at 10:28 PM, Tharinda Ehelepola 
wrote:

> Hi,
>
> I am Tharinda Ehelepola, a final year undergraduate at Faculty of
> Engineering, University of Peradeniya and currently in my internship at
> Wso2. I am very much interesting about this project and I have some
> experience about EMM server and its policies.
>
> I would like to know more details about the project and deliverable.
>
> Thanks and Regards,
> Tharinda.
> --
>
> *Tharinda Ehelepola*
>
> *Software Engineering Intern*
> LinkedIn 
> TP :  94711834769
> Email: tharin...@wso2.com
> Blog: tharindaehelepola.blogspot.com/
> Web: tharinda.tk
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [EMM]Release progress update EMM 2.0.1

[Kamidu Punchihewa]

 'Publisher'
   - [EMM-1208 <https://wso2.org/jira/browse/EMM-1208>] - Loading dialog
   box should be moved to the appropriate context in list views
   - [EMM-1233 <https://wso2.org/jira/browse/EMM-1233>] - Remove all 
   from button spacing
   - [EMM-1158 <https://wso2.org/jira/browse/EMM-1158>] - Search option is
   missing for operations log

Improvement

   - [EMM-1219 <https://wso2.org/jira/browse/EMM-1219>] - Add Role function
   should be made as a wizard where to have permission settings coupled in the
   same flow
   - [EMM-1220 <https://wso2.org/jira/browse/EMM-1220>] - Role permission
   list should be restructured to have a meaningful set of permissions



*Jiras to be Completed*
Bug

   - [EMM-1231 <https://wso2.org/jira/browse/EMM-1231>] - Action of the
   enroll device on the app bar should be moved to appropriate position.

Improvement

   - [EMM-1200 <https://wso2.org/jira/browse/EMM-1200>] - On small screens,
   detailed view of the menu items not get listed under relevant area
   - [EMM-1202 <https://wso2.org/jira/browse/EMM-1202>] - Improve to behave
   policy view list as a policy priority list.
   - [EMM-1215 <https://wso2.org/jira/browse/EMM-1215>] - Operation dialog
   should be improved to be flexible for customization.
   - [EMM-1221 <https://wso2.org/jira/browse/EMM-1221>] - Loading icon and
   font are taking long time to fully loaded.
   - [EMM-1223 <https://wso2.org/jira/browse/EMM-1223>] - Error
   messages/Dialog boxes should be shown properly in a responsive way
   - [EMM-1226 <https://wso2.org/jira/browse/EMM-1226>] - Policy priority
   list view should be restructured according to the different display
   resolution.


Thanks & Best Regards.

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Mon, Feb 1, 2016 at 11:21 AM, Kamidu Punchihewa <sachi...@wso2.com>
wrote:

> Hi,
>
> Currently we are planning to release EMM 2.0.1-RC1 on the 12th of February.
> This release will include fixes and enhancements in the following
> components.9
>
>- UI/UX enhancements in User interface.
>- Known Issues in Mobile Application Management.
>- Known Issues in CDMF.
>
>
> The Progress is Listed Below.
> *Completed Jiras*
> Bug
>
>- [EMM-918 <https://wso2.org/jira/browse/EMM-918>] - Validation
>criteria for user information should be consistent in both carbon
>management console and MDM dashboard
>- [EMM-1132 <https://wso2.org/jira/browse/EMM-1132>] -
>'Application/' user roles should not be listed under roles in
>'Enterprise Install' UI
>- [EMM-1176 <https://wso2.org/jira/browse/EMM-1176>] - Unable to
>perform user role edit, when user role name contains spaces
>- [EMM-1183 <https://wso2.org/jira/browse/EMM-1183>] - Search policies
>by role name contains a blank field as search property
>- [EMM-1190 <https://wso2.org/jira/browse/EMM-1190>] - Unable to
>perform user edit, when username contains spaces
>- [EMM-1191 <https://wso2.org/jira/browse/EMM-1191>] - Need to add
>validation for user(s) and role(s) filed in policy creation and
>modification.
>- [EMM-1198 <https://wso2.org/jira/browse/EMM-1198>] - When scrolling
>down, there's a shaky effect in the UI
>- [EMM-1199 <https://wso2.org/jira/browse/EMM-1199>] - If Users/Roles
>are not assigned for the relevent policy. It should be hidden in the Policy
>list view.
>- [EMM-1201 <https://wso2.org/jira/browse/EMM-1201>] - In edit user
>view, required asterisk is not required for username field
>- [EMM-1203 <https://wso2.org/jira/browse/EMM-1203>] - Change buttons
>visibility based on the content availability
>- [EMM-1209 <https://wso2.org/jira/browse/EMM-1209>] - If there are no
>devices enrolled,Device view icon should be hidden in the dashboard.
>- [EMM-1213 <https://wso2.org/jira/browse/EMM-1213>] - Remove "from
>EMM User Store" wording and change to a meaningful text.
>- [EMM-1217 <https://wso2.org/jira/browse

Re: [Dev] [DEV][UI/UX] Data Table Extended Prompt An Alert When Filtering Data

[Kamidu Punchihewa]

Hi Jerad,

Since we are using the data table extended library and its filtering option
where backend ajax option is enabled.We don't have the access to perform
the suggestion you have provided.
Which is "if this is causing any issue for back-end processing. We should
handle it from the back-end or* before we make the back-end cal*l".

Handling the css selectors which is appended from one particular UI library
from a published backend API is not the best practise to follow.
Sending css selectors to a backend api via the library is not the advisable
either.

We should  address this and enable the backend filtering without the "^",
"$" or any css and frontend related characters/selectors from the  data
table extended library.

Thanks and Regards.

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Tue, Feb 16, 2016 at 8:22 AM, Jerad Rutnam <je...@wso2.com> wrote:

> Hi Kamidu,
>
> This is to fix *exact *match filtering in front-end level. "^" for starts
> and "$" for ends with, for more details check html selectors [1].
>
> e.g. This will fix the issue where it shows "in*active*" queries when we
> filter for "*active*".
>
> And if this is causing any issue for back-end processing. We should handle
> it from the back-end or before we make the back-end call.
>
> [1] - http://www.w3schools.com/cssref/css_selectors.asp
>
> Cheers!
> Jerad
>
>
> On Mon, Feb 15, 2016 at 9:05 PM, Kamidu Punchihewa <sachi...@wso2.com>
> wrote:
>
>> Hi UI/UX Team,
>>
>> I have faced $subject when fitting data using the ajax method.
>> An "IllegalArgumentException" was thoun in the back end, and a datatable
>> error alert was prompt from the front end when a filtering was triggered.
>>
>> There was a mismatch in the expected uri format and the current uri
>> format given by the data table extended library.When comparing expected
>> backend call [1] with current backend call [2] there were two extra
>> characters included to the current uri.
>>
>> This causes due to the latest change which is listed below.
>>
>> Older version :
>>
>> column
>>>
>>> .search(val ? val : '', true, false)
>>>
>>> .draw();
>>>
>>>
>> New version :
>>
>> column
>>> .search(val ? '^' + val + '$' : '', true, false)
>>> .draw();
>>
>>
>>
>> Any reason for this latest change ?
>>
>> [1].  'endpoint?draw=2=0=16*=data'*
>> [2].  'endpoint?draw=2=0=16*=^data$'*
>>
>> Thanks and Regards.
>> Kamidu Sachith Punchihewa
>> *Software Engineer*
>> WSO2, Inc.
>> lean . enterprise . middleware
>> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>>
>>
>> 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, retransmit, 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
>>
>>
>
>
> --
> *Jerad Rutnam*
> *Software Engineer*
>
> WSO2 Inc.
> lean | enterprise | middleware
> M : +94 77 959 1609 | E : je...@wso2.com | W : www.wso2.com
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][UI/UX] Data Table Extended Prompt An Alert When Filtering Data

[Kamidu Punchihewa]

Hi UI/UX Team,

I have faced $subject when fitting data using the ajax method.
An "IllegalArgumentException" was thoun in the back end, and a datatable
error alert was prompt from the front end when a filtering was triggered.

There was a mismatch in the expected uri format and the current uri format
given by the data table extended library.When comparing expected backend
call [1] with current backend call [2] there were two extra characters
included to the current uri.

This causes due to the latest change which is listed below.

Older version :

column
>
> .search(val ? val : '', true, false)
>
> .draw();
>
>
New version :

column
> .search(val ? '^' + val + '$' : '', true, false)
> .draw();



Any reason for this latest change ?

[1].  'endpoint?draw=2=0=16*=data'*
[2].  'endpoint?draw=2=0=16*=^data$'*

Thanks and Regards.
Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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

[Dev] [Encoding Special Charactors] Throws an Character Out Of Range exception

[Kamidu Punchihewa]

Hi All,

When Encoding String including special / Latin characters throws an
Character Out Of Range exception when we use *encodeURIComponent and
decodeURIComponent* methods which was recommended to used behalf of  *escape
and unescape* since there are deprecated.
Using *escape and unescape* does not cause the above issues and Mozilla
Developer Network Publication[1] still encourage to use *escape and
unescape *alone with the *encodeURIComponent and decodeURIComponent. *

Recommended Approach is given below.

function utf8_to_b64(str) {
return window.btoa(escape(encodeURIComponent(str)));}
function b64_to_utf8(str) {
return decodeURIComponent(unescape(window.atob(str)));}


If we replace *escape and unescape with **encodeURIComponent and
decodeURIComponent *the functions seems recursive as given below.

function utf8_to_b64(str) {
return window.btoa(encodeURIComponent(encodeURIComponent(str)));
}
function b64_to_utf8(str) {
return decodeURIComponent(decodeURIComponent(window.atob(str)));
}

Which is the most appropriate way of utilising the above function?

[1].https://developer.mozilla.org/en-US/docs/Web/API/WindowBase64/btoa

Thanks & Best Regards.
Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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

[Dev] [EMM]Release progress update EMM 2.0.1

[Kamidu Punchihewa]

Hi,

Currently we are planning to release EMM 2.0.1-RC1 on the 12th of February.
This release will include fixes and enhancements in the following
components.9

   - UI/UX enhancements in User interface.
   - Known Issues in Mobile Application Management.
   - Known Issues in CDMF.


The Progress is Listed Below.
*Completed Jiras*
Bug

   - [EMM-918 ] - Validation criteria
   for user information should be consistent in both carbon management console
   and MDM dashboard
   - [EMM-1132 ] -
   'Application/' user roles should not be listed under roles in
   'Enterprise Install' UI
   - [EMM-1176 ] - Unable to perform
   user role edit, when user role name contains spaces
   - [EMM-1183 ] - Search policies
   by role name contains a blank field as search property
   - [EMM-1190 ] - Unable to perform
   user edit, when username contains spaces
   - [EMM-1191 ] - Need to add
   validation for user(s) and role(s) filed in policy creation and
   modification.
   - [EMM-1198 ] - When scrolling
   down, there's a shaky effect in the UI
   - [EMM-1199 ] - If Users/Roles
   are not assigned for the relevent policy. It should be hidden in the Policy
   list view.
   - [EMM-1201 ] - In edit user
   view, required asterisk is not required for username field
   - [EMM-1203 ] - Change buttons
   visibility based on the content availability
   - [EMM-1209 ] - If there are no
   devices enrolled,Device view icon should be hidden in the dashboard.
   - [EMM-1213 ] - Remove "from EMM
   User Store" wording and change to a meaningful text.
   - [EMM-1217 ] - Change add
   buttons to "Save" and edit buttons to "Update" in Add/Edit forms
   - [EMM-1227 ] - Login button and
   title text should be similar
   - [EMM-1230 ] - Policy publish
   text should be changed

Improvement

   - [EMM-1178 ] - Validations to
   user role and user name should be configurable
   - [EMM-1212 ] - Operation
   requseting time should not have milliseconds value in operation log
   - [EMM-1216 ] - Improve role
   create/edit interfaces
   - [EMM-1218 ] - Platform boxes
   should be similar in policy creation wizard.
   - [EMM-1221 ] - Loading icon and
   font are taking long time to fully loaded.
   - [EMM-1222 ] - Footer web
   address (wso2.org) should be changed to a link.
   - [EMM-1224 ] - Assign
   users/roles selection boxes should be validated in Policy creation.


*Jiras In Progress*
Bug

   - [EMM-1147 ] - Exception when
   user clicks sign out button in 'Store' and 'Publisher'
   - [EMM-1208 ] - Loading dialog
   box should be moved to the appropriate context in list views

Improvement

   - [EMM-1166 ] - Capitals used in
   certain notifications, UI labels, etc need to be removed
   - [EMM-1195 ] - List View
   contains some unwanted white spaces.
   - [EMM-1196 ] - Apply changes
   button should be moved to the policy list view/priority view with a proper
   message.
   - [EMM-1207 ] - Required Field
   should be indicated using one method.
   - [EMM-1210 ] - Enable inline
   validation if possible
   - [EMM-1211 ] - Usage of
   placeholder text need to be valid


*Jiras to be Completed*
Bug

   - [EMM-1231 ] - Action of the
   enroll device on the app bar should be moved to appropriate position.
   - [EMM-1232 ] - If there are no
   any data,pagination controls should not be visible.
   - [EMM-1233 ] - Remove all 
   from button spacing

Improvement

   - [EMM-1200 ] - On small screens,
   detailed view of the menu items not get listed under relevant area
   - [EMM-1202 ] - Improve to behave
   policy view list as a policy priority list.
   - [EMM-1214 ] 

Re: [Dev] [VOTE] Release WSO2 Enterprise Mobility Manager 2.0.0 RC3

[Kamidu Punchihewa]

Hi all,

I have tested the following scenarios in EMM web app in a standalone setup
using the default user store and a secondary user store.

   - Created a role
  - Update a role
  - Rove existing roles
  - Manage permissions to a role
  - Created an user
  - Edited the user's details and saved
  - Invited the user via email
  - Read the enrollment URL via QR code
  - Removed the user
  - Changed the password
  - Manage Platform Configuration
  - Create a Policy
  - Edited the Policy
  - Modified Policy priority
  - Users and roles search

No issues found.
*My vote : [x] - Stable - Go ahead and release*

Thanks & Regards

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Mon, Jan 4, 2016 at 4:50 PM, Prabath Abeysekera 
wrote:

> Hi Devs,
>
> This is the third release candidate of WSO2 Enterprise Mobility Manager
> 2.0.0.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12592
>
> Please download, test and vote.
>
> Source & binary distribution files:
> https://github.com/wso2/product-mdm/releases/tag/v2.0.0-RC3
>
> The tag to be voted upon:
> https://github.com/wso2/product-mdm/tree/v2.0.0-RC3
>
> Known issues
> https://wso2.org/jira/issues/?filter=12593
>
>
> [ ]  Stable - go ahead and release
> [ ]  Broken - do not release (explain why)
>
>
> Thanks and Regards,
> EMM/IoTS Team
>
> --
> Prabath Abeysekara
> Technical Lead
> WSO2 Inc.
> Email: praba...@wso2.com
> Mobile: +94774171471
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Enterprise Mobility Manager 2.0.0 RC2

[Kamidu Punchihewa]

Hi all,

I have tested the following scenarios in EMM web app in a standalone setup.
Created a role
Update a role
Assigned permissions to the role

Created an user
Edited the user's details and saved

Invited the user via email
Read the enrollment URL via QR code
Removed the user
Edited the role
Removed the role
Create a Policy
Edited the Policy
No issues found. 
My vote : [x] - Stable - Go ahead and release 


Thanks & Regards

-Original Message-
From: "Geeth Munasinghe" 
Sent: ‎12/‎24/‎2015 12:49 AM
To: "dev" 
Subject: [Dev] [VOTE] Release WSO2 Enterprise Mobility Manager 2.0.0 RC2

Hi Devs,


This is the second release candidate of WSO2 Enterprise Mobility Manager 2.0.0. 


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


Please download, test and vote.


Source & binary distribution files:
https://github.com/wso2/product-mdm/releases/tag/v2.0.0-RC2


The tag to be voted upon:
https://github.com/wso2/product-mdm/tree/v2.0.0-RC2



Known issues
https://wso2.org/jira/issues/?filter=12593





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




Thanks and Regards,
EMM Server Team








G. K. S. Munasinghe

Senior Software Engineer,
WSO2, Inc. http://wso2.com 
lean.enterprise.middleware.


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

Re: [Dev] [DEV][IS] Getting an Unique index or primary key violation exception.

[Kamidu Punchihewa]

Hi IS Team.

The above error occurs in the 1st token expiration time also,with on device
calling a singleton token refreshing call to IS.
This happens when EMM android agent try to acquire a new set of token on
the access token expiry using the refresh token grant.

This Issue Started after the IS version bump from 5.0.3-SNAPSHOT  to 5.0.3.

Code Snippet which initiate communication with IS is given below.








*var xMLHttpRequest = new XMLHttpRequest();var tokenEndpoint =
mdmProps.idPServer + "/oauth2/token";xMLHttpRequest.open("POST",
tokenEndpoint, false);xMLHttpRequest.setRequestHeader("Content-Type",
"application/x-www-form-urlencoded");xMLHttpRequest.setRequestHeader("Authorization",
"Basic " + clientData);var url = "grant_type=refresh_token_token="
+ tokenPair.refreshToken;if (scope) {*

*url = url + "=" + scope*



*}xMLHttpRequest.send(url);*

Thanks & Best Regards.

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Wed, Dec 16, 2015 at 3:15 PM, Kamidu Punchihewa <sachi...@wso2.com>
wrote:

> Hi Johann/IS Team,
>
> As per the discussion i had offline earlier above exception occurred under
> heavy loads.
>
> The above exception occurred without any high loads in the system.
> When one devices logged in for some time, without any concurrent calls to
> IS, this exception is given to the device.
> Any idea why this happens with one device acting alone.
>
> Thanks and Regards.
>
> Kamidu Sachith Punchihewa
> *Software Engineer*
> WSO2, Inc.
> lean . enterprise . middleware
> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>
>
> 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, retransmit, 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.
>
> On Wed, Dec 16, 2015 at 12:13 PM, Kamidu Punchihewa <sachi...@wso2.com>
> wrote:
>
>> Hi IS team,
>>
>>
>> I am getting a "Unique index or primary key violation" exception when
>> trying to refresh the access token with the refresh token grant type. The
>> error log is given below.
>>
>> As per the discussion I had offline with Johann, this seems to be a known
>> issue which could occur when tested with a high load of concurrent calls.
>> But in my case it was only just 4 connections attempting to refresh tokens
>> concurrently.
>> Even though the exception is thrown, a new token pair can be generated by
>> sending another few calls.
>>
>> The issue is the exception which is visible in the log.In a production
>> environment, since this exception is thrown in the IS back-end, it would be
>> a bit odd to the user to see an exception in the EMM console.
>>
>> WDUT?
>>
>>
>> Error Log :
>>
>> [2015-11-26 11:27:42,093] ERROR
>>> {org.wso2.carbon.webapp.authenticator.framework.WebappAuthenticationValve}
>>> -  Access token has expired , API : /mdm-android-agent/operation/device-info
>>> [2015-11-26 11:27:42,190] ERROR
>>> {org.wso2.carbon.webapp.authenticator.framework.WebappAuthenticationValve}
>>> -  Access token has expired , API : /mdm-admin/notifications/NEW
>>> [2015-11-26 11:27:42,299] ERROR
>>> {org.wso2.carbon.identity.oauth2.OAuth2Service} -  Error occurred while
>>> issuing the access token for Client ID : CJo5Izhh4aziaMV1gAKN8fovcpka, User
>>> ID null, Scope : [] and Grant Type : refresh_token
>>> org.wso2.carbon.identity.oauth2.IdentityOAuth2Exception: Error when

Re: [Dev] [DEV][IS] Getting an Unique index or primary key violation exception.

[Kamidu Punchihewa]

Hi Johann/IS Team,

As per the discussion i had offline earlier above exception occurred under
heavy loads.

The above exception occurred without any high loads in the system.
When one devices logged in for some time, without any concurrent calls to
IS, this exception is given to the device.
Any idea why this happens with one device acting alone.

Thanks and Regards.

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Wed, Dec 16, 2015 at 12:13 PM, Kamidu Punchihewa <sachi...@wso2.com>
wrote:

> Hi IS team,
>
>
> I am getting a "Unique index or primary key violation" exception when
> trying to refresh the access token with the refresh token grant type. The
> error log is given below.
>
> As per the discussion I had offline with Johann, this seems to be a known
> issue which could occur when tested with a high load of concurrent calls.
> But in my case it was only just 4 connections attempting to refresh tokens
> concurrently.
> Even though the exception is thrown, a new token pair can be generated by
> sending another few calls.
>
> The issue is the exception which is visible in the log.In a production
> environment, since this exception is thrown in the IS back-end, it would be
> a bit odd to the user to see an exception in the EMM console.
>
> WDUT?
>
>
> Error Log :
>
> [2015-11-26 11:27:42,093] ERROR
>> {org.wso2.carbon.webapp.authenticator.framework.WebappAuthenticationValve}
>> -  Access token has expired , API : /mdm-android-agent/operation/device-info
>> [2015-11-26 11:27:42,190] ERROR
>> {org.wso2.carbon.webapp.authenticator.framework.WebappAuthenticationValve}
>> -  Access token has expired , API : /mdm-admin/notifications/NEW
>> [2015-11-26 11:27:42,299] ERROR
>> {org.wso2.carbon.identity.oauth2.OAuth2Service} -  Error occurred while
>> issuing the access token for Client ID : CJo5Izhh4aziaMV1gAKN8fovcpka, User
>> ID null, Scope : [] and Grant Type : refresh_token
>> org.wso2.carbon.identity.oauth2.IdentityOAuth2Exception: Error when
>> storing the access token for consumer key : CJo5Izhh4aziaMV1gAKN8fovcpka
>> at
>> org.wso2.carbon.identity.oauth2.dao.TokenMgtDAO.storeAccessToken(TokenMgtDAO.java:245)
>> at
>> org.wso2.carbon.identity.oauth2.dao.TokenMgtDAO.invalidateAndCreateNewToken(TokenMgtDAO.java:1103)
>> at
>> org.wso2.carbon.identity.oauth2.token.handlers.grant.RefreshGrantHandler.issue(RefreshGrantHandler.java:246)
>> at
>> org.wso2.carbon.identity.oauth2.token.AccessTokenIssuer.issue(AccessTokenIssuer.java:186)
>> at
>> org.wso2.carbon.identity.oauth2.OAuth2Service.issueAccessToken(OAuth2Service.java:196)
>> at
>> org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.getAccessToken(OAuth2TokenEndpoint.java:273)
>> at
>> org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.issueAccessToken(OAuth2TokenEndpoint.java:115)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at
>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:188)
>> at
>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:104)
>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:204)
>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:101)
>> at
>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
>> at
>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:94)
>> at
>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
>> at
>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>> at
>> org.apache.cx

[Dev] [DEV][IS] Getting an Unique index or primary key violation exception.

[Kamidu Punchihewa]

Hi IS team,


I am getting a "Unique index or primary key violation" exception when
trying to refresh the access token with the refresh token grant type. The
error log is given below.

As per the discussion I had offline with Johann, this seems to be a known
issue which could occur when tested with a high load of concurrent calls.
But in my case it was only just 4 connections attempting to refresh tokens
concurrently.
Even though the exception is thrown, a new token pair can be generated by
sending another few calls.

The issue is the exception which is visible in the log.In a production
environment, since this exception is thrown in the IS back-end, it would be
a bit odd to the user to see an exception in the EMM console.

WDUT?


Error Log :

[2015-11-26 11:27:42,093] ERROR
> {org.wso2.carbon.webapp.authenticator.framework.WebappAuthenticationValve}
> -  Access token has expired , API : /mdm-android-agent/operation/device-info
> [2015-11-26 11:27:42,190] ERROR
> {org.wso2.carbon.webapp.authenticator.framework.WebappAuthenticationValve}
> -  Access token has expired , API : /mdm-admin/notifications/NEW
> [2015-11-26 11:27:42,299] ERROR
> {org.wso2.carbon.identity.oauth2.OAuth2Service} -  Error occurred while
> issuing the access token for Client ID : CJo5Izhh4aziaMV1gAKN8fovcpka, User
> ID null, Scope : [] and Grant Type : refresh_token
> org.wso2.carbon.identity.oauth2.IdentityOAuth2Exception: Error when
> storing the access token for consumer key : CJo5Izhh4aziaMV1gAKN8fovcpka
> at
> org.wso2.carbon.identity.oauth2.dao.TokenMgtDAO.storeAccessToken(TokenMgtDAO.java:245)
> at
> org.wso2.carbon.identity.oauth2.dao.TokenMgtDAO.invalidateAndCreateNewToken(TokenMgtDAO.java:1103)
> at
> org.wso2.carbon.identity.oauth2.token.handlers.grant.RefreshGrantHandler.issue(RefreshGrantHandler.java:246)
> at
> org.wso2.carbon.identity.oauth2.token.AccessTokenIssuer.issue(AccessTokenIssuer.java:186)
> at
> org.wso2.carbon.identity.oauth2.OAuth2Service.issueAccessToken(OAuth2Service.java:196)
> at
> org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.getAccessToken(OAuth2TokenEndpoint.java:273)
> at
> org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.issueAccessToken(OAuth2TokenEndpoint.java:115)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:188)
> at
> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:104)
> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:204)
> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:101)
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:94)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> at
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:249)
> at
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:248)
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:222)
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:153)
> at
> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:171)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:289)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:209)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:265)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at
> org.wso2.carbon.ui.filters.CRLFPreventionFilter.doFilter(CRLFPreventionFilter.java:59)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
> 

Re: [Dev] How to get Maven Home for java implementation

[Kamidu Punchihewa]

Hi Nuwan,

System.getenv() is working fine with windows environment but not so well in
linux environments.
Please utilize System.getProperty() and check again.

If the above change didn't work try getting all the available properties
using the code given below.

public static void main(String[] args) {
> RuntimeMXBean runtimeBean = ManagementFactory.getRuntimeMXBean();
>
> Map systemProperties =
> runtimeBean.getSystemProperties();
> Set keys = systemProperties.keySet();
> for (String key : keys) {
> String value = systemProperties.get(key);
> System.out.printf("[%s] = %s.\n", key, value);
> }
> }

If you can't not see the $M2_HOME in the property list that means the
system property is not set in the scope where java searches for the system
variables.

Hope this wil solve the issue.

Note: Its better if you can set the $M2_HOME home in /etc/environments
rather then ~/.bashrc. Since /etc/environment does not depend on the logged
user.

Thanks and Regards.

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Mon, Dec 14, 2015 at 12:00 PM, Nuwan Pallewela  wrote:

> Hi Devs,
>
> I need to get the *Maven Home* value to execute maven goal
> eclipse:eclipse for a created project. I tried to use *java.lang.System*
> class to retrieve it by executing following code. But Maven Home in not
> listed in there either properties or process environment.
>
> if (System.getenv("M2_HOME") != null) {
> return System.getenv("M2_HOME");
> } else if (System.getenv("MAVEN_HOME") != null) {
> return System.getenv("MAVEN_HOME");
> } else if (System.getenv("M3_HOME") != null) {
> return System.getenv("M3_HOME");
> } else if (System.getProperty("maven.home") != null) {
> return System.getProperty("maven.home");
> } else {
> log.error("Maven Home variable value is not found in system
> properties");
> throw new IllegalStateException("Maven Home variable is not
> set ");
> }
>
> Maven is correctly installed in the system and following is the result
> when I run "mvn --version"
>
> nuwan@nuwan-ThinkPad-T540p:~$ mvn --version
> Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1;
> 2014-12-14T22:59:23+05:30)
> Maven home: /usr/local/apache-maven-3.2.5
> Java version: 1.8.0_66, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-8-oracle/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.13.0-68-generic", arch: "amd64", family:
> "unix"
>
> I have also had edit the .bashrc file by adding following lines.
>
> export M2_HOME=/usr/local/apache-maven-3.2.5
> export M2=$M2_HOME/bin
> export PATH=$M2/bin:$PATH
>
> But still I can't read M2_HOME from java.lang.System class.
>
> Any help would be hugely appreciated.
>
> Thanks,
> Nuwan
>
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com *
> Mobile  *+94719079739 <%2B94719079739>@*
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Jaggery] Sending errors without sending the apache internal server page

[Kamidu Punchihewa]

Hi All,

I have a requirement of sending a backend error as a responseText which
holds an error message and response status which holds the error code.
I have tried using response.sendError() but it sends the apache tomcat
server page as the response.
Any other way I can achieve this?

The current way of sending error message and code as json object results in
errors and bad requests also receive with status 200 with the error code in
the responseText.

Thanks and Regards.

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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] Displaying the username & email of users in EMM console

[Kamidu Punchihewa]

Hi Jerad,

In EMM, user's name is visible without any label. Additionally the user
name and the email also is given.
Find the attach screen capture as a sample.


So the above mentioned issue will be resolved.Wec an either replace the
labels Username: and Email with meaningful icons or add a button which
prompt a layover containing these details to the user on click.
WDYT?

Thanks and Regards.
​
Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Fri, Nov 6, 2015 at 9:19 AM, Jerad Rutnam <je...@wso2.com> wrote:

> Hi Kamidu,
>
> Agreed that EMM is an end user application. So yes, if you get something
> like *@ *along with an email address will confuse the
> user. But since this is an end user application, showing the username
> like *@ *seems wrong to me. Here we should actually show
> a Display Name (ex:- Jerad Rutnam) and we should prevent special characters
> there, otherwise this will confuse the user. WDYT?
>
> So if we have a special use case like this, then yes we can use icons to
> avoid misleading the user.
>
> Cheers,
> Jerad
>
> On Thu, Nov 5, 2015 at 10:45 PM, Kamidu Punchihewa <sachi...@wso2.com>
> wrote:
>
>> Hi Jerad,
>>
>> What you are saying is True .But i feel like we need to indicate these
>> specially when come to scenarios where the username also an email or looks
>> like an image.
>> In my previous experience i had experience with the server where it gives
>> the user name as *@*.In cases like that user might feel
>> like there are two emails.Since EMM is an end user application we need to
>> make it less complicated as possible.
>> This is just an opinion we can get all the ideas and come with the nice
>> final design.Finally we need what makes EMM better right.
>>
>> Cheers
>>
>> Kamidu Sachith Punchihewa
>> *Software Engineer*
>> WSO2, Inc.
>> lean . enterprise . middleware
>> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>>
>>
>> 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, retransmit, 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.
>>
>> On Thu, Nov 5, 2015 at 11:18 AM, Jerad Rutnam <je...@wso2.com> wrote:
>>
>>> Hi Kamidu,
>>>
>>> It's a good idea. But I feels it will looks bit clutter since we have
>>> the action icons. And even for an icon it will take some space. WDYT?
>>>
>>> Cheers!
>>> Jerad
>>>
>>> On Thu, Nov 5, 2015 at 10:09 AM, Harshan Liyanage <hars...@wso2.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Prabath also had a similar idea. That's also a good suggestion. So lets
>>>> get the feedback from UX team.
>>>>
>>>> Thanks,
>>>>
>>>> Harshan Liyanage
>>>> Software Engineer
>>>> Mobile: *+94724423048*
>>>> Email: hars...@wso2.com
>>>> Blog : http://harshanliyanage.blogspot.com/
>>>> *WSO2, Inc. :** wso2.com <http://wso2.com/>*
>>>> lean.enterprise.middleware.
>>>>
>>>> On Thu, Nov 5, 2015 at 10:06 AM, Kamidu Punchihewa <sachi...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> +1 for both ideas.
>>>>> What if we replace the lable user name and email to a small icon like
>>>>> in GitHub or Twitter.
>>>>> @ Harshan When users using

Re: [Dev] Displaying the username & email of users in EMM console

[Kamidu Punchihewa]

Hi Jerad,

What you are saying is True .But i feel like we need to indicate these
specially when come to scenarios where the username also an email or looks
like an image.
In my previous experience i had experience with the server where it gives
the user name as *@*.In cases like that user might feel
like there are two emails.Since EMM is an end user application we need to
make it less complicated as possible.
This is just an opinion we can get all the ideas and come with the nice
final design.Finally we need what makes EMM better right.

Cheers

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Thu, Nov 5, 2015 at 11:18 AM, Jerad Rutnam <je...@wso2.com> wrote:

> Hi Kamidu,
>
> It's a good idea. But I feels it will looks bit clutter since we have the
> action icons. And even for an icon it will take some space. WDYT?
>
> Cheers!
> Jerad
>
> On Thu, Nov 5, 2015 at 10:09 AM, Harshan Liyanage <hars...@wso2.com>
> wrote:
>
>> Hi,
>>
>> Prabath also had a similar idea. That's also a good suggestion. So lets
>> get the feedback from UX team.
>>
>> Thanks,
>>
>> Harshan Liyanage
>> Software Engineer
>> Mobile: *+94724423048*
>> Email: hars...@wso2.com
>> Blog : http://harshanliyanage.blogspot.com/
>> *WSO2, Inc. :** wso2.com <http://wso2.com/>*
>> lean.enterprise.middleware.
>>
>> On Thu, Nov 5, 2015 at 10:06 AM, Kamidu Punchihewa <sachi...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> +1 for both ideas.
>>> What if we replace the lable user name and email to a small icon like in
>>> GitHub or Twitter.
>>> @ Harshan When users using separate user store with predefined  users
>>> the user name can be the email it self EMM had these kind of requirements
>>> In that kind a scenarios sharon's suggestion is really valuable.
>>>
>>> Cheers
>>>
>>> Kamidu Sachith Punchihewa
>>> *Software Engineer*
>>> WSO2, Inc.
>>> lean . enterprise . middleware
>>> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>>>
>>>
>>> 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, retransmit, 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.
>>>
>>> On Thu, Nov 5, 2015 at 9:27 AM, Harshan Liyanage <hars...@wso2.com>
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> Thanks for your valuable ideas. Yeah, we need to show the label for
>>>> other properties, but since we are not showing them in the grid-view we can
>>>> omit the labels from grid-view.  So +1 for both ideas.
>>>>
>>>> Regards,
>>>>
>>>> Harshan Liyanage
>>>> Software Engineer
>>>> Mobile: *+94724423048*
>>>> Email: hars...@wso2.com
>>>> Blog : http://harshanliyanage.blogspot.com/
>>>> *WSO2, Inc. :** wso2.com <http://wso2.com/>*
>>>> lean.enterprise.middleware.
>>>>
>>>> On Thu, Nov 5, 2015 at 8:59 AM, Sharon David <shar...@wso2.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> +1 to Jerad's suggestion.
>>>>> Small concern, if the mail is not mentioned its better to keep it
>>>>> blank without mentioning "unspecified" .
>>>>>
>>>>> On Thu, Nov 5, 2015 at 8:52 AM, Jerad 

Re: [Dev] Displaying the username & email of users in EMM console

[Kamidu Punchihewa]

Hi,

+1 for both ideas.
What if we replace the lable user name and email to a small icon like in
GitHub or Twitter.
@ Harshan When users using separate user store with predefined  users the
user name can be the email it self EMM had these kind of requirements In
that kind a scenarios sharon's suggestion is really valuable.

Cheers

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


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,
retransmit, 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.

On Thu, Nov 5, 2015 at 9:27 AM, Harshan Liyanage  wrote:

> Hi all,
>
> Thanks for your valuable ideas. Yeah, we need to show the label for other
> properties, but since we are not showing them in the grid-view we can omit
> the labels from grid-view.  So +1 for both ideas.
>
> Regards,
>
> Harshan Liyanage
> Software Engineer
> Mobile: *+94724423048*
> Email: hars...@wso2.com
> Blog : http://harshanliyanage.blogspot.com/
> *WSO2, Inc. :** wso2.com *
> lean.enterprise.middleware.
>
> On Thu, Nov 5, 2015 at 8:59 AM, Sharon David  wrote:
>
>> Hi,
>>
>> +1 to Jerad's suggestion.
>> Small concern, if the mail is not mentioned its better to keep it blank
>> without mentioning "unspecified" .
>>
>> On Thu, Nov 5, 2015 at 8:52 AM, Jerad Rutnam  wrote:
>>
>>> Hi Harshan,
>>>
>>> Grid view here is an optional. So what I suggest is to enforce list view
>>> on load. And yes it's not necessary here to show the label "Username,
>>> Email", but for other values like "Role, Type" etc ... we have to show the
>>> label.
>>>
>>> So +1 for removing the labels for those 2 values in grid view.
>>>
>>> Cheers!
>>> Jerad
>>>
>>> On Thu, Nov 5, 2015 at 3:59 AM, Udara Rathnayake 
>>> wrote:
>>>
 For ES we have done a similar UI fix to display name of the
 asset/publisher, when there is a lengthy name.
 Not sure it's going to suit here but you can have a look.

 On Wed, Nov 4, 2015 at 9:58 AM, Harshan Liyanage 
 wrote:

> Hi,
>
> We need to show the username & email of users in EMM console. But the
> existing UI theme can not be used to show lengthy user names [1]. My
> suggestion is to only show the username & email without their text-labels
> (Username & Email).
>
> WDYT?
>
> [1]. https://wso2.org/jira/browse/EMM-926
>
> Thanks,
>
> Harshan Liyanage
> Software Engineer
> Mobile: *+94724423048*
> Email: hars...@wso2.com
> Blog : http://harshanliyanage.blogspot.com/
> *WSO2, Inc. :** wso2.com *
> lean.enterprise.middleware.
>
> ___
> 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


>>>
>>>
>>> --
>>> *Jerad Rutnam*
>>> *Software Engineer*
>>>
>>> WSO2 Inc.
>>> lean | enterprise | middleware
>>> M : +94 77 959 1609 | E : je...@wso2.com | W : www.wso2.com
>>>
>>
>>
>>
>> --
>> Sharon David
>> Software Engineer - UI/UX  |   WSO2 Inc
>>
>> +94 777 668 411  |  shar...@wso2.com  |   http://wso2.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