eScan BlogeScan Blog    eScan WebsiteeScan Website    eScan ForumeScan Forum    eScan FeedseScan Feeds     
    
Languages:     

From eScan Wiki

Jump to: navigation, search

Pre-Requisites for Managing iOS Devices

Overview

The eScan EMM requires a SSL certificate to manage your iOS devices from the EMM console. This document gives you information on all the pre-requisites for managing iOS devices and how you can import the SSL certificate. It also briefs on what the certificate is about and where you can purchase the same.


Steps required:

  1. Make sure you have a dedicated IP. You can have static IP or use NAT *
  2. Decide on a domain name.
    You need to decide a domain name for your EMM console to which the connecting devices are directed to your server, for eg: emm.mycompany.com
  3. Add A-record. Creating an A-record will re-direct anyone who visits emm.mycompany.com to the dedicated IP. For more information on creating your A-record please contact your DNS provider/Name Server Provider.
  4. Make sure that the below ports are made available for proper functionality.
    Ports: 10443,2021,2221,2222,2225,2226,443,3333.
    In case, you are using NAT or NO-IP, port redirection to the local Corporate 360 server will be required.
  5. Acquiring the SSL certificate from an Apple approved Certificate Authority (CA) **. Refer below link for more help on "How to generate a SSL certificate using Certificate Authority (CA)".
    http://wiki.escanav.com/wiki/index.php/Escan/english/escan11/eScan_Management_Console/EMM/Generate_SSL_Cert_iOS_Mgmt
  6. Import certificate and start managing your iOS devices.

* If you are using NATing please refer this link for more information
https://en.wikipedia.org/wiki/Network_address_translation

** List of Apple Approved CA https://support.apple.com/en-us/HT204132


Please Note:

  1. This is not the iOS certificate or some certificate that will be provided by Apple.
  2. This is a normal SSL certificate that organization's use on their server for SSL communication (https). Eg: When you connect to a website www.escanav.com you are on a secured connection, as this server 'escanav.com' has a SSL certificate installed.
  3. If you are having the server as 'emm.mycompany.com', you need to get a SSL certificate for the domain emm.mycompany.com. You will have to buy this from a CA or generate it for free.
  4. The certificate thus bought from the CA has to be renewed every year or if it is for free it has to be renewed every 3 months.
  5. This certificate needs to be imported in the console, for the server and the Apple servers to communicate securely.

How to import a SSL certificate in the eScan Corporate 360 EMM console?

A. To add the certificate when you log into the eScan Corporate 360 console for the first time:

  1. Click on eScan Mobility Management (EMM). It opens the EMM console use only for Android and iOS devices.
  2. Under To manage iOS devices you need to add a Trusted CA Certificate, click on Start with iOS. It opens a new window where you can import your certificate files.
  3. Browse the file from your local drive.
  4. Save the files.
    You will see a confirmation message “Certificate added successfully ”.
Note: Make sure you add an authentic CA certificate in .crt file format and .key file format for the key. Self-signed file will not be accepted.


B. To add the CA certificate if

  1. You had selected to proceed with "Start with Android (without iOS)" earlier
  2. or

  3. You have deleted the previous certificate please follow the steps below:

  1. On the left menu click Settings.
  2. Select Certificate Management tab.
  3. Click the Add button. The Add Certificate window is displayed.
  4. Browse the file from your local drive.
  5. Save the files. You will see a confirmation message “Certificate added successfully”.

What is a CA certificate?

To manage iOS devices on the EMM console you are required to add a trusted CA certificate. A certificate authority (CA) is a trusted entity that issues electronic documents that verify a digital entity’s identity on the Internet. The digital certificate is an essential part of secure communication and plays an important part in the public key infrastructure (PKI). Certificates typically include the owner's public key, the expiration date of the certificate, the owner's name and other information about the public key owner.


Why is a CA Certificate required?

The certificate is from a trusted third party who is responsible for physically verifying the legitimacy of the identity of an individual or organization before issuing a digital certificate. It guarantees that the individual granted the unique certificate is, in fact, who he or she claims to be. This allows others (relying parties) to rely upon signatures or on assertions made about the private key that corresponds to the certified public key.


How to purchase a CA certificate?

Please contact an authentic SSL certificate issuing authority (like Lets Encrypt (free provider), Rapid SSL , Comodo etc.) to purchase a CA certificate. Make sure the certificate they issue is mentioned among the list in the link below.

List of Apple Approved CA https://support.apple.com/en-us/HT204132


How to create your A-record for the dedicate IP?

Creating an A- record will re-direct anyone who visits your EMM to the dedicated IP. For more information on creating your A-record please contact your ISP.


Deployment Scenarios

The eScan EMM for iOS devies can be used in different scenarios as below.

Scenario 1: eScan server is installed on a system and a Static IP (Public IP) is assigned to the system.

Scenario 2: eScan server is installed on a system locally and NAT with port redirection is done to the server system.


Note:

1. SSL Sniffing devices provide their own Certificate, which would be rejected by EMM and iOS during the validation process. Disable SSL Sniffing for Network Interfaces of EMM.

2. Self-Signed Certificates are not accepted.


eScan Copyright © 2015 MicroWorld Technologies Inc.- AntiVirus & Content Security.       Send your feedback to solutions@escanav.com eScan Wiki

    Privacy policy  About eScan Wiki  Disclaimers   This page has been accessed 11,908 times.