Hi Dilan,

If I assume that "Assign devices in step 6" means an enrollment of the
> devices, shouldn't this "Request Profile in step 11"
> happen as a sub-action of step 6 since it's a pre-requirement for the
> enrollment?
>

I believe as per how the DEP enrolment (and anything related to iOS) works
it is the apple server that manages all communication with its devices.
Thus, what the EMM does is talking to the Apple Server which acts as a
proxy communicating to its registered devices.

Hence, AFAIU *"Step 6"* refers to a step where a device-administrator who
registers his/her EMM server and retrieves the token from deploy.apple
server, allocates all the company owned devices to this specific
registration. Subsequently he/she creates the Profile to be sent to these
devices during enrollemnt in the EMM-Server and sends the same to the
deploy.apple server.

Finally, *"Step 11" *happens as part of the enrolment flow of the COPE
device, where the device requests its "EMM Provider" provided Profile from
the deploy.apple server.

However, it would be much clearer to understand the exact flow if we could
get ourselves a DEP account which would make the relevant docs available
for us.


Regards
-------------------------------------
*Shabir Mohamed*
*Software Engineer*
WSO2 Inc.; http://wso2.com
Email: [email protected] <[email protected]>
Mobile: +94 77 3516019 | +94 71 6583393

On Tue, Feb 9, 2016 at 11:34 AM, Dilan Udara Ariyaratne <[email protected]>
wrote:

> Hi Tharindha,
>
> With current implementation of iOS enrollment to EMM server, the mentioned
> profile in step 9 is created on the fly by EMM server when
> a device enrollment happens with the system.
>
> If I assume that "Assign devices in step 6" means an enrollment of the
> devices, shouldn't this "Request Profile in step 11"
> happen as a sub-action of step 6 since it's a pre-requirement for the
> enrollment?
>
> Also as a side note, for improved clarity of this activity diagram, it is
> better to introduce another swim lane for actor "EMM-admin" and initiate
> all relevant requests
> from there. Also, the arrow head of step 4 should be the other way around.
>
> Thanks,
> Dilan.
>
>
>
> *Dilan U. Ariyaratne*
> Software Engineer
> WSO2 Inc. <http://wso2.com/>
> Mobile: +94725197942
> lean . enterprise . middleware
>
> On Mon, Feb 8, 2016 at 11:50 AM, Tharinda Ehelepola <[email protected]>
> wrote:
>
>> Hi All,
>>
>> *Supervision was introduced by Apple in iOS 5 to differentiate
>> institutionally-owned iPhones and iPads from personally-owned devices.
>> Supervision is enabled using Apple Configurator
>> <http://www.enterpriseios.com/wiki/Apple_Configurator>, Device Enrollment
>> Program <http://www.enterpriseios.com/wiki/Device_Enrollment_Program> if
>> purchased directly from Apple.*
>>
>>
>>
>> *Requirements - WSO2 should be registered in deploy.apple.com
>> <https://deploy.apple.com/> as a organization- A device is needed which is
>> directly purchased from apple *
>> I have design below architecture for the iOS supervision mode
>> enrollment.
>>
>>
>> ​
>> Regrads,
>> Tharinda.
>> --
>>
>> *Tharinda Ehelepola*
>>
>> *Software Engineering Intern*
>> LinkedIn <https://lk.linkedin.com/in/tharindadilshan>
>> TP :      94711834769
>> Email: [email protected]
>> Web: tharinda.tk
>>
>
>
> _______________________________________________
> Architecture mailing list
> [email protected]
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to