iOS Device

The following sections guide you through configuring iOS in WSO2 IoT Server and enrolling an iOS device. WSO2 IoT Server is bundled with the WSO2 Enterprise Mobility Management (WSO2 EMM) capabilities.

This tutorial follows the sample scenario of the Mob X organization of which Chris (the system administrator) is configuring iOS with WSO2 EMM for the organization and Alex (the device owner) is registering an iOS device.

Before you begin

WSO2 EMM supports devices on iOS 7, 8, 9, and 10.
Install Oracle Java SE Development Kit (JDK) version 1.8.* and set the JAVA_HOME environment variable. For more information on setting up JAVA_HOME on your OS, see WSO2 IoT Server documentation on Installing the Product.
Download WSO2 EMM and unzip the file . WSO2 IoT Server is bundled with WSO2 EMM capabilities. Therefore, what you will be downloading is the WSO2 IoT Server pack.

The downloaded pack is referred to as <IOTS_HOME> throughout this document.
The downloaded WSO2 IoT Server file is large. Therefore, when unzipping it the OS might extract it halfway through and stop. To avoid this, we recommend that you unzip the file via the terminal.
Example:
unzip wso2iot-3.2.0.zip
Start WSO2 IoT Server's core profile, which corresponds to the WSO2 Connected Device Management Framework (WSO2 CDMF) profile.
```
cd <IOTS_HOME>/bin
sh iot-server.sh
```
The default port assigned for the core is 9443.
In your browser, access the IoT Server Console by navigating to https://<EMM_HOST>:9443/devicemgt and log in using admin as the username and password.
Fill in the following iOS form via the WSO2 site. WSO2 will send you an email with the following information.
- The P2 repository with the iOS features, End User License Agreement (EULA) and the README.txt.
- The iOS agent source code. You can use this if you want to customize the iOS agent application in WSO2 IoT Server.
Get your certificate signed by Apple. Register your organization with the Apple Developer Enterprise Program. Thereafter, follow the steps mentioned in MDM Vendor CSR Signing Overview.

Configuring iOS support in WSO2 EMM

For the sake of simplicity in this tutorial, we are not setting up the WSO2 EMM iOS agent on your device. Therefore, we will not walk through the iOS client configurations. Note that the 'device ringing', 'sending messages', and 'getting the device location' operations require the WSO2 EMM iOS agent, so those operations will not be available in this scenario.

For more information on configuring WSO2 EMM for iOS, including iOS client configurations, see the iOS configurations guide in the WSO2 IoT Server documentation.

If you are facing issues while configuring WSO2 EMM for iOS in your testing environment, contact us and we will help you out.

Configuring WSO2 EMM to install iOS applications

Click here for more information.

The download URL for WSO2 EMM is configured for HTTP by default. Although you can install Android mobile applications using this default configuration, to install iOS applications, you need to configure it for HTTPS as it's required for the iOS MDM protocol behavior.

Follow the steps given below to configure WSO2 EMM to install iOS mobile applications:

Open the <IoT_HOME>/conf/app-manager.xml file.
Add %https% as the value for the AppDownloadURLHost property.
```
<Config name="AppDownloadURLHost">%https%</Config>
```

Chris has now done the configurations needed to allow users to register and monitor their devices with WSO2 EMM. Chris then proceeds to configure iOS support in EMM.

Configuring the IP or hostname

Click here for more information.

Thie script automatically configures the IP and creates the required SSL certificates for the IP or hostname. This method is recommended because manually configuring the IP address includes many steps and if you miss out on a step you will run into errors.

Navigate to the <IOTS_HOME>/scripts directory.
Run the change-ip script.
Example: Running the script on a Mac or Linux OS.
Tip: The script will find and replace the IP address given in argument1 (localhost) with the IP address given as argument2 (10.10.10.14), in the necessary configuration files.
```
./change-ip.sh
```

Change the current IP address of the EMM core, broker, and analytics profile.

Enter the values for EMM core SSL certificate.

Click here for more information.

Enter the requested information when prompted.

Field	Usage/Purpose
Country	The name of your country. Enter the two digit code for your country.
State	The state your organization is at.
Location	The city your organization is located at.
Organization	The name of your organization. For this scenario, we entered wso2.
Organization Unit	Defined the Team ID as the organization unit.
Email	The email is used to identify the existing users. For this scenario, we entered chris@wso2.com as the email.
Commonname	Fully qualified domain name of your server.

If you want to configure the steps manually, see the WSO2 IoT Server documentation on Configuring the IP or hostname manually and if you want to change the default ports, see Changing the Default Ports.

Installing the iOS features

Click here for more information.

After obtaining a signed CSR, the P2 repository, and the other files via email, Chris can install the specific features in the P2 repository that are required to enable iOS by following the instructions given below.

Download and extract the ios-feature-deployer that you received via email.
Copy the ios-feature-deployer folder to the <IOTS_HOME> directory.

Navigate inside the ios-feature-deployer folder on the terminal and execute the following command to install the iOS features to WSO2 IoT. Agree to the End User License Agreement (EULA) to complete the iOS configurations.

cd ios-feature-deployer 
mvn clean install -f ios-feature-deployer.xml

Tip by Chris

Tip: To verify successful installation of the iOS features, do the following:

Open the <IOTS-HOME>/wso2/components/default/configuration/org.eclipse.equinox.simpleconfigurator/bundles.info file and verify if the following properties have changed from false to true .

org.wso2.carbon.device.mgt.ios.api.utils,3.0.5.SNAPSHOT,../plugins/org.wso2.carbon.device.mgt.ios.api.utils_3.0.5.SNAPSHOT.jar,4,true

org.wso2.carbon.device.mgt.ios.apns,3.0.5.SNAPSHOT,../plugins/org.wso2.carbon.device.mgt.ios.apns_3.0.5.SNAPSHOT.jar,4,true

org.wso2.carbon.device.mgt.ios.core,3.0.5.SNAPSHOT,../plugins/org.wso2.carbon.device.mgt.ios.core_3.0.5.SNAPSHOT.jar,4,true

org.wso2.carbon.device.mgt.ios.payload,3.0.5.SNAPSHOT,../plugins/org.wso2.carbon.device.mgt.ios.payload_3.0.5.SNAPSHOT.jar,4,true

org.wso2.carbon.device.mgt.ios.plugin,3.0.5.SNAPSHOT,../plugins/org.wso2.carbon.device.mgt.ios.plugin_3.0.5.SNAPSHOT.jar,4,true

Once the ios-feature-deployer script has finished running, you can see the <IOTS_HOME>/ios-configurator directory that was created.

Navigate inside the <IOTS_HOME>/ios-configurator directory and run the ios.sh script.
```
cd ios-configurator
sh ios.sh
```

Enter the requested information when prompted. Be sure to provide the same information when configuring the iOS platform configurations.

Field	Usage/Purpose
Country	The name of your country. Enter the two digit code for your country.
State	The state your organization is at.
Location	The city your organization is located at.
Organization	The name of your organization. For this scenario, we entered MobX.
Organization Unit	Defined the Team ID as the organization unit.
Email	The email is used to identify the existing users. For this scenario, we entered chris@mobx.com as the email.
Commonname	Fully qualified domain name of your server.

This part of the script creates a key pair, generates a signature, and signs the key using the signature.

Make sure the <EnabledUpdateApi> parameter in the <IOTS_HOME>/conf/etc/webapp-publisher-config.xml file is set to false if you need to restart the server many times after configuring the IP. This configuration is enabled when you run the ios.sh script.

By enabling the update API property, the APIs and the respective web apps get updated when the server restarts. This takes some time. Therefore, if you need to restart the server many times after this configuration or when in a production environment, you need to revert back to the default setting.

Generating an MDM APNS certificate

Click here for more information.

Except for a few operations (ring, message and get location) that are performed by the WSO2 EMM agent, all the other device operations, and policies areappliedonaniOS device via it's operating system. Therefore, for the WSO2 EMM server to communicate with the operating system of the device, you need to generate the MDM APNS certificate.

The MDM APNS certificate will be referred to as the MDM certificate in the EMM Console.

Go to https://appleid.apple.com/account#!&page=create and get an Apple ID, if you do not have one already.
Go to the Apple Push Certificate Portal at https://identity.apple.com/pushcert/ and log in with your customer account details. You do not need an enterprise account for this. Your Apple ID is sufficient.
Click Create Certificate and agree to the terms and conditions.
Upload the encoded .plist file you got after signing your certificate.

Didn't get your certificate signed by Apple? Register your organization with the Apple Developer Enterprise Program and follow the steps mentioned in MDM Vendor CSR Signing Overview.
Download the generated MDM signing certificate, which is a certificate for third-party servers provided by Apple, and rename it to MDM_Certificate.
Get the USERID (TOPIC ID) from the MDM signing certificate (MDM_Certificate.pem), as it will be used later in the configuration.
You can decode the MDM signing certificate to obtain the USERID by executing the following command:
```
openssl x509 -in MDM_Certificate.pem -text -noout
```
The TOPIC ID is assigned to the UID property.
Example: UID=com.apple.mgmt.External.0dbe5637-8f16-4d9f-bac4-e18cac2f7d4e
Remove the password/pass phrase from your private key file (e.g.,customerPrivateKey.pem).
```
openssl rsa -in customerPrivateKey.pem -out customerKey.pem 
```
Merge the customer key file that was derived in the latter step with the MDM signing certificate to generate the MDM Apple Push Notification Service (APNS) Certificate. In this example, Chris merges the customerKey.pem file with the MDM_Certificate.pem file to generate the MDM_APNSCert.pem file.

Tip: Before you merge the customerKey.pem file and the MDM_Certificate.pem file, make sure both files are in the same directory.
```
cat MDM_Certificate.pem customerKey.pem > MDM_APNSCert.pem
```
Open the APNS Certificate (MDM_APNSCert.pem) and add a line break between the content of the two files. For example, if your content looks as "-----END CERTIFICATE----------BEGIN RSA PRIVATE KEY-----", add a line break after 5 dashes so that the content looks as follows:
```
-----END CERTIFICATE-----
-----BEGIN RSA PRIVATE KEY-----
```
Convert the MDM_APNSCert.pem file to MDM_APNSCert.pfx file. You need a password for this, which you will need again when configuring the iOS platform configurations.
```
openssl pkcs12 -export -out MDM_APNSCert.pfx -inkey customerPrivateKey.pem -in MDM_APNSCert.pem
```

Configuring the iOS platform

Click here for more information.

Multiple tenants can use WSO2 EMM while maintaining tenant-based isolation. The iOS platform configurations page enables tenants to customize the iOS settings based on their own requirements.

Chris proceeds to configure the iOS platform configurations by adding the generated MDM APNS certificate.

Restart WSO2 EMM's core profile. You can stop the profiles using CTRL+C respectively.
```
cd <IOTS_HOME>/bin
sh iot-server.sh
```
Log in to the device management console at https://<EMM_HOST>:9443/devicemgt using admin as the username and password if you haven't previously logged in.
Click Menu > CONFIGURATION MANAGEMENT > PLATFORM CONFIGURATIONS > iOS Configurations and fill in the form.

Use the generated MDM-APNS certificate for both the MDM certificate and the APNS certificate.
In this tutorial, you are not installing the WSO2 EMM's iOS agent on the device. Therefore, you don't need to generate the APNS certificate. The APNS certificate is used to trigger operations, such as ring, notification, and iOS. If you want to trigger these operations, you need to generate the APNS certificate and upload it.
- MDM Certificate Password: Give the same password you gave when converting the MDM_APNS certificate from the pem to the pfx format.
- MDM Certificate Topic ID: Give the topic ID of the certificate. If you are unsure of the topic ID, refer step 6 under generating the MDM APNS certificate.
Tip: To learn more about each platform setting, hover your mouse pointer over the help tip.

Creating users and a sample policy

Follow the steps given below to create two users, Alex and Chris, and a configured passcode policy. This will make it easy for you to try out the EMM quick start guide.

Tip by Chris

Have you run the sample script previously when trying out the Android quick start guide? If yes, delete the two users alex and chris, the role iotMobileUser and the sample policies that were created for Android, iOS, and Windows.

Navigate to the mobile-qsg directory located in the <IOTS_HOME>/samples directory on the terminal window.

Run the mobile-qsg.sh script to configure the iOS server settings in WSO2 EMM.

cd <IoT_PRODUCT_HOME>/samples/mobile-qsg
sh mobile-qsg.sh

When you add a new user to WSO2 EMM, the user receives an email with the username and password that needs to be used to log in to WSO2 EMM. In this quick start guide, we have not configured WSO2 EMM to send emails. Therefore you will get an error in the terminal where the core profile is running. If you don't want to see this error, you need to configure the email settings. For more information, see the WSO2 IoT Server documentation on Configuring the Email Settings.

Click here to see the error you get.

[2017-07-27 02:47:14,527] [IoT-Core] ERROR - {org.apache.axis2.description.ClientUtils} The system cannot infer the transport information from the mailto:chris@mobx.com URL.
[2017-07-27 02:47:14,527] [IoT-Core] ERROR - {org.apache.axis2.description.ClientUtils} The system cannot infer the transport information from the mailto:alex@example.com URL.
[2017-07-27 02:47:14,531] [IoT-Core] ERROR - {org.wso2.carbon.email.sender.core.service.EmailSenderServiceImpl} Error occurred while delivering the message, subject: 'You have successfully been registered in WSO2 IoT', to: 'chris@mobx.com'
org.apache.axis2.AxisFault: The system cannot infer the transport information from the mailto:chris@mobx.com URL.
	at org.apache.axis2.description.ClientUtils.inferOutTransport(ClientUtils.java:81)
	at org.apache.axis2.client.OperationClient.prepareMessageContext(OperationClient.java:288)
	at org.apache.axis2.description.OutOnlyAxisOperationClient.executeImpl(OutOnlyAxisOperation.java:249)
	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
	at org.apache.axis2.client.ServiceClient.fireAndForget(ServiceClient.java:511)
	at org.apache.axis2.client.ServiceClient.fireAndForget(ServiceClient.java:488)
	at org.wso2.carbon.email.sender.core.service.EmailSenderServiceImpl$EmailSender.run(EmailSenderServiceImpl.java:117)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
[2017-07-27 02:47:14,531] [IoT-Core] ERROR - {org.wso2.carbon.email.sender.core.service.EmailSenderServiceImpl} Error occurred while delivering the message, subject: 'You have successfully been registered in WSO2 IoT', to: 'alex@example.com'
org.apache.axis2.AxisFault: The system cannot infer the transport information from the mailto:alex@example.com URL.
	at org.apache.axis2.description.ClientUtils.inferOutTransport(ClientUtils.java:81)
	at org.apache.axis2.client.OperationClient.prepareMessageContext(OperationClient.java:288)
	at org.apache.axis2.description.OutOnlyAxisOperationClient.executeImpl(OutOnlyAxisOperation.java:249)
	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
	at org.apache.axis2.client.ServiceClient.fireAndForget(ServiceClient.java:511)
	at org.apache.axis2.client.ServiceClient.fireAndForget(ServiceClient.java:488)
	at org.wso2.carbon.email.sender.core.service.EmailSenderServiceImpl$EmailSender.run(EmailSenderServiceImpl.java:117)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

Check out the WSO2 EMM dashboard by signing in to the WSO2 EMM console using chris as the username and chrisadmin as the password: https://<EMM_HOST>:9443/devicemgt
You will then see the new iotMobileUser role, three new policies, and the two new users that were added using this script

Updating the passcode policy

As a security measure, the MobX management has asked Chris to update the passcode policy for all iOS devices so that a device user can only enter the wrong password five times. If a user fails to enter the correct password in the fifth attempt, the device will not be accessible for 15 minutes. This can be regulated in WSO2 EMM by updating the passcode policy that was already in place. Chris follows the steps given below to update the policy:

Sign out of the EMM console and log in using the following credentials:
Enter chris as the username and chrisadmin as the password.
Click LOG IN.
In the EMM console click View under POLICIES.
Click the edit logo that is on the passcode policy for iOS devices.
Update the passcode profile that is already in place by defining the maximum fail attempts as 5, and click CONTINUE.

A profile in the context of IoT Server refers to a collection of policies.
If you want to know more about each policy setting, hover your mouse pointer over the help tip.
The passcode policy that was created for this scenario has the following groups assigned. You can optionally update the groups.
1. Chris selects the set user role/s option and then selects the iotMobileuser role from the item list.
2. Click CONTINUE.
  Optionally, you can update the name and the description of the policy.
It is mandatory that the policy is assigned to Alex's mobile device, so Chris clicks SAVE & PUBLISH to make the policy active immediately.

If you SAVE the configured profile, it will be in the inactive state and will not be applied to any devices.

If you SAVE & PUBLISH the configured profile of policies, it will be in the active state. The active policies will be enforced on new devices that enroll with IoT Server based on the policy enforcement criteria. If you want to push this policy to the existing devices and want this policy to be applied to the devices, click APPLY CHANGES TO DEVICES.

Tip by Chris

You can ensure that the policy is applied on the device by going to the enrolled device page, clicking on your device and clicking the Policy Compliance tab on the Device Management console.

Another way to ensure that the policy is enforced on the device is by checking the settings in the device. For more information, see the WSO2 IoT Server documentation on Verifying Policies Applied on an iOS Device.

Publishing applications

Chris needs to publish the WSO2Con application. Let's take a look at how you can publish an application using the WSO2 IoT Server's application publisher.

Navigate to the App Publisher using the following URL: https://<IoT_HOST>:9443/publisher
Enter the username as chris and password as chrisadmin.
Click Add New Mobile Application that is under the Mobile Application drop down.
Select iOS for the Platform.
Select Enterprise as the Store Type
Download the IPA file from here and select the IPA file as shown below. The IPA file size should not exceed 200MB.

Click Next, and you get the following screen.

Enter the following details of the app.

Attribute Name	Value
Name	iOS-App
Display Name	iOS-App
Description	This is an iOS application.
Recent Changes	Leave blank.
Version	Keep the default value.
Category	Keep the default value.
Restrict Visibility	Leave blank.
Banner	Upload the `<IOTS_HOME>/samples/mobile-qsg/apps/ios/images/banner.jpg` file.
Screenshots	Upload the `<IOTS_HOME>/samples/mobile-qsg/apps/ios/images/screen1.jpg` file.
Icon file	Upload the `<IOTS_HOME>/samples/mobile-qsg/apps/ios/images/icon.jpg` file.

Click Create. The created app will appear in the created list of apps.
Now toy are directed the page that has all the created applciations.
Click Submit for Review for the iOS-App application.
Click Approve > Publish.
The iOS-App application is now available in the app store for device owners like Alex to install on their devices.

To learn more about the mobile application life cycle, see Mobile Application Lifecycle Management.

Registering the iOS device

WSO2 IoT Server supports devices on iOS 7, 8, 9, and 10.

Tip by Chris

Before you begin to enroll the device, make sure that the WSO2 IoT Server server and the device are on the same network.

Before starting to enroll the device without the iOS device agent, make sure to disable the device location on your device. Else, you run into errors.

Follow the instructions below to register an iOS device:

Sign in to the WSO2 IoT Server device management console using alex as the username and alexuser as the password.
Click Enroll New Device.
Click iOS to enroll your device with WSO2 IoTS.
Enroll the device.
1. Click Enroll Device.
2. Scan the QR code and the Safari browser will display the IoT Server iOS enrollment screen.
  After scanning the QR code you will be directed to a web page. When this page appears, the web browser will typically display an "insecure connection" message, which requires your confirmation before you can continue.
Tap Install IoT Server Certificate. The iOS devices need the root certificate to be downloaded to trust the server certificate.
The Install Profile screen appears. Tap Install.
Tip by Chris
If you are using iOS 10 with a self-signed certificate, do the following to mark it as a trusted certificate. This is required in iOS 10 because there is a change in how self-signed CA certificates are trusted by iOS devices from iOS 10 onwards.
1. Open the Certificate Trust Settings found in Settings > General > About.
2. Enable full trust for the certificate related to WSO2 IoT Server.
Tap the Skip Agent Installer link at the bottom of the screen.
In this tutorial, you are registering the iOS device with WSO2 IoT Server without installing the WSO2 iOS agent. Therefore, you will not be able to ring the device, get the device location or send notifications to the device using WSO2 IoT Server. If you want to try out the said operations, click Install IoT Server agent.
On the IoT Server Registration screen, enter your details:
- Domain - You don't need to enter the domain details for this scenario.
- Username - Enter alex as the username.
- Password - Enter alexuser as the password.
By default WSO2 EMM only supports the "bring your own device" (BYOD) registration process for the iOS platform.
Tap Log In.
Click for a troubleshooting tip
Troubleshooting tip
If you get an error stating that the server certificate is invalid, it may be because your iOS version is version 10 or a later version. Ensure that you have enabled full trust for the certificate as mentioned on this tip in step 6. To resolve, do the following:
Open the Certificate Trust Settings found in Settings>General>About.
Enable full trust for the certificate related to WSO2 EMM.
Open Settings>General, scroll to the bottom and open Profiles.
If you do not see a Profiles section, you do not have a configuration profile installed.
In the Profiles section, select the IoT profile and tap Delete Profile.
Restart the device enrollment process from step 4.
After reading the End User License Agreement (EULA), tap I accept the terms.
Tap Install when prompted to install the carbon.super Profile Service.
Getting an error? Click here for a troubleshooting tip
Troubleshooting tip
If you get an error stating that the server certificate is invalid, it may be because your iOS version is version 10 or a later version. Ensure that you have enabled full trust for the certificate as mentioned on this tip in step 6. To resolve, do the following:
Open the Certificate Trust Settings found in Settings>General>About.
Enable full trust for the certificate related to WSO2 EMM.
Open Settings>General, scroll to the bottom and open Profiles.
If you do not see a Profiles section, you do not have a configuration profile installed.
In the Profiles section, select the IoT profile and tap Delete Profile.
Restart the device enrollment process from step 4.
A warning message appears to indicate that by installing the profile the EMM will remotely manage the iOS device. Tap Install.
Tap Trust to confirm that you are aware of the device being remotely managed by installing the profile.
After the profile is installed, click Done.
Upon the successful registration, the DEVICE ADDED confirmation appears.

Since you are not installing the WSO2 EMM iOS agent in this guide, you will get a Cannot Open Page warning message after the enrollment is complete.

Trying out iOS device operations

Alex can now navigate to the Device management page, view information specific to her device, and carry out operations on the device. She follows the steps given below:

Access the EMM Management Console using alex as username and alexuser as the password.
Click the icon.
Click DEVICE MANAGEMENT.
Click on the registered device.

Alex tries out the various operations on her device via the WSO2 EMM Management Console.

NOTE:

Because we didn't install the WSO2 EMM iOS agent while registering the device, the ring device, send notifications, and get device location operations do not function. For more information on installing the agent in the registration process, you can follow the steps in the Enrolling With the iOS Agent tutorial that is in the WSO2 IoT Server documentation.

In this tutorial, you are not installing the agent. Therefore, the device location operation fails as it needs the agent to push the location details to WSO2 EMM. To avoid error logs while testing this tutorial, comment out the following configuration that is in the <IOTS_HOME>/Repository/deployment/server/devicetypes/ios.xml file.

<!--Operation>
   <Name>DEVICE_LOCATION</Name>
   <RecurrentTimes>1</RecurrentTimes>
</Operation-->

View device details

The details of each registered devices will be shown on separate pages within the Device page.

Description

Device Details

The following device information will be retrieved automatically when you register with WSO2 IoTS.

Device	This shows the name the user has given his/her device (e.g., Kim's iPhone).
Model	The type of device will be stated (e.g., iPhone, iPad)
IMEI	The International Mobile Station Equipment Identity (IMEI) number of all GSM devices. This is not applicable to devices suchasiPadswhichwork without a SIM.
Status	Indicates if the device is active, inactive or removed from WSO2 IoTS.
Ownership	Indicates if the device is your own device/Bring Your Own Device (BYOD) or if it's a Corporate-Owned, Personally Enabled (COPE) device. For the device to be a COPE device, WSO2 IoT Server must be configured to use the system server application.

Operation Log

A list of all the operations that have been carried out by you and its current status.

Location

Provides the location of your device.

Applications

A list of all the applications that have been installed on your device and the memory consumption by each application will be listed under this section.

Policy Compliance

If your device does not comply with certain criteria in the enforced policy, the aspects in which your device is none compliant will be highlighted under this section.

Device operations

Click on the operation you wish to carry out and provide the required details (if requested) to apply the selected operation on your device.

Operation	Description
Device Lock	Ability to lock a device via WSO2 EMM.
Location	Ability to receive the location of the device.
Ring	Ability to ring the device via WSO2 EMM.
Clear Password	Ability to remove a device lock via WSO2 EMM.
Enterprise Wipe	Ability to unregister a device from WSO2 EMM.
Send Notification	Ability to send a notification to the device via WSO2 EMM. The WSO2 EMM admin can use this device operation to send notifications to the WSO2 EMM users.
Wipe Data	Ability to carry out a factory reset operation on your own device via the EMM. The user will have to provide the PIN, which he/she entered when registering to EMM, to be able to wipe his/her device.

Tip by Chris

To know if a policy is applied to your device, see the WSO2 IoT Server documentation on Verifying Policies Applied on an iOS Device.

Installing an application on the iOS device

MobX wants Chris to ensure that the employees can only download mobile applications made available via the MobX app store. For this, Chris creates and publishes the WSO2Con application to the MobX app store.

Let's take a look at how Alex installs this application on the device.

Navigate to the App Store using the following URL: https://<EMM_HOST>:9443/store
Sign in using alex and alexuser as the username and password.
Click the iOS-App mobile application, and click Install.
Leave the text box empty and click Yes. This will install the application instantly on the device.
A notification pops up on the device asking permission to install the application. Click Allow.
A success message will be shown when you have successfully subscribed to the application.
Tap install on your device to finish installing the application.

Note from Chris

Remember to change the AppDownloadURLHost property value that is in the <IOTS_HOME>/conf/app-manager.xml file back to HTTP if you are trying out the quick start guide for Android or testing WSO2 EMM with Android devices.

Unregistering and uninstalling the iOS agent

Want to unregister your device from WSO2 EMM and uninstall the iOS agent that's on your device? Follow the steps given below:

Navigate to Settings > General > Profiles or Profiles & Device Management.
Tap the WSO2 Inc profiles, such as wso2 Mobile Device Management.
Tap Delete App.

Now you have successfully unregistered your device from WSO2 EMM, removed the profiles that were added when the iOS agent was installed, and uninstalled the WSO2 Device management application.

What's next?

Want to enroll your iOS device with the iOS agent? See the WSO2 IoT Server documentation on Enrolling With the iOS Agent
To know more on what you can do with iOS in WSO2 IoT Server, see the WSO2 IoT Server documentation on Working with iOS Devices.

iOS Device

Configuring iOS support in WSO2 EMM

Configuring WSO2 EMM to install iOS applications

Configuring the IP or hostname

Installing the iOS features

Generating an MDM APNS certificate

Configuring the iOS platform

Creating users and a sample policy

Updating the passcode policy

Publishing applications

Registering the iOS device

Trying out iOS device operations

Device Lock

Location

Ring

Clear Password

Enterprise Wipe

Send Notification

Wipe Data

Installing an application on the iOS device

Unregistering and uninstalling the iOS agent

What's next?