Hi all, +1 for the idea.
Considering a BYOD dis-enrollment scenario, when an user sends a dis-enrollment request to the system, are we going to change the device state to a particular state (since we are already maintaining the device life cycle) or introduce a new mechanism to support this process? Regards, On Wed, Jul 8, 2015 at 10:58 AM, Kasun Dananjaya Delgolla <[email protected]> wrote: > Hi All, > > Given below is the proposed workflows for the $subject. > > *Enrollment* > > *BYOD* > > Login -> License Agreement -> Enter critical operation PIN -> Registration > > *COPE* > > Login -> Registration > > *Dis-Enrollment* > > *BYOD -* > > [image: Inline image 2] > > *COPE - * > > *There will be no dis-enroll option for COPE devices. If a COPE device > needs to be dis-enrolled, that has to be performed through the EMM console > by the admin. Operation list will have a dis-enroll option to fulfill this > requirement.* > > Please raise your concerns on this. > > Thanks > -- > 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>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
