Hi Inosh, In the step 11, you have mentioned that the device sends authentication request, generate access and refresh tokens and send it to device. However you need client credentials (client key, secret) in-order to generate access tokens. How are you planing to get these client credentials prior to generating access tokens? In the existing EMM implementation we use Dynamic-client-registration to do that. I think we can use the same here. However we need to modify the flow diagram to reflect that.
Thanks. Harshan Liyanage Software Engineer Mobile: *+94724423048* Email: hars...@wso2.com Blog : http://harshanliyanage.blogspot.com/ *WSO2, Inc. :** wso2.com <http://wso2.com/>* lean.enterprise.middleware. On Tue, Jan 26, 2016 at 2:07 PM, Inosh Perera <ino...@wso2.com> wrote: > Hi Milan, > > +1 Cant we use an embedded QR code reader or some other way to retrieve > this token? > Using QR code is possible and it would make the process usable in all many > platforms oppose to ADB where only Android is able to work with. Although > when it comes to COPE scenario, mostly it is Android devices and it is a > set of known devices so we can assume the driver change is not much of a > concern. So under the above assumption at the time of device getting > connected, we can think the drivers are already installed, which makes it > much easier to enroll because the user only needs to plugin the device. In > BYOP/CYOD scenario, this can be problematic. > > Regards, > Inosh > > > On Tue, Jan 26, 2016 at 12:29 PM, Milan Perera <mi...@wso2.com> wrote: > >> Hi Inosh, >> >> My concerns for the above proposed method as follows. >> >> AFAIU, in here what we are trying to do is to minimize the user >> interaction with the device as much as possible for the auto enrolment >> scenario. >> However according to above method, user should have to connect the device >> to a machine and has to run a script as well, hence it needs more >> interaction. >> Also, if we use ADB for this, there may be instance where PC does not >> recognize the device, which ends up manually installing drivers and etc. >> >> Why do we have to use ADB in order to do this? >> >> Cant we use an embedded QR code reader or some other way to retrieve this >> token? >> >> Regards, >> >> -- >> *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 <ar...@wso2.com> | Web: www.wso2.com >> <http://lk.linkedin.com/in/milanharinduperera> >> >> _______________________________________________ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Inosh Perera > Software Engineer, WSO2 Inc. > Tel: 077813 7285, 0785293686 > > _______________________________________________ > 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
