Re: [Architecture] [Dev] [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
 Architecture@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


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

Re: [Architecture] [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
> d...@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.
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [IoT][Android] Making Android passcode policy to be consistent with iOS

[Kamidu Punchihewa]

Hi Inosh at el,

+1 for the idea so the users have the same experience when using/enforcing
policies to there managed mobile devices. Can't we follow the same approach
in windows as well, so we can expose the same experience all whole EMM use
case? WDYT?

Thanks and Best Regards,

On Wed, Jan 31, 2018 at 12:20 PM, Inosh Perera  wrote:

> Hi Charitha,
>
> +1, By doing so we can have same experience for pass code policy. Anyway
> with current design, we have clear separation with Android and iOS
> policies. So still we might have to keep those two policy wizards.
> Since policies are platform specific, even if the passcode policy's
> behaviour is similar, we will not be changing the UI.
>
> Regards,
> Inosh
>
> On Wed, Jan 31, 2018 at 12:14 PM, Inosh Perera  wrote:
>
>> Hi Rasika,
>>
>> Please find the possible combinations and the minimum password needed
>> bellow,
>> isSimple isAlphanumeric isComplex Minimum sufficient password
>> y n n 1234
>> y y n 1234a
>> y y y 1234a#
>> n y y 1234a#
>> n n y 1234#
>> y n y 1234#
>> n y n 1234#h
>> n n n 1234#
>> Regards,
>> Inosh
>>
>>
>> On Wed, Jan 31, 2018 at 11:51 AM, Charitha Goonetilleke <
>> charit...@wso2.com> wrote:
>>
>>> Hi Inosh,
>>>
>>> On Tue, Jan 30, 2018 at 3:33 PM, Inosh Perera  wrote:
>>>
 Hi all,

 Currently the passcode policy of IoT server for Android and iOS
 platforms seems to have followed 2 different approaches and this
 inconsistency can lead to confusion for an EMM administrator.

 *Following are the inconsistencies,*
 In iOS protocol, allow simple passcode means that the user is free to
 enter just a pin or any passcode. However with Android currently, it must
 be a alphanumeric value only.
 Also in iOS disallow simple is equivalent to having at least one
 complex characters regardless of the alphanumeric check. When alphanumeric
 is not required and complex characters are set to 1, the user should be
 able to add a password like "1234$" as the passcode and currently Android
 policy does not support this behaviour and it ask for a minimum one
 alphabetic character regardless of the state of alphanumeric checkbox.
 Therefore to get rid of these inconsistencies, I suggest we should make the
 Android passcode policy work similar to iOS.

 *Solution*
 Therefore, as per iOS protocol, following would be the standard of the
 passcode policy,
 allowSimple - If a simple passcode containing just numbers or just
 letters or combination is allowed. Setting this to "no" mean, a complex
 passcode is required and of minimum of 1 complex character together with
 numbers or alphabets characters.
 minComplexChars - A complex character is a character other than an
 alphanumeric value. Setting min complex chars restriction will not mean
 that an alphabetic character is required.
 requireAlphanumeric - Whether alphabetic characters are required or is
 it enough to have numbers only.

>>>
>>> +1, By doing so we can have same experience for pass code policy. Anyway
>>> with current design, we have clear separation with Android and iOS
>>> policies. So still we might have to keep those two policy wizards.
>>>
>>>

 Regards,
 Inosh

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


>>> Thanks & regards,
>>> /charithag
>>>
>>> --
>>> *Charitha Goonetilleke*
>>> Senior Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 77 751 3669 <%2B94777513669>
>>> Twitter:@CharithaWs , fb: charithag
>>> , linkedin: charithag
>>> 
>>>
>>> 
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Inosh Perera
>> Senior Software Engineer, WSO2 Inc.
>> Tel: 077813 7285, 0785293686
>>
>
>
>
> --
> Inosh Perera
> Senior Software Engineer, WSO2 Inc.
> Tel: 077813 7285, 0785293686
>
> ___
> Architecture mailing list
> Architecture@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>

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, 

Re: [Architecture] [Feature] Storing the application certificate in the database.

[Kamidu Punchihewa]

Hi Rushmin/ Shazni,

+1 for storing the certificates in the database.
Regarding the User Experience aspected discussed above, IMHO I think its
better to provide both the option where a user can select the file as in
uploading a file and same as allowing user to input the certificate content
into an editor. A user will have two options so they can use most familiar
and convenient method to them.

Uploading a file needs a file name and the filename is an unwated data in
> our case


Since uploading file will have unwanted data to be saved, we can read the
file using front-end scripting and view the certificate contains in the
text editor which users can type or past the certificate data. Then we just
have to send the certificate data to the backend and handle only the needed
information. WDYT?


Thanks and Best Regards,

On Sun, Jan 14, 2018 at 10:31 AM, Inosh Perera  wrote:

> Hi Rushmin,
>
> The certificate should be stored in the database so that it is shared and
> a restart is not needed.
> +1 for the approach. There is a similar implementation[1] in the IoT
> server to maintain device identity certificates of the devices for auto
> enrollment flows. However, since the client we are using(device agents) are
> provided by the IoT server, the in-build CA of the IoT server creates per
> device certificates for each device, therefore, we are doing mutual TLS.
> However, you may still be able to use some of the logic.
>
> [1]. https://github.com/wso2/carbon-device-mgt/tree/master/c
> omponents/certificate-mgt
>
> Regards,
> Inosh
>
> On Mon, Jan 8, 2018 at 9:39 PM, Shazni Nazeer  wrote:
>
>> Yes. Seems both options are viable and has it own pros and cons. I'm +1
>> for either option. Just that uploading is little more convenient at the
>> time of adding it. But having text have its own reason to consider it.
>>
>> On Sun, Jan 7, 2018 at 11:22 PM, Rushmin Fernando 
>> wrote:
>>
>>>
>>>
>>> On Mon, Jan 8, 2018 at 3:19 AM, Shazni Nazeer  wrote:
>>>
 1) The SP UI will have a new text area to enter the certificate in PEM
 format.
 Is there any specific reason to use text area here? In IDP UI, we
 have an option to upload the idp cert. IMO it is better to have that 
 option
 in SP UI as well for the UI consistance. '

>>>

> It is bit easier for users to paste the content staight away rather
 than uploading files.
 +1 for making both UIs consistent.
>>>
>>>
 +! for certificate upload mechanism for consistency. I think uploading
 will be much easier than pasting the text.

>>>
>>>
>>>
>>> Thank you for the feedback Shazni. I agree that uploading might be
>>> eaiser when you have the file in hand. But we have following cons as well
>>> given that a PEM encoded ceritificate is a text content which is about 10
>>> lines.
>>>
>>>
>>> 1) Uploading a file needs a file name and the filename is an unwated
>>> data in our case.
>>>
>>> 2) If you want to view the uploaded PEM file later, you have to download
>>> it. (It is cleaner when you see the content in the UI)
>>>
>>>
>>>
>>>


 Also if the user can still add the certificate of the SP to the
 keystore and also from the UI, what would be the behavior when one of the
 certificate is invalid or expired and the other one is correct? Will there
 be any precedence, such as if it's in DB it will only check in DB or
 whether it checks in both DB and keystore?

 On Sat, Jan 6, 2018 at 6:37 AM, Godwin Shrimal  wrote:

> Thanks for the explanation Rushmin. Yeah, it makes sense. +1
>
>
> Thanks
> Godwin
>
> On Fri, Jan 5, 2018 at 3:30 PM, Rushmin Fernando 
> wrote:
>
>> Hi Godwin,
>>
>> IMO certificate is a first class member of a service provider. So
>> storing it as a field in SP_APP is cleaner.
>>
>> On the other hand, the datatype of a certificate doesn't really go
>> with other metadata.
>>
>> In the best case, we have to alter the metadata table to hold a
>> VARCHAR of like 1000 characters.
>>
>> Considering all of these facts, I thought of using the SP_APP table
>> instead of SP_METADATA.
>>
>> What do you think?
>>
>> On Fri, Jan 5, 2018 at 12:56 PM, Godwin Shrimal 
>> wrote:
>>
>>> Hi Rushmin,
>>>
>>> Any reason to use SP_APP table to persist the certificate? We have a
>>> table called SP_METADATA to SP related metadata. I think we can use that
>>> table without changing any DB Schema. WDYT?
>>>
>>>
>>> Thanks
>>> Godwin
>>>
>>> On Fri, Jan 5, 2018 at 1:33 PM, Rushmin Fernando 
>>> wrote:
>>>


 On Fri, Jan 5, 2018 at 11:55 AM, Isura Karunaratne 
 wrote:

> Hi Rushmin,

Re: [Architecture] [Dev] [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
> Architecture@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.
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [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
>>> d...@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
>> d...@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
> d...@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: [Architecture] WSO2 IoT server supporting OMA Lightweight M2M protocol (OMA LWM2M)

[Kamidu Punchihewa]

Hi Inosh,

LWM2M Leshan server provides a restful interface where all the
characteristics/properties are represent by an integer. You can find a more
details including the features and the usability of Leshan server in there
home page's getting started section[1] .

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 Tue, Mar 7, 2017 at 3:38 PM, Sumedha Rubasinghe  wrote:

> Hi Ching,
> Could you list out the exact set of steps needed to get this to working
> please?
>
>
> On Tue, Mar 7, 2017 at 9:53 AM, Ching Shi  wrote:
>
>> Hi all,
>>
>> OMA Lightweight M2M protocol is from the Open Mobile Alliance for IoT
>> device management. This protocol provides,
>>
>>1. Device management functionalities over sensor or cellular networks
>>2. Transfer service data from the network to devices
>>
>> Lightweight M2M enabler defines the application layer communication
>> protocol between a LWM2M server and a LWM2M client. The target LWM2M
>> devices for this enabler are mainly resource constrained devices. Therefore
>> this enabler makes use of a light and compact protocol as well as an
>> efficient resource data model.
>>
>> Eclipse Leshan is an open source project which consists of a Lightweight
>> M2M server. Leshan also consists of a LWM2M client which could run on any
>> Linux Distribution. For example if the LWM2M client is running in a
>> Raspberry Pi it could communicate with the LWM2M Server.
>>
>> The Eclipse Leshan Server is now integrated with the WSO2 IoT Server
>> providing OMA Lightweight M2M. Initially the Eclipse Leshan Server wasn't
>> handling any security. Authentication and authorisation is now handled in
>> the Eclipse Leshan Server and Single Sign On (SSO) is configured with the
>> WSO2 IoT Server.
>>
>>
>> --
>> Ching Tien Shi
>> Intern - Engineering
>> Mobile : +94770186272 <077%20018%206272>
>>
>>
>>
>> --
>> Ching Tien Shi
>> Intern - Engineering
>> Mobile : +94770186272 <077%20018%206272>
>>
>>
>
>
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [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
>> d...@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks & Regards,
> Dulanja Liyanage
> Lead, Platform Security Team
> WSO2 Inc.
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] [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.
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] 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
>