[Dev] Username Recovery Feature in IS 6.0.0

[Dinali Dabarera]

Hi all,

We are working on implementing username recovery feature for IS 6.0.0

*The admin has to enable the Username Recovery*


*When Username Recovery enabled:*

   - User portal user can click on the forget username option.
   - The User can enter his details of the default profile.
   - The System will match the entered details with the claims available
   and if they matched, the relevant username will email to his email address
   and prompt a notification saying that an email is sent to his mail.
   - If it doesn't match, the user will notify telling that relevant user
   is not registered in the system.

*When Username Recovery is disabled:*

   - User portal user may not be able to recover his username.
   - The User needs to contact the admin of the system to recover his
   username.

The admin enables the username recovery in the identity.yaml file for the
users in the domain.  Since we have different user stores available in IS
6.0.0,
  *Does the admin need to enable username recovery in user store wise
or Does he need to configure it for the whole domain at once?*


Please provide us your comments on this point.

Thanks,

Dina.
-- 
*Dinali Rosemin Dabarera*
Software Engineer
WSO2 Lanka (pvt) Ltd.
Web: http://wso2.com/
Email : gdrdabar...@gmail.com
LinkedIn 
Mobile: +94770198933 <+94%2077%20019%208933>





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

Re: [Dev] [UUF] Define page layout for default error pages

[Danushka Fernando]

Not sure which components its coming from. For example 404 error page is a
default error page coming from UUF.

Thanks & Regards
Danushka Fernando
Senior Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729

On Sat, Jan 21, 2017 at 10:18 AM, SajithAR Ariyarathna 
wrote:

> On Sat, Jan 21, 2017 at 6:20 AM, Danushka Fernando 
>> wrote:
>>
>>> Hi All
>>> I found that default error pages like 404 error page which comes from
>>> UUF doesn't use app's basic layout. And I couldn't find a way to override
>>> it. Is there a way of achieving this.
>>>
>> Are you referring to the error pages comes from
> "org.wso2.carbon.uuf.common.foundation.ui" component?
>
> On Sat, Jan 21, 2017 at 8:49 AM, Danushka Fernando 
> wrote:
>
>> Nisala
>> This means we have to write whole error page right? But what if we need
>> just layout to be changed. Isn't there an option other than duplicating?
>> Because we will change basically the header and footer only.
>>
>> Thanks & Regards
>> Danushka Fernando
>> Senior Software Engineer
>> WSO2 inc. http://wso2.com/
>> Mobile : +94716332729 <+94%2071%20633%202729>
>>
>> On Sat, Jan 21, 2017 at 8:12 AM, Nisala Nanayakkara 
>> wrote:
>>
>>> Hi Danushka,
>>>
>>> You can define your own error pages and its' layout as follows. As an
>>> example you need to add below configuration to app.yaml.
>>>
>>> *errorPages: *
>>> *404: "/foundation/error/404"*
>>> * default: **"/foundation/error/default**"*
>>>
>>> Please find related app.yaml[1] and the error pages here[2].
>>>
>>> [1] - https://github.com/wso2/carbon-uuf/blob/master/samples/apps/
>>> org.wso2.carbon.uuf.sample.pets-store.app/src/main/app.yaml
>>> [2] - https://github.com/wso2/carbon-uuf/tree/master/samples/compo
>>> nents/org.wso2.carbon.uuf.sample.foundation.ui/src/main/pages/error
>>>
>>> Thanks,
>>> Nisala
>>>
>>>
>>>
>>> On Sat, Jan 21, 2017 at 6:20 AM, Danushka Fernando 
>>> wrote:
>>>
 Hi All
 I found that default error pages like 404 error page which comes from
 UUF doesn't use app's basic layout. And I couldn't find a way to override
 it. Is there a way of achieving this.

 Thanks & Regards
 Danushka Fernando
 Senior Software Engineer
 WSO2 inc. http://wso2.com/
 Mobile : +94716332729 <+94%2071%20633%202729>

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


>>>
>>>
>>> --
>>> *Nisala Niroshana Nanayakkara,*
>>> Software Engineer
>>> Mobile:(+94)717600022
>>> WSO2 Inc., http://wso2.com/
>>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sajith Janaprasad Ariyarathna
> Software Engineer; WSO2, Inc.;  http://wso2.com/
> 
>
___
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

[Menaka Jayawardena]

Hi I have tested the following,

1. Enrolling android sense.
2. Publishing data
3. View them in the portal dashboard graphs.
  - Sensor data
  - Realtime data
  - Location
  - Battery history
  - Communication

[+] Stable - go ahead and release.

Thanks,
Menaka


On Jan 21, 2017 10:33 AM, "Lakshani Gamage"  wrote:

Hi,

I have tested below.

   - App Management integration.
   - Add/Edit users and Roles.
   - Enroll Android devices

[+]Stable - go ahead and release
Thanks,

On Sat, Jan 21, 2017 at 10:09 AM, Kamidu Punchihewa 
wrote:

> 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 <
> jasin...@wso2.com> 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 

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

[Madhawa Perera]

Hi All,

I have tested following scenarios,

   - Tested Android, iOS and Windows device enrollment with admin user and
   another user created with necessary permissions and tested device lock
   operation in iOS, and device ring operation in Android and Windows
   - Tested following scenarios with Device Grouping with enrolled iOS and
   Android devices together and Windows and Android devices together
   - Creating new groups and updating them
  - Adding devices to groups via groups
  - Adding devices to groups via devices
  - Sharing groups with user roles and updating shared details
  - Adding operations to grouped devices from shared users

[+] Stable - go ahead and release

Thank you
Best Regards,
Madhawa




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
 architect...@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>>
>>> --
>>>
>>> *Jasintha Dasanayake**Associate Technical Lead*
>>>
>>> *WSO2 Inc. | http://wso2.com lean . enterprise .
>>> middleware*
>>>
>>>
>>> *mobile :- 0711-368-118*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Regards,
>>
>> Chatura Dilan Perera
>> *Associate Tech Lead** - WSO2 Inc.*
>> www.dilan.me
>>
>> ___
>> 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:+94713350904 <+94%2071%20335%200904>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Madhawa Perera
*Software Engineer*
Mobile : +94 (0) 773655496
<%2B94%20%280%29%20773%20451194>
madha...@wso2.com
___
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

[Lakshani Gamage]

Hi,

I have tested below.

   - App Management integration.
   - Add/Edit users and Roles.
   - Enroll Android devices

[+]Stable - go ahead and release
Thanks,

On Sat, Jan 21, 2017 at 10:09 AM, Kamidu Punchihewa 
wrote:

> 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 <
> jasin...@wso2.com> 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 

Re: [Dev] [UUF] Define page layout for default error pages

[SajithAR Ariyarathna]

>
> On Sat, Jan 21, 2017 at 6:20 AM, Danushka Fernando 
>  wrote:
>
>> Hi All
>> I found that default error pages like 404 error page which comes from UUF
>> doesn't use app's basic layout. And I couldn't find a way to override it.
>> Is there a way of achieving this.
>>
> Are you referring to the error pages comes from
"org.wso2.carbon.uuf.common.foundation.ui" component?

On Sat, Jan 21, 2017 at 8:49 AM, Danushka Fernando 
wrote:

> Nisala
> This means we have to write whole error page right? But what if we need
> just layout to be changed. Isn't there an option other than duplicating?
> Because we will change basically the header and footer only.
>
> Thanks & Regards
> Danushka Fernando
> Senior Software Engineer
> WSO2 inc. http://wso2.com/
> Mobile : +94716332729 <+94%2071%20633%202729>
>
> On Sat, Jan 21, 2017 at 8:12 AM, Nisala Nanayakkara 
> wrote:
>
>> Hi Danushka,
>>
>> You can define your own error pages and its' layout as follows. As an
>> example you need to add below configuration to app.yaml.
>>
>> *errorPages: *
>> *404: "/foundation/error/404"*
>> * default: **"/foundation/error/default**"*
>>
>> Please find related app.yaml[1] and the error pages here[2].
>>
>> [1] - https://github.com/wso2/carbon-uuf/blob/master/samples/apps/
>> org.wso2.carbon.uuf.sample.pets-store.app/src/main/app.yaml
>> [2] - https://github.com/wso2/carbon-uuf/tree/master/samples/
>> components/org.wso2.carbon.uuf.sample.foundation.ui/src/main/pages/error
>>
>> Thanks,
>> Nisala
>>
>>
>>
>> On Sat, Jan 21, 2017 at 6:20 AM, Danushka Fernando 
>> wrote:
>>
>>> Hi All
>>> I found that default error pages like 404 error page which comes from
>>> UUF doesn't use app's basic layout. And I couldn't find a way to override
>>> it. Is there a way of achieving this.
>>>
>>> Thanks & Regards
>>> Danushka Fernando
>>> Senior Software Engineer
>>> WSO2 inc. http://wso2.com/
>>> Mobile : +94716332729 <+94%2071%20633%202729>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Nisala Niroshana Nanayakkara,*
>> Software Engineer
>> Mobile:(+94)717600022
>> WSO2 Inc., http://wso2.com/
>>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sajith Janaprasad Ariyarathna
Software Engineer; WSO2, Inc.;  http://wso2.com/

___
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
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> -

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

[Sameera Gunarathne]

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
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


 --

 *Jasintha Dasanayake**Associate Technical Lead*

 *WSO2 Inc. | http://wso2.com lean . enterprise .
 middleware*


 *mobile :- 0711-368-118*

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


>>>
>>>
>>> --
>>> Regards,
>>>
>>> Chatura Dilan Perera
>>> *Associate Tech Lead** - WSO2 Inc.*
>>> www.dilan.me
>>>
>>> ___
>>> 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:+94713350904 <+94%2071%20335%200904>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *G. K. S. Munasinghe*
> *Senior Software Engineer,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: ge...@wso2.com
> phone:(+94) 777911226 <+94%2077%20791%201226>
>
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sameera Gunarathne
Software Engineer, WSO2 Inc. http://wso2.com

Email: samee...@wso2.com
Mobile: +94714155561

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

[Geeth Munasinghe]

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
 architect...@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>>
>>> --
>>>
>>> *Jasintha Dasanayake**Associate Technical Lead*
>>>
>>> *WSO2 Inc. | http://wso2.com lean . enterprise .
>>> middleware*
>>>
>>>
>>> *mobile :- 0711-368-118*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Regards,
>>
>> Chatura Dilan Perera
>> *Associate Tech Lead** - WSO2 Inc.*
>> www.dilan.me
>>
>> ___
>> 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:+94713350904 <+94%2071%20335%200904>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*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] [Architecture] [VOTE] Release WSO2 IoT Server 3.0.0 RC2

[Inosh Perera]

Hi,

I have tested following scenarios,

   - Enrolled iOS mobile device (8.4) on IoT server
   - Tested device lock operation
   - Tested all the available policies.
   - Installed public web applications via app store and tested enterprise
   install and uninstall.

[+] Stable - go ahead and release.

Regards,
Inosh

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
 architect...@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>>
>>> --
>>>
>>> *Jasintha Dasanayake**Associate Technical Lead*
>>>
>>> *WSO2 Inc. | http://wso2.com lean . enterprise .
>>> middleware*
>>>
>>>
>>> *mobile :- 0711-368-118*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Regards,
>>
>> Chatura Dilan Perera
>> *Associate Tech Lead** - WSO2 Inc.*
>> www.dilan.me
>>
>> ___
>> 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:+94713350904 <+94%2071%20335%200904>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

Re: [Dev] [UUF] Define page layout for default error pages

[Danushka Fernando]

Nisala
This means we have to write whole error page right? But what if we need
just layout to be changed. Isn't there an option other than duplicating?
Because we will change basically the header and footer only.

Thanks & Regards
Danushka Fernando
Senior Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729

On Sat, Jan 21, 2017 at 8:12 AM, Nisala Nanayakkara  wrote:

> Hi Danushka,
>
> You can define your own error pages and its' layout as follows. As an
> example you need to add below configuration to app.yaml.
>
> *errorPages: *
> *404: "/foundation/error/404"*
> * default: **"/foundation/error/default**"*
>
> Please find related app.yaml[1] and the error pages here[2].
>
> [1] - https://github.com/wso2/carbon-uuf/blob/master/
> samples/apps/org.wso2.carbon.uuf.sample.pets-store.app/src/main/app.yaml
> [2] - https://github.com/wso2/carbon-uuf/tree/master/
> samples/components/org.wso2.carbon.uuf.sample.foundation.
> ui/src/main/pages/error
>
> Thanks,
> Nisala
>
>
>
> On Sat, Jan 21, 2017 at 6:20 AM, Danushka Fernando 
> wrote:
>
>> Hi All
>> I found that default error pages like 404 error page which comes from UUF
>> doesn't use app's basic layout. And I couldn't find a way to override it.
>> Is there a way of achieving this.
>>
>> Thanks & Regards
>> Danushka Fernando
>> Senior Software Engineer
>> WSO2 inc. http://wso2.com/
>> Mobile : +94716332729 <+94%2071%20633%202729>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Nisala Niroshana Nanayakkara,*
> Software Engineer
> Mobile:(+94)717600022
> WSO2 Inc., http://wso2.com/
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [UUF] Define page layout for default error pages

[Nisala Nanayakkara]

Hi Danushka,

You can define your own error pages and its' layout as follows. As an
example you need to add below configuration to app.yaml.

*errorPages: *
*404: "/foundation/error/404"*
* default: **"/foundation/error/default**"*

Please find related app.yaml[1] and the error pages here[2].

[1] -
https://github.com/wso2/carbon-uuf/blob/master/samples/apps/org.wso2.carbon.uuf.sample.pets-store.app/src/main/app.yaml
[2] -
https://github.com/wso2/carbon-uuf/tree/master/samples/components/org.wso2.carbon.uuf.sample.foundation.ui/src/main/pages/error

Thanks,
Nisala



On Sat, Jan 21, 2017 at 6:20 AM, Danushka Fernando 
wrote:

> Hi All
> I found that default error pages like 404 error page which comes from UUF
> doesn't use app's basic layout. And I couldn't find a way to override it.
> Is there a way of achieving this.
>
> Thanks & Regards
> Danushka Fernando
> Senior Software Engineer
> WSO2 inc. http://wso2.com/
> Mobile : +94716332729 <+94%2071%20633%202729>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

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

[Hasunie Adikari]

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
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>>
>> *Jasintha Dasanayake**Associate Technical Lead*
>>
>> *WSO2 Inc. | http://wso2.com lean . enterprise .
>> middleware*
>>
>>
>> *mobile :- 0711-368-118*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Regards,
>
> Chatura Dilan Perera
> *Associate Tech Lead** - WSO2 Inc.*
> www.dilan.me
>
> ___
> 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:+94713350904
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [UUF] Define page layout for default error pages

[Danushka Fernando]

Hi All
I found that default error pages like 404 error page which comes from UUF
doesn't use app's basic layout. And I couldn't find a way to override it.
Is there a way of achieving this.

Thanks & Regards
Danushka Fernando
Senior Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729
___
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

[Chathura Dilan]

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
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
>
> *Jasintha Dasanayake**Associate Technical Lead*
>
> *WSO2 Inc. | http://wso2.com lean . enterprise .
> middleware*
>
>
> *mobile :- 0711-368-118*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Regards,

Chatura Dilan Perera
*Associate Tech Lead** - WSO2 Inc.*
www.dilan.me
___
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

[Jasintha Dasanayake]

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
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*Jasintha Dasanayake**Associate Technical Lead*

*WSO2 Inc. | http://wso2.com lean . enterprise .
middleware*


*mobile :- 0711-368-118*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Ayyoob Hamza]

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
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Milan Perera]

Hi,

I have tested following scenarios.

   - Installed iOS mobile plugin and configured the IoTS.
   - Enrolled iOS mobile device (v 10.1) as admin.
   - Executed device lock, ring, location, notification operations.
   - Added a restriction via a policy.
   - Installed public, enterprise and web applications via app store.
   - Un-enrolled the device.
   - Created a new user with a necessary permissions.
   - Enrolled the device using newly created user.
   - Tested the same operations as above.


[+] Stable - go ahead and release.

Regards,


On Fri, Jan 20, 2017 at 10:33 PM, Rasika Perera  wrote:

> [-architecture, -dev]
>
> Guys,
>
> Please vote on your tested areas.
>
> Thanks,
> Rasika
>
> On Fri, Jan 20, 2017 at 10:29 PM, Rasika Perera  wrote:
>
>> Hi Devs,
>>
>> *WSO2 ​IoT ​Server ​3.0.0-RC2 Released*
>>
>> This is the 2nd Release Candidate of the WSO2
>> ​IoT Server​
>>
>> ​3​
>> .0.0
>>
>> Please download, test the product and vote.
>>
>> *​*Known issues  :
>>  https://wso2.org/jira/issues/?filter=13634
>> Fixes provided :​
>> https://wso2.org/jira/issues/?filter=13635
>>
>> *Source and binary distribution files:*
>> https://github.com/wso2/product-iots/releases/tag/v3.0.0-RC2
>>
>> *The tag to be voted upon:*
>> https://github.com/wso2/product-iots/tree/v3.0.0-RC2
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thanks,
>> ~WSO2 IoT Team~
>>
>> --
>> With Regards,
>>
>> *Rasika Perera*
>> Software Engineer
>> LinkedIn: http://lk.linkedin.com/in/rasika90
>>
>> 
>>
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>>
>
>
>
> --
> With Regards,
>
> *Rasika Perera*
> Software Engineer
> LinkedIn: http://lk.linkedin.com/in/rasika90
>
> 
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>



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


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

[Dev] [VOTE] Release WSO2 IoT Server 3.0.0 RC2

[Rasika Perera]

Hi Devs,

*WSO2 ​IoT ​Server ​3.0.0-RC2 Released*

This is the 2nd Release Candidate of the WSO2
​IoT Server​

​3​
.0.0

Please download, test the product and vote.

*​*Known issues  :
 https://wso2.org/jira/issues/?filter=13634
Fixes provided :​
https://wso2.org/jira/issues/?filter=13635

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

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

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

Thanks,
~WSO2 IoT Team~

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

Re: [Dev] [Architecture] Account Lock/Disable Feature in IS 6.0.0

[Ishara Karunarathna]

Hi

On Fri, Jan 20, 2017 at 4:28 PM, Rushmin Fernando  wrote:

> Isura, as per my understanding, in most of the cases 'inactive' user are
> treated as non-existing users.
>
> So from the domain model side we should have a method to .
>
>  get the active users (since this the default case, we can even name
> the method as getUsers() )
>
> and another method to 
>
>  get the user including inactive users
>
+1 for this. Ideally in all user operation we can filter out the inactive
users.
Ex in JDBC user stores we may accound_inactive claim in LDAP we can filter
out with UserAccountControl attribute.

>
> When it comes to operations, we anyway have to have an interceptor in the
> authentication flow to refuse locked users (inative users will no even be
> considered)
>
> One down side is performance. If we check this before in authentication it
will reduce the performance.
so if the user store (Identity store ) support for account locking better
to use that implementation. if not we have to explicitly check the
account lock property.

-Ishara


>
>
> On Fri, Jan 20, 2017 at 3:32 PM, Isura Karunaratne  wrote:
>
>> Hi all,
>>
>>
>> We are working on implementing account lock/disable features for IS
>> 6.0.0.
>>
>> *Account Lock: *
>>
>>- User *must not *be able to login to the system.
>>- Admin user *can* update the user attributes and assign roles
>>(account is active)
>>- User cannot start a  password recovery flow.
>>
>> *Account Disable: *
>>
>>- User *must not* be able to login to the system.
>>- Admin user *can not* update the user attributes and cannot assign
>>roles until enabling the account. (inactive state)
>>- User cannot start a  password recovery flow.
>>
>>
>>
>> *When will the account be locked?*
>>
>>
>>
>>- Self Signup users until account confirmation
>>- Try to login with invalid credentials more than configured number
>>of attempts. Then the account will be locked configured amount of time.
>>(Like 5 minutes). This lock time will be increased if the user locked 
>> again
>>based on a configuration.
>>- Provide invalid answers more than configured number of attempts,
>>when password recovery
>>- User onboarding with Email/SMS verification flow.
>>- When admin needs to block the user to login to the system
>>- When admin initiated password reset flow starts.
>>
>>
>>
>> *When will the account be disabled?*
>>
>>
>>
>>
>>
>>- When admin needs to inactivate user.
>>
>>
>>
>> What is the best way handle account disable check? We can do this from a
>> inceptor level, then we need to check account disable in each operation.
>>
>> Thanks
>> Isura.
>>
>>
>>
>>
>>
>> *Isura Dilhara Karunaratne*
>> Senior Software Engineer | WSO2
>> Email: is...@wso2.com
>> Mob : +94 772 254 810 <+94%2077%20225%204810>
>> Blog : http://isurad.blogspot.com/
>>
>>
>>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> *Best Regards*
>
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc.  - Lean . Enterprise . Middleware
>
> mobile : +94775615183
>
>
>


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

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

Re: [Dev] [UUF] Boolean values are not get stored properly in injected js variable from sendToClient()

[Manuranga Perera]

Yes it's find. But it creates lot of boilerplate code to get and assign
attributes one by one, and it's easy to make mistakes like above.


On Fri, Jan 20, 2017 at 2:43 PM, SajithAR Ariyarathna 
wrote:

> Hi Manu,
>
> Server-side JS is meant to be the "view controller" which creates the
> "view model" for the "view" (HBS template). So, I think its fine to process
> a data-structure (model) retrieved from back-end in order to create the
> view model.
>
> On Fri, Jan 20, 2017 at 5:19 PM, Indunil Upeksha Rathnayake <
> indu...@wso2.com> wrote:
>
>> Hi Manuranga,
>>
>> Thanks for your response.
>>
>> 1) Yeah we can do like that as well, if we only using the existing
>> attributes in the object which retrieved from the service. But here, we are
>> passing some values which are not directly exposed from the service (ex:
>> claimLabel - from the OSGI service we get the claim URI, but here we are
>> passing the URI without the claim dialect). Since UUF still not supporting
>> custom helpers, it's not possible to write a function helper and handle it
>> in hbs side right? or is there some other way to handle it?
>>
>> 2) We are getting set of claims that need to be shown in UI, by calling
>> an OSGI service(claims which relates to a specific claim profile). So that
>> those are not already defined in hbs. Every field
>> labels/validations(required fields/regex patterns/read only fields etc) in
>> the UI, will be populated from those claims. So that all the claims should
>> be sent to the front-end JS.
>>
>> Thanks and Regards
>>
>> On Fri, Jan 20, 2017 at 3:04 PM, Manuranga Perera  wrote:
>>
>>> @Indunil
>>> 1. Without the for loop can we just do sendToClient("signupClaims",
>>> claimProfile.claims); will that work?
>>> 2. Why do need to send all the claims to front-end JS anyway? aren't
>>> those already used in HBS?
>>>
>>> @Sajith
>>> 1. I keep seeing people trying to manually convert java to json. Can we
>>> give a better option? maybe have callOSGiServiceAsJson?
>>>
>>>
>>>
>>> On Fri, Jan 20, 2017 at 7:17 AM, Indunil Upeksha Rathnayake <
>>> indu...@wso2.com> wrote:
>>>
 Hi,

 Thanks all for your responses.  Yes in my case it doesn't need to
 convert boolean to string. But if needed, as sajith mentioned, seems like
 have to import that class in the script with Java.type Nashorn
 extension.

 Thanks and Regards

 On Fri, Jan 20, 2017 at 10:52 AM, SajithAR Ariyarathna <
 sajit...@wso2.com> wrote:

> Hi Indunil,
>
> Seems like the problem is in your script.
>
> Boolean.toString(claimForProfile[i].getRequired())
>
>  I believe your intention here is to call
> java.lang.Boolean#toString(boolean b) method, right? But Nashorn
> doesn't know that, because you haven't imported java.lang.Boolean class
> in your script. In order to use a Java class in your script, first you 
> have
> to import that class in your script with Java.type Nashorn extension
> [1]. (see 'call Java class' sample in the features-app sample)
> Since you haven't imported java.lang.Boolean class, Nashorn thinks
> Boolean.toString is a JS function, thus it is serialized to "function
> Boolean() { [native code] }".
>
> Anyway, You don't need to convert boolean values to strings here. So
> let's remove Boolean.toString
>
> [1] https://docs.oracle.com/javase/8/docs/technotes/guides/s
> cripting/prog_guide/javascript.html#A1147187
>
> Thanks.
>
> On Fri, Jan 20, 2017 at 10:13 AM, SajithAR Ariyarathna <
> sajit...@wso2.com> wrote:
>
>> Hi Indunil,
>>>
>>> claimProfileMap["required"] = Boolean.toString(claimForProfile[i].
>>> getRequired());
>>>
>> I don't see a particular reason to convert boolean to string. You can
>> just use the boolean value directly.
>>
>> Anyhow, we will fix this.
>> Thanks.
>>
>> On Fri, Jan 20, 2017 at 7:47 AM, Indunil Upeksha Rathnayake <
>> indu...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> The code segment I have used as follows.
>>>
>>> function getProfile() {
>>> var claimProfile;
>>> try {
>>> // Get Claim Profile
>>> claimProfile = 
>>> callOSGiService("org.wso2.is.portal.user.client.api.ProfileMgtClientService",
>>> "getProfile", ["self-signUp"]);
>>> } catch(e) {
>>> return {errorMessage: "Failed to retrieve the claim profile."};
>>> }
>>> var claimForProfile = claimProfile.claims;
>>>
>>> var claimProfileArray = [];
>>>
>>> for (var i = 0; i < claimForProfile.length; i++) {
>>> var claimProfileMap = {};
>>> claimProfileMap["displayName"] = 
>>> claimForProfile[i].getDisplayName();
>>> claimProfileMap["claimURI"] = claimForProfile[i].getClaimURI();
>>> if (claimForProfile[i].getDefaultValue()) {
>>> claimProfile

Re: [Dev] [UUF] Boolean values are not get stored properly in injected js variable from sendToClient()

[SajithAR Ariyarathna]

Hi Manu,

Server-side JS is meant to be the "view controller" which creates the "view
model" for the "view" (HBS template). So, I think its fine to process a
data-structure (model) retrieved from back-end in order to create the view
model.

On Fri, Jan 20, 2017 at 5:19 PM, Indunil Upeksha Rathnayake <
indu...@wso2.com> wrote:

> Hi Manuranga,
>
> Thanks for your response.
>
> 1) Yeah we can do like that as well, if we only using the existing
> attributes in the object which retrieved from the service. But here, we are
> passing some values which are not directly exposed from the service (ex:
> claimLabel - from the OSGI service we get the claim URI, but here we are
> passing the URI without the claim dialect). Since UUF still not supporting
> custom helpers, it's not possible to write a function helper and handle it
> in hbs side right? or is there some other way to handle it?
>
> 2) We are getting set of claims that need to be shown in UI, by calling an
> OSGI service(claims which relates to a specific claim profile). So that
> those are not already defined in hbs. Every field
> labels/validations(required fields/regex patterns/read only fields etc) in
> the UI, will be populated from those claims. So that all the claims should
> be sent to the front-end JS.
>
> Thanks and Regards
>
> On Fri, Jan 20, 2017 at 3:04 PM, Manuranga Perera  wrote:
>
>> @Indunil
>> 1. Without the for loop can we just do sendToClient("signupClaims",
>> claimProfile.claims); will that work?
>> 2. Why do need to send all the claims to front-end JS anyway? aren't
>> those already used in HBS?
>>
>> @Sajith
>> 1. I keep seeing people trying to manually convert java to json. Can we
>> give a better option? maybe have callOSGiServiceAsJson?
>>
>>
>>
>> On Fri, Jan 20, 2017 at 7:17 AM, Indunil Upeksha Rathnayake <
>> indu...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> Thanks all for your responses.  Yes in my case it doesn't need to
>>> convert boolean to string. But if needed, as sajith mentioned, seems like
>>> have to import that class in the script with Java.type Nashorn
>>> extension.
>>>
>>> Thanks and Regards
>>>
>>> On Fri, Jan 20, 2017 at 10:52 AM, SajithAR Ariyarathna <
>>> sajit...@wso2.com> wrote:
>>>
 Hi Indunil,

 Seems like the problem is in your script.

 Boolean.toString(claimForProfile[i].getRequired())

  I believe your intention here is to call
 java.lang.Boolean#toString(boolean b) method, right? But Nashorn
 doesn't know that, because you haven't imported java.lang.Boolean class
 in your script. In order to use a Java class in your script, first you have
 to import that class in your script with Java.type Nashorn extension
 [1]. (see 'call Java class' sample in the features-app sample)
 Since you haven't imported java.lang.Boolean class, Nashorn thinks
 Boolean.toString is a JS function, thus it is serialized to "function
 Boolean() { [native code] }".

 Anyway, You don't need to convert boolean values to strings here. So
 let's remove Boolean.toString

 [1] https://docs.oracle.com/javase/8/docs/technotes/guides/s
 cripting/prog_guide/javascript.html#A1147187

 Thanks.

 On Fri, Jan 20, 2017 at 10:13 AM, SajithAR Ariyarathna <
 sajit...@wso2.com> wrote:

> Hi Indunil,
>>
>> claimProfileMap["required"] = Boolean.toString(claimForProfile[i].
>> getRequired());
>>
> I don't see a particular reason to convert boolean to string. You can
> just use the boolean value directly.
>
> Anyhow, we will fix this.
> Thanks.
>
> On Fri, Jan 20, 2017 at 7:47 AM, Indunil Upeksha Rathnayake <
> indu...@wso2.com> wrote:
>
>> Hi,
>>
>> The code segment I have used as follows.
>>
>> function getProfile() {
>> var claimProfile;
>> try {
>> // Get Claim Profile
>> claimProfile = 
>> callOSGiService("org.wso2.is.portal.user.client.api.ProfileMgtClientService",
>> "getProfile", ["self-signUp"]);
>> } catch(e) {
>> return {errorMessage: "Failed to retrieve the claim profile."};
>> }
>> var claimForProfile = claimProfile.claims;
>>
>> var claimProfileArray = [];
>>
>> for (var i = 0; i < claimForProfile.length; i++) {
>> var claimProfileMap = {};
>> claimProfileMap["displayName"] = 
>> claimForProfile[i].getDisplayName();
>> claimProfileMap["claimURI"] = claimForProfile[i].getClaimURI();
>> if (claimForProfile[i].getDefaultValue()) {
>> claimProfileMap["defaultValue"] = 
>> claimForProfile[i].getDefaultValue();
>> }
>> claimProfileMap["claimLabel"] = 
>> claimForProfile[i].getClaimURI().replace("http://wso2.org/claims/";, "");
>> claimProfileMap["required"] = 
>> Boolean.toString(claimForProfile[i].getRequired());
>> claimProf

[Dev] Please review and merge

[Thanuja Jayasinghe]

Hi All,

Please review and merge [1]. This is the fix for [2].

[1] - https://github.com/wso2/carbon-kernel/pull/1277
[2] - https://github.com/wso2/carbon-kernel/issues/1276

Thanks,
Thanuja

-- 
*Thanuja Lakmal*
Senior Software Engineer
WSO2 Inc. http://wso2.com/
*lean.enterprise.middleware*
Mobile: +94715979891 +94758009992
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [UUF] Boolean values are not get stored properly in injected js variable from sendToClient()

[Indunil Upeksha Rathnayake]

Hi Manuranga,

Thanks for your response.

1) Yeah we can do like that as well, if we only using the existing
attributes in the object which retrieved from the service. But here, we are
passing some values which are not directly exposed from the service (ex:
claimLabel - from the OSGI service we get the claim URI, but here we are
passing the URI without the claim dialect). Since UUF still not supporting
custom helpers, it's not possible to write a function helper and handle it
in hbs side right? or is there some other way to handle it?

2) We are getting set of claims that need to be shown in UI, by calling an
OSGI service(claims which relates to a specific claim profile). So that
those are not already defined in hbs. Every field
labels/validations(required fields/regex patterns/read only fields etc) in
the UI, will be populated from those claims. So that all the claims should
be sent to the front-end JS.

Thanks and Regards

On Fri, Jan 20, 2017 at 3:04 PM, Manuranga Perera  wrote:

> @Indunil
> 1. Without the for loop can we just do sendToClient("signupClaims",
> claimProfile.claims); will that work?
> 2. Why do need to send all the claims to front-end JS anyway? aren't those
> already used in HBS?
>
> @Sajith
> 1. I keep seeing people trying to manually convert java to json. Can we
> give a better option? maybe have callOSGiServiceAsJson?
>
>
>
> On Fri, Jan 20, 2017 at 7:17 AM, Indunil Upeksha Rathnayake <
> indu...@wso2.com> wrote:
>
>> Hi,
>>
>> Thanks all for your responses.  Yes in my case it doesn't need to convert
>> boolean to string. But if needed, as sajith mentioned, seems like have to
>> import that class in the script with Java.type Nashorn extension.
>>
>> Thanks and Regards
>>
>> On Fri, Jan 20, 2017 at 10:52 AM, SajithAR Ariyarathna > > wrote:
>>
>>> Hi Indunil,
>>>
>>> Seems like the problem is in your script.
>>>
>>> Boolean.toString(claimForProfile[i].getRequired())
>>>
>>>  I believe your intention here is to call java.lang.Boolean#toString(boolean
>>> b) method, right? But Nashorn doesn't know that, because you haven't
>>> imported java.lang.Boolean class in your script. In order to use a Java
>>> class in your script, first you have to import that class in your script
>>> with Java.type Nashorn extension [1]. (see 'call Java class' sample in
>>> the features-app sample)
>>> Since you haven't imported java.lang.Boolean class, Nashorn thinks
>>> Boolean.toString is a JS function, thus it is serialized to "function
>>> Boolean() { [native code] }".
>>>
>>> Anyway, You don't need to convert boolean values to strings here. So
>>> let's remove Boolean.toString
>>>
>>> [1] https://docs.oracle.com/javase/8/docs/technotes/guides/s
>>> cripting/prog_guide/javascript.html#A1147187
>>>
>>> Thanks.
>>>
>>> On Fri, Jan 20, 2017 at 10:13 AM, SajithAR Ariyarathna <
>>> sajit...@wso2.com> wrote:
>>>
 Hi Indunil,
>
> claimProfileMap["required"] = Boolean.toString(claimForProfile[i].
> getRequired());
>
 I don't see a particular reason to convert boolean to string. You can
 just use the boolean value directly.

 Anyhow, we will fix this.
 Thanks.

 On Fri, Jan 20, 2017 at 7:47 AM, Indunil Upeksha Rathnayake <
 indu...@wso2.com> wrote:

> Hi,
>
> The code segment I have used as follows.
>
> function getProfile() {
> var claimProfile;
> try {
> // Get Claim Profile
> claimProfile = 
> callOSGiService("org.wso2.is.portal.user.client.api.ProfileMgtClientService",
> "getProfile", ["self-signUp"]);
> } catch(e) {
> return {errorMessage: "Failed to retrieve the claim profile."};
> }
> var claimForProfile = claimProfile.claims;
>
> var claimProfileArray = [];
>
> for (var i = 0; i < claimForProfile.length; i++) {
> var claimProfileMap = {};
> claimProfileMap["displayName"] = 
> claimForProfile[i].getDisplayName();
> claimProfileMap["claimURI"] = claimForProfile[i].getClaimURI();
> if (claimForProfile[i].getDefaultValue()) {
> claimProfileMap["defaultValue"] = 
> claimForProfile[i].getDefaultValue();
> }
> claimProfileMap["claimLabel"] = 
> claimForProfile[i].getClaimURI().replace("http://wso2.org/claims/";, "");
> claimProfileMap["required"] = 
> Boolean.toString(claimForProfile[i].getRequired());
> claimProfileMap["regex"] = claimForProfile[i].getRegex();
> claimProfileMap["readonly"] = 
> Boolean.toString(claimForProfile[i].getReadonly());
> claimProfileMap["dataType"] = claimForProfile[i].getDataType();
> claimProfileArray[i] = claimProfileMap;
> }
> sendToClient("signupClaims", claimProfileArray);
> return {
> "signupClaims": claimProfileArray
> };
> }
>
> ​
> Thanks and Regards
>

Re: [Dev] Account Lock/Disable Feature in IS 6.0.0

[Lahiru Cooray]

On Fri, Jan 20, 2017 at 4:43 PM, Prabath Siriwardena 
wrote:

> Hi Isura,
>
> Please find my comment inline...
>
> On Fri, Jan 20, 2017 at 2:02 AM, Isura Karunaratne  wrote:
>
>> Hi all,
>>
>>
>> We are working on implementing account lock/disable features for IS
>> 6.0.0.
>>
>> *Account Lock: *
>>
>>- User *must not *be able to login to the system.
>>- Admin user *can* update the user attributes and assign roles
>>(account is active)
>>- User cannot start a  password recovery flow.
>>
>>
> In summary the user cannot do any actions with the system - but the
> Administrators can.
>
 (We could have an option in user's UI to inform/contact admin once the
account is locked?)

>
>
>> *Account Disable: *
>>
>>- User *must not* be able to login to the system.
>>- Admin user *can not* update the user attributes and cannot assign
>>roles until enabling the account. (inactive state)
>>- User cannot start a  password recovery flow.
>>
>> Neither the user nor the Administrator can do any actions on this user.
> Special case, the Administrator can enable the user account.
>
>
>>
>>
>> *When will the account be locked?*
>>
>>
>>
>>- Self Signup users until account confirmation
>>
>> This is special status - and we need to identify this status different
> from the account lock. A user in this status can request to resend the
> confirmation code.
>
> Also one (an Administrator) should be able to setup a policy to wipe out
> all the unconfirmed accounts after sometime. Also there can be cases we
> still let unconfirmed users login to the system - but only a limited set of
> functionality is allowed.
>
>>
>>- Try to login with invalid credentials more than configured number
>>of attempts. Then the account will be locked configured amount of time.
>>(Like 5 minutes). This lock time will be increased if the user locked 
>> again
>>based on a configuration.
>>- Provide invalid answers more than configured number of attempts,
>>when password recovery
>>- User onboarding with Email/SMS verification flow.
>>
>> Applies the same comment here - for the self-signup
>
>>
>>- When admin needs to block the user to login to the system (lock or
>>disable?)
>>- When admin initiated password reset flow starts.
>>- Being logged into the system on many devices simultaneously?
>>
>>

> We need to identify this states different from the account lock..
>
>>
>>
>> *When will the account be disabled?*
>>
>>
>>
>>
>>
>>- When admin needs to inactivate user.
>>
>>

>
>>
>> What is the best way handle account disable check? We can do this from a
>> inceptor level, then we need to check account disable in each operation.
>>
>> Thanks
>> Isura.
>>
>>
>>
>>
>>
>> *Isura Dilhara Karunaratne*
>> Senior Software Engineer | WSO2
>> Email: is...@wso2.com
>> Mob : +94 772 254 810 <+94%2077%20225%204810>
>> Blog : http://isurad.blogspot.com/
>>
>>
>>
>>
>
>
> --
> Thanks & Regards,
> Prabath
>
> Twitter : @prabath
> LinkedIn : http://www.linkedin.com/in/prabathsiriwardena
>
> Mobile : +1 650 625 7950 <(650)%20625-7950>
>
> http://facilelogin.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

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

Re: [Dev] Account Lock/Disable Feature in IS 6.0.0

[Prabath Siriwardena]

Hi Isura,

Please find my comment inline...

On Fri, Jan 20, 2017 at 2:02 AM, Isura Karunaratne  wrote:

> Hi all,
>
>
> We are working on implementing account lock/disable features for IS 6.0.0.
>
> *Account Lock: *
>
>- User *must not *be able to login to the system.
>- Admin user *can* update the user attributes and assign roles
>(account is active)
>- User cannot start a  password recovery flow.
>
>
In summary the user cannot do any actions with the system - but the
Administrators can.


> *Account Disable: *
>
>- User *must not* be able to login to the system.
>- Admin user *can not* update the user attributes and cannot assign
>roles until enabling the account. (inactive state)
>- User cannot start a  password recovery flow.
>
> Neither the user nor the Administrator can do any actions on this user.
Special case, the Administrator can enable the user account.


>
>
> *When will the account be locked?*
>
>
>
>- Self Signup users until account confirmation
>
> This is special status - and we need to identify this status different
from the account lock. A user in this status can request to resend the
confirmation code.

Also one (an Administrator) should be able to setup a policy to wipe out
all the unconfirmed accounts after sometime. Also there can be cases we
still let unconfirmed users login to the system - but only a limited set of
functionality is allowed.

>
>- Try to login with invalid credentials more than configured number of
>attempts. Then the account will be locked configured amount of time. (Like
>5 minutes). This lock time will be increased if the user locked again based
>on a configuration.
>- Provide invalid answers more than configured number of attempts,
>when password recovery
>- User onboarding with Email/SMS verification flow.
>
> Applies the same comment here - for the self-signup

>
>- When admin needs to block the user to login to the system
>- When admin initiated password reset flow starts.
>
> We need to identify this states different from the account lock..

>
>
> *When will the account be disabled?*
>
>
>
>
>
>- When admin needs to inactivate user.
>
>
>
> What is the best way handle account disable check? We can do this from a
> inceptor level, then we need to check account disable in each operation.
>
> Thanks
> Isura.
>
>
>
>
>
> *Isura Dilhara Karunaratne*
> Senior Software Engineer | WSO2
> Email: is...@wso2.com
> Mob : +94 772 254 810 <+94%2077%20225%204810>
> Blog : http://isurad.blogspot.com/
>
>
>
>


-- 
Thanks & Regards,
Prabath

Twitter : @prabath
LinkedIn : http://www.linkedin.com/in/prabathsiriwardena

Mobile : +1 650 625 7950

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

Re: [Dev] [Architecture] Account Lock/Disable Feature in IS 6.0.0

[Rushmin Fernando]

Isura, as per my understanding, in most of the cases 'inactive' user are
treated as non-existing users.

So from the domain model side we should have a method to .

 get the active users (since this the default case, we can even name
the method as getUsers() )

and another method to 

 get the user including inactive users

When it comes to operations, we anyway have to have an interceptor in the
authentication flow to refuse locked users (inative users will no even be
considered)



On Fri, Jan 20, 2017 at 3:32 PM, Isura Karunaratne  wrote:

> Hi all,
>
>
> We are working on implementing account lock/disable features for IS 6.0.0.
>
> *Account Lock: *
>
>- User *must not *be able to login to the system.
>- Admin user *can* update the user attributes and assign roles
>(account is active)
>- User cannot start a  password recovery flow.
>
> *Account Disable: *
>
>- User *must not* be able to login to the system.
>- Admin user *can not* update the user attributes and cannot assign
>roles until enabling the account. (inactive state)
>- User cannot start a  password recovery flow.
>
>
>
> *When will the account be locked?*
>
>
>
>- Self Signup users until account confirmation
>- Try to login with invalid credentials more than configured number of
>attempts. Then the account will be locked configured amount of time. (Like
>5 minutes). This lock time will be increased if the user locked again based
>on a configuration.
>- Provide invalid answers more than configured number of attempts,
>when password recovery
>- User onboarding with Email/SMS verification flow.
>- When admin needs to block the user to login to the system
>- When admin initiated password reset flow starts.
>
>
>
> *When will the account be disabled?*
>
>
>
>
>
>- When admin needs to inactivate user.
>
>
>
> What is the best way handle account disable check? We can do this from a
> inceptor level, then we need to check account disable in each operation.
>
> Thanks
> Isura.
>
>
>
>
>
> *Isura Dilhara Karunaratne*
> Senior Software Engineer | WSO2
> Email: is...@wso2.com
> Mob : +94 772 254 810 <+94%2077%20225%204810>
> Blog : http://isurad.blogspot.com/
>
>
>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
*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

[Dev] Account Lock/Disable Feature in IS 6.0.0

[Isura Karunaratne]

Hi all,


We are working on implementing account lock/disable features for IS 6.0.0.

*Account Lock: *

   - User *must not *be able to login to the system.
   - Admin user *can* update the user attributes and assign roles (account
   is active)
   - User cannot start a  password recovery flow.

*Account Disable: *

   - User *must not* be able to login to the system.
   - Admin user *can not* update the user attributes and cannot assign
   roles until enabling the account. (inactive state)
   - User cannot start a  password recovery flow.



*When will the account be locked?*



   - Self Signup users until account confirmation
   - Try to login with invalid credentials more than configured number of
   attempts. Then the account will be locked configured amount of time. (Like
   5 minutes). This lock time will be increased if the user locked again based
   on a configuration.
   - Provide invalid answers more than configured number of attempts, when
   password recovery
   - User onboarding with Email/SMS verification flow.
   - When admin needs to block the user to login to the system
   - When admin initiated password reset flow starts.



*When will the account be disabled?*





   - When admin needs to inactivate user.



What is the best way handle account disable check? We can do this from a
inceptor level, then we need to check account disable in each operation.

Thanks
Isura.





*Isura Dilhara Karunaratne*
Senior Software Engineer | WSO2
Email: is...@wso2.com
Mob : +94 772 254 810 <+94%2077%20225%204810>
Blog : http://isurad.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [UUF] Boolean values are not get stored properly in injected js variable from sendToClient()

[Manuranga Perera]

@Indunil
1. Without the for loop can we just do sendToClient("signupClaims",
claimProfile.claims); will that work?
2. Why do need to send all the claims to front-end JS anyway? aren't those
already used in HBS?

@Sajith
1. I keep seeing people trying to manually convert java to json. Can we
give a better option? maybe have callOSGiServiceAsJson?



On Fri, Jan 20, 2017 at 7:17 AM, Indunil Upeksha Rathnayake <
indu...@wso2.com> wrote:

> Hi,
>
> Thanks all for your responses.  Yes in my case it doesn't need to convert
> boolean to string. But if needed, as sajith mentioned, seems like have to
> import that class in the script with Java.type Nashorn extension.
>
> Thanks and Regards
>
> On Fri, Jan 20, 2017 at 10:52 AM, SajithAR Ariyarathna 
> wrote:
>
>> Hi Indunil,
>>
>> Seems like the problem is in your script.
>>
>> Boolean.toString(claimForProfile[i].getRequired())
>>
>>  I believe your intention here is to call java.lang.Boolean#toString(boolean
>> b) method, right? But Nashorn doesn't know that, because you haven't
>> imported java.lang.Boolean class in your script. In order to use a Java
>> class in your script, first you have to import that class in your script
>> with Java.type Nashorn extension [1]. (see 'call Java class' sample in
>> the features-app sample)
>> Since you haven't imported java.lang.Boolean class, Nashorn thinks
>> Boolean.toString is a JS function, thus it is serialized to "function
>> Boolean() { [native code] }".
>>
>> Anyway, You don't need to convert boolean values to strings here. So
>> let's remove Boolean.toString
>>
>> [1] https://docs.oracle.com/javase/8/docs/technotes/guides/
>> scripting/prog_guide/javascript.html#A1147187
>>
>> Thanks.
>>
>> On Fri, Jan 20, 2017 at 10:13 AM, SajithAR Ariyarathna > > wrote:
>>
>>> Hi Indunil,

 claimProfileMap["required"] = Boolean.toString(claimForProfile[i].
 getRequired());

>>> I don't see a particular reason to convert boolean to string. You can
>>> just use the boolean value directly.
>>>
>>> Anyhow, we will fix this.
>>> Thanks.
>>>
>>> On Fri, Jan 20, 2017 at 7:47 AM, Indunil Upeksha Rathnayake <
>>> indu...@wso2.com> wrote:
>>>
 Hi,

 The code segment I have used as follows.

 function getProfile() {
 var claimProfile;
 try {
 // Get Claim Profile
 claimProfile = 
 callOSGiService("org.wso2.is.portal.user.client.api.ProfileMgtClientService",
 "getProfile", ["self-signUp"]);
 } catch(e) {
 return {errorMessage: "Failed to retrieve the claim profile."};
 }
 var claimForProfile = claimProfile.claims;

 var claimProfileArray = [];

 for (var i = 0; i < claimForProfile.length; i++) {
 var claimProfileMap = {};
 claimProfileMap["displayName"] = 
 claimForProfile[i].getDisplayName();
 claimProfileMap["claimURI"] = claimForProfile[i].getClaimURI();
 if (claimForProfile[i].getDefaultValue()) {
 claimProfileMap["defaultValue"] = 
 claimForProfile[i].getDefaultValue();
 }
 claimProfileMap["claimLabel"] = 
 claimForProfile[i].getClaimURI().replace("http://wso2.org/claims/";, "");
 claimProfileMap["required"] = 
 Boolean.toString(claimForProfile[i].getRequired());
 claimProfileMap["regex"] = claimForProfile[i].getRegex();
 claimProfileMap["readonly"] = 
 Boolean.toString(claimForProfile[i].getReadonly());
 claimProfileMap["dataType"] = claimForProfile[i].getDataType();
 claimProfileArray[i] = claimProfileMap;
 }
 sendToClient("signupClaims", claimProfileArray);
 return {
 "signupClaims": claimProfileArray
 };
 }

 ​
 Thanks and Regards


 On Thu, Jan 19, 2017 at 10:03 PM, Manuranga Perera 
 wrote:

> when sending boolean value as a string(converting boolean to string
>> using "Boolean.toString()"
>
> Not very clear what you are saying here. Can you please show the code.
>
> On Thu, Jan 19, 2017 at 4:23 PM, Danushka Fernando  > wrote:
>
>> HI
>> Seems its calling [1] and [2] is something its getting called. When
>> we have a boolean as a string probably that happens. But not sure that's
>> expected.
>>
>> [1] https://github.com/google/gson/blob/0636635cbffa08157bdb
>> d558b1212e4d806474eb/gson/src/main/java/com/google/gson/Gson
>> .java#L580
>> [2] https://developer.mozilla.org/en-US/docs/Web/JavaScript/
>> Reference/Global_Objects/Object/toSource
>>
>> Thanks & Regards
>> Danushka Fernando
>> Senior Software Engineer
>> WSO2 inc. http://wso2.com/
>> Mobile : +94716332729 <+94%2071%20633%202729>
>>
>> On Thu, Jan 19, 2017 at 7:43 PM, Indunil Upeksha Rathnayake <
>> indu...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> It's returning 

Re: [Dev] [APIM][C5] Intermittent error while loading Swagger Definition

[Fazlan Nazeem]

On Tue, Jan 10, 2017 at 5:19 PM, Thusitha Thilina Dayaratne <
thusit...@wso2.com> wrote:

> Hi Thilini,
>
> It seems that some services are getting register before all the carbon
> transports get registered.  Could you please create a github issue for this.
> We'll look into this.
>

Hi,

Any update on this. We are unable to test our REST apis due to this, and
have to restart the server few times to make it work.


>
> Thanks
> Thusitha
>
> On Tue, Jan 10, 2017 at 4:55 PM, Thilini Shanika 
> wrote:
>
>> Hi all,
>>
>> We are experiencing an issue while loading swagger definition via
>> SwaggerDefinitionService. Intermittently, after a server restart, we are
>> getting 'Swagger definition not found ' error while loading a given
>> swagger definition by path.
>>
>> For example, if we are loading http://localhost:9090/
>> swagger?path=/api/am/store/v0.10/apis definition (by
>> /api/am/store/v0.10/apis
>>  base
>> path), intermittently the definition cannot be retrieved and getting
>> following error.
>>
>> {"error": "Swagger definition not found for path /api/am/store/v0.10/apis"}
>>
>> But after one or more server restarts, we can load the swagger definition 
>> with the given base path, successfully.
>>
>> When we were debugging, getSwaggerDefinition implementation in 
>> SwaggerDefinitionService, we observed that intermittently 
>> serviceRegistry.getServiceWithBasePath(path) [1] turned to be empty. So that 
>> the swagger definition could not be loaded.
>>
>> Any clue on this behavior of not having a service registered with a given 
>> base path, intermittently?
>>
>> [1] 
>> https://github.com/wso2/msf4j/blob/v2.1.0/swagger/src/main/java/org/wso2/msf4j/swagger/SwaggerDefinitionService.java#L75
>>
>>
>>
>>
>> --
>> Thilini Shanika
>> Senior Software Engineer
>> WSO2, Inc.; http://wso2.com
>> 20, Palmgrove Avenue, Colombo 3
>>
>> E-mail: tgtshan...@gmail.com
>>
>>
>
>
> --
> Thusitha Dayaratne
> Software Engineer
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> Mobile  +94712756809 <+94%2071%20275%206809>
> Blog  alokayasoya.blogspot.com
> Abouthttp://about.me/thusithathilina
> 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

Fazlan Nazeem

*Software Engineer*

*WSO2 Inc*
Mobile : +94772338839
<%2B94%20%280%29%20773%20451194>
fazl...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev