-1 for configurable feature. This could potentially open up a security
hole. Also since this is not something that's going to vary based on the
customer (enrollment is a general use case) - I believe we should choose a
method.

On Wed, Jun 10, 2015 at 11:06 AM, Harshan Liyanage <[email protected]> wrote:

> Yeah. +1 for configurable feature.
>
> Lakshitha Harshan
> Software Engineer
> Mobile: *+94724423048*
> Email: [email protected]
> Blog : http://harshanliyanage.blogspot.com/
> *WSO2, Inc. :** wso2.com <http://wso2.com/>*
> lean.enterprise.middleware.
>
> On Wed, Jun 10, 2015 at 10:48 AM, Inosh Perera <[email protected]> wrote:
>
>> Hi all,
>>
>> If it is configurable whether to use the 'ask user for password" or
>> admin assign it(auto generated) it would be ideal.
>>
>> Regards,
>> Inosh
>>
>> On Wed, Jun 10, 2015 at 10:46 AM, Dulitha Wijewantha <[email protected]>
>> wrote:
>>
>>> Hi guys,
>>> The usual approach will work fine for normal web application scenarios
>>> where the user is invited to the web app. But our scenario is specific
>>> where the user mainly uses the account to enroll the device. The problem
>>> Harshan mention is critical if we follow the proposed approach.
>>>
>>> How about we do this - when the admin creates the user, the a default
>>> password is generated and email to the user as previously. The account,
>>> however - is setup with limited permission whereby the user can only
>>> perform device enrollment. When the user logs into the MDM console we
>>> prompt the user to change his password since he is using a default
>>> generated password.
>>>
>>> Cheers~
>>>
>>> On Wed, Jun 10, 2015 at 10:30 AM, Milan Perera <[email protected]> wrote:
>>>
>>>> +1. I think we should do this because user should have the freedom to
>>>> choose the password under some kind of password policy.
>>>>
>>>> On Wed, Jun 10, 2015 at 9:59 AM, Kasun Dananjaya Delgolla <
>>>> [email protected]> wrote:
>>>>
>>>>> +1. @Harshan-I think what Prabath mentions is just end user changing
>>>>> the password if required. So it's not necessarily 2 times. Anyway it's the
>>>>> similar approach we had in 1.1.0. And I don't see an alternative to this
>>>>> method. So I think we better do this.
>>>>>
>>>>> On Wed, Jun 10, 2015 at 5:43 AM, Harshan Liyanage <[email protected]>
>>>>> wrote:
>>>>>
>>>>>> Hi Prabath,
>>>>>>
>>>>>> That sounds ok to me. But will it break the end-user experience since
>>>>>> the users have to login to MDM console and then to enroll the device
>>>>>> instead of directly enrolling the device (2 MDM logins vs 1 login)?
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Lakshitha Harshan
>>>>>> Software Engineer
>>>>>> Mobile: *+94724423048*
>>>>>> Email: [email protected]
>>>>>> Blog : http://harshanliyanage.blogspot.com/
>>>>>> *WSO2, Inc. :** wso2.com <http://wso2.com/>*
>>>>>> lean.enterprise.middleware.
>>>>>>
>>>>>> On Wed, Jun 10, 2015 at 12:34 AM, Prabath Abeysekera <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>>> Guys,
>>>>>>>
>>>>>>> I'm planning to do the $Subject.
>>>>>>>
>>>>>>> Right now we ourselves have implemented a functionality where an
>>>>>>> email is triggered upon creating users. However, this particular
>>>>>>> functionality appears to be already there with a much better 
>>>>>>> implementation
>>>>>>> as part of IS components. What it does is, adminstrators can opt to 
>>>>>>> create
>>>>>>> a user in the user management system with "ask user for password" 
>>>>>>> option,
>>>>>>> which would automatically trigger an email with a preconfigured template
>>>>>>> when the user creation is all done. Then the user can log into the MDM
>>>>>>> console and set himself a password for further use. We can even enforce
>>>>>>> captcha validation using the existing functionality in IS.
>>>>>>>
>>>>>>> Once this step is done, we can then go on to invite users for
>>>>>>> enrolling their devices.
>>>>>>>
>>>>>>> Please shout if there's any issue with the above suggested approach.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Prabath
>>>>>>> --
>>>>>>> Prabath Abeysekara
>>>>>>> Technical Lead
>>>>>>> WSO2 Inc.
>>>>>>> Email: [email protected]
>>>>>>> Mobile: +94774171471
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Kasun Dananjaya Delgolla
>>>>>
>>>>> Software Engineer
>>>>> WSO2 Inc.; http://wso2.com
>>>>> lean.enterprise.middleware
>>>>> Tel:  +94 11 214 5345
>>>>> Fax: +94 11 2145300
>>>>> Mob: + 94 771 771 015
>>>>> Blog: http://kddcodingparadise.blogspot.com
>>>>> Linkedin: *http://lk.linkedin.com/in/kasundananjaya
>>>>> <http://lk.linkedin.com/in/kasundananjaya>*
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Milan Harindu Perera
>>>> Software Engineer
>>>> *WSO2, Inc*
>>>> (+94) 77 309 7088
>>>> lean . enterprise . middleware
>>>> <http://lk.linkedin.com/in/milanharinduperera>
>>>>
>>>
>>>
>>>
>>> --
>>> Dulitha Wijewantha (Chan)
>>> Software Engineer - Mobile Development
>>> WSO2 Inc
>>> Lean.Enterprise.Middleware
>>>  * ~Email       [email protected] <[email protected]>*
>>> *  ~Mobile     +94712112165 <%2B94712112165>*
>>> *  ~Website   dulitha.me <http://dulitha.me>*
>>> *  ~Twitter     @dulitharw <https://twitter.com/dulitharw>*
>>>   *~Github     @dulichan <https://github.com/dulichan>*
>>>   *~SO     @chan <http://stackoverflow.com/users/813471/chan>*
>>>
>>
>>
>>
>> --
>> Inosh Perera
>> Software Engineer, WSO2 Inc.
>> Tel: 0785293686
>>
>
>


-- 
Dulitha Wijewantha (Chan)
Software Engineer - Mobile Development
WSO2 Inc
Lean.Enterprise.Middleware
 * ~Email       [email protected] <[email protected]>*
*  ~Mobile     +94712112165*
*  ~Website   dulitha.me <http://dulitha.me>*
*  ~Twitter     @dulitharw <https://twitter.com/dulitharw>*
  *~Github     @dulichan <https://github.com/dulichan>*
  *~SO     @chan <http://stackoverflow.com/users/813471/chan>*
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to