WSO2 IoT Server enables you to register mobile devices via the BYOD or COPE device enrollment scenario. Data containerization allows you to have a separation between data. Therefore, if you are registering your device via the BYOD scenario you are able to have a clear separation between your personal data and the enterprise data. To understand the underlying concept clearly, take a look at the example given below.
MobX uses WSO2 IoT Server to manage and monitor the employees mobile devices and applications. Alex joins as the new Engineering team manager and needs to register the personal mobile device with WSO2 IoT Server, but is concerned because Alex doesn't want to expose the personal data on the device to the Organization. On the other hand, MobX is concerned about not letting the other applications installed in Alex's device to access the confidential enterprise data. For example, Alex has installed an application for enterprise docs on the device. This application has access to all the enterprise docs and the personal docs as they are all stored in the same location. Therefore, it is important to clearly separate the enterprise and personal data in a BYOD device enrollment scenario. Follow the steps given below to enable data containerization on your device.
The following subsections will provide details on how data containerization is achieved via the managed-profile feature.
Setting up the work profile
Data containerization for Android devices was implemented using the Managed Profile feature that is available on the Android devices that support the Android Lollipop OS or upwards. Let's take a look at the how data containerization works on WSO2 IoT Server.
- When you download and install the Android Agent on your Android mobile device, the agent will check if the device supports the managed profile feature.
If the device supports the managed profile feature, the agent will prompt the user to set up the work profile before the installation.
Having the Android Lollipop OS version or above will not enable you to set up the work profile. The setup might fail because of the OS customizations that would have been done on some of the devices by the manufacturers.
- Once the profile is set up, the Android agent is automatically copied into the new work profile. Therefore, WSO2 IoT Server will prompt you to uninstall the agent you downloaded previously as it was installed in the devices personal profile.
After setting up the work profile you need to follow the default steps to register an Android device with WSO2 IoT Server.
Once the registration process is completed, navigate to the launcher of the device and you will be able to see the applications that are used by the worker profile and the personal profile. The applications having the red icon are used by the WSO2 IoT Server work profile.
- Using this approach, you don't have to switch between the personal profile and work profile as all the applications used by each profile is shown in the same launcher.
- Based on the underlying architecture, the profiles have their own storage locations that can not be accessed by each other.
Applying Android device operations
After registering your device with WSO2 IoT Server you can apply operations on a device.
The Android agent is the profile owner of the newly created work profile and only has control over it. Therefore, now the agent is unable to perform operations that affect the entire device, such as changing the device PIN and wiping data of the entire device.
If your Organization has imposed a policy to restrict the usage of the camera, you will not be able to use the camera application that is installed in the work profile. You will only be allowed to used the camera application that is installed in your personal profile.
The enterprise wipe operation will delete the enterprise-related data along with the work profile on your device while keeping the personal data intact.