Knox Manage manages the following application types: Internal applications: Applications for internal use

Size: px

Start display at page:

Download "Knox Manage manages the following application types: Internal applications: Applications for internal use"

Avice McBride
5 years ago
Views:

1 15 Applications Knox Manage manages the following application types: Internal applications: Applications for internal use Public applications: Applications that are deployed through Google's Play Store on Android devices, the Managed Google Play Store on Android Enterprise devices, and Apple's App Store on ios devices Kiosk applications: Applications running in Kiosk mode on the device Control application: Applications either blacklisted or whitelisted VPP applications: Applications distributed by using Apple's Volume Purchase Program (VPP) Users can download internal and public applications in Knox Manage device. Administrator controls application downloads and executions by activating/deactivating the internal/pubic application via Knox Manage Admin Portal. For more information about managing application policies, see Creating application management profiles. For more information about managing applications on user devices, see Managing device applications. For more information about Kiosk applications, see Kiosk Applications. For more information about VPP applications, see Managing VPP applications. Adding internal applications You can register your internal application files and configure settings for basic information, automatic update, app wrapping and ios managed app. Applications with the same package or bundle can be registered as multiple versions. To register an internal application, follow the steps below: 1. Go to Applications > Internal Applications. 2. Click to add an internal application. 340

2 3. Enter information in the Add Internal Application window. Icon: Icon images should be in JPG or PNG format and should not be larger than 5MB. Icon is registered automatically when you add Installation File. Platform: Choose between Android and ios. Android Package Name (Bundle ID for ios) and Version: are automatically extracted when you select a file. - Multiple versions of an application with the same package (bundle) name can be registered. Installation File: Click Browse, and select APK file for Android and IPA file for ios. Data shown below is automatically entered. - APK file: Name, Package Name and Version. - IPA file: Name, Bundle ID, Bundle Name, URL Scheme and Version. Name: English name of the installation file is automatically entered. Category: Select from the category list. Description: Enter detail information of application. Supported Devices: Choose among All, Phone or Tablet. Screenshot: Optional. UP to 4 files are allowed and each image should not be larger than 5MB. Service Term: Choose application service period. Enter the start/end date or check No end Date. 341

3 No integrity validation: If you click this, a cyclic redundancy check (CRC), which checks integrity of data sent by apps, is not performed. A CRC determines the check value used to ensure that there are no errors in data sent through a network, etc., and then sends it along with the data. It is only applicable to Android devices. Auto update: If you check Auto update, it checks the version of the application installed on the device to update to the latest version and notify the user accordingly. App Wrapper: When uploading internal applications on the Admin Portal, reconfigure and save them so that security policies can be controlled. - The App Wrapper function is only available on Android and Android Enterprise devices. For more information, see App wrapping. Use ios Managed App Setting: Check when you register the ios application that is developed with MDM settings that can be modified. 4. Click Save. App wrapping Using Knox Manage's App Wrapper, you can add security policy control functions, such as text copy and paste, screen lock, and screen capture, to internal applications. Another advantage of using App Wrapper is that it also allows you to insert code that enables you to control security policies for internal applications used by customers and then reconfigure the applications, without having to modify the source code. Thus, you can add new functions in a short amount of time, even if you aren't knowledgeable in platform development. Please note the following for using the Knox Manage App Wrapper: Conversion using the Knox Manage App Wrapper is limited to the internal applications. There may be copyright issues when converting public applications. The security logic application that checks the signing key may not function normally. The functions that you can configure using App Wrapper are screen capture, screen lock, text copy and paste, and registration of INI configuration files. The existing and wrapped internal applications are distinguished by different icons on the user device. Screen lock: If the EMM Client's screen is locked because of the EMM Client's Lock device after (second) value set in Profiles > Application Management Profile, then the wrapped internal applications are also locked. Therefore, you need to enter the screen lock password and unlock the screen of the EMM Client or the wrapped internal applications if you want to use them. 342

4 Configuration INI file: You can register a configuration file in wrapped applications, as well as configure additional control settings. Register wrapped applications and an INI configuration file in Profiles > Application Management Profile, and apply them to a device. Then, the INI configuration file is saved to the device's data storage. For more about how to register the INI file required for a wrapped application, see Setting up application policies. To use the INI file, you need to add the source code to read the INI file from the internal application. For more information, see Reading the configuration file. Reading the configuration file If you want to use the values included in an INI configuration file from an internal application, then you need to find the path and name of that configuration file. Then, add a source to read the text. Below describes the code that is required to read a configuration file. private String readinifile(string filename) throws FileNotFoundException, IOException, Exception { StringBuffer sb = new StringBuffer(); BufferedReader br = null; int ch = 0; br = new BufferedReader(new FileReader(fileName)); while((ch = br.read())!= -1) { sb.append((char) ch); br.close(); return sb.tostring(); // Path : /data/data/[packagename]/files/ini private String getinifolder(context context) { return context.getfilesdir() + File.separator + "ini"; // ini File Name : [packagename].ini */ private String getinifilename(context context) { return context.getpackagename() + "." + "ini"; The getinifolder function searches for the directory path where the configuration file is saved. The getinifilename function searches for the name of the {PackageName.ini file. The readinifile function reads the configuration file through the file path received as a parameter value, and then sends a text value. 343

5 The code that calls the readinifile() function after determining the existence of the file is as follows: btniniread.seton-clicklistener(new ON-CLICKListener() public void ON-CLICK(View v) { String text = null; String filepath = getinifolder(mcontext) + File.separator + getinifilename(mcontext); File file = new File(filePath); if(file.exists()) { try { text = readinifile(filepath); catch (FileNotFoundException e) { text = "FileNotFoundException"; e.printstacktrace(); catch (IOException e) { text = "IOException"; e.printstacktrace(); catch (Exception e) { text = "Exception"; e.printstacktrace(); else { text = "File Not Found"; editiniread.settext(text); ); The full path where a configuration file can be saved: getinifolder(mcontext) + File.separator + getinifilename(mcontext) Example of ios i Managed App Setting ios Managed App setting is used for modifying MDM settings of applications on ios devices. Administrator needs the Key and Value for Managed app settings when registering the application as an internal application. The following example is for registering ManagedAppConfig app and set it s default URL to 1. Get an application file from the developers. 2. Register the file in Applications > Internal Applications. 3. Click Use ios Managed App Setting in Add Internal Application window. 4. Move to Managed App Settings tab 344

6 5. Enter the server URL and in the Key-Value, and click. 6. To send a device command, go to Devices & Users > Devices and send Apply latest internal app info command after clicking of a device. 7. Make sure that the application is installed on the device with the default URL, Adding public applications Select Google Play (Android), Managed Google Play (Android), or App Store (ios) as the app store, and register applications. The default country used for searches in app stores is the Default Country Code specified in Settings > Configuration. You can also perform searches using a different country. To add public applications, follow the steps below: 1. Go to Applications > Public Applications. 2. Click. 3. Enter the information for the following items in the Add Public Application window and click. App store: Select either Google Play (Android), Managed Google Play (Android), or App Store (ios). The app store manages applications by country. - Managed Google Play (Android) is an app store for Android Enterprise devices. For more information about Google managed apps, see Adding Google Managed Apps. Set Country: To use a country other than the default country for searches in app stores, click Set Country, and select a country. Application Name: Enter the full or partial name of the app you wish to search for. - You cannot enter special characters such as * or?. 345

Icon, Platform,Version: Information provided by an app store is entered automatically and it can't be changed.

7 4. Choose an app from the application list in the Add Public Application window, and click Next. 5. Enter the basic information from Add Public Application window. Icon, Platform,Version: Information provided by an app store is entered automatically and it can't be changed. Basic Information: Information provided by an app store, such as URL, Package Name, Country, Name, and Description is entered automatically, and only Name and Description can be changed. 346

- Category: This is the category to which the app will later belong; the app will appear in this category on the device. A list of categories registered in Applications > Categories is displayed.

8 - Category: This is the category to which the app will later belong; the app will appear in this category on the device. A list of categories registered in Applications > Categories is displayed. - Description: Enter detail information of application. Service Term: Specify the service period. Enter the start/end date or check No end Date. Screenshot: The images provided by app store are automatically uploaded and cannot be changed. 6. Click Save. Adding control applications Applications can be controlled using profile. They are called Control Applications and are classified as follows: Blacklist and whitelist Pre-loaded applications Administrators can whitelist or blacklist applications in Knox Manage. Blacklist refers to the applications that are not allowed on user devices. Whitelist refers to the applications that are only allowed on user devices. Control applications can be registered, modified, or deleted in Applications > Control Applications from the Admin Portal. Applications that are registered as internal and public applications cannot be registered as control applications. To register a control applications, follow the steps below: 1. Go to Applications > Control Applications. 2. Click to add a control application. Platform: Select a platform among Android, ios, Windows. 347

9 Registration Method: Depending on the platform, choose between Manual and Extract from File. Platform Android, ios Windows Description You can enter the application information manually or extract from the file. Manual Input: Fill out the fields manually. - For Android, you can use wild card(*) when entering a package name. The wild card can be located in the middle or the end of each name, separated with.. e.g.) com.*.emm / com.knox.* / com.*.emm.* Extract from file: When you import an installation file, the Package Name, Bundle ID, Bundle Name and Application Name are automatically entered. You can enter the application information manually or through URL Search. Manual Input: Enter Package Name, Publisher and Application Name. URL: When you enter the application ID, full Package Name, Publisher and the Application Name are automatically entered. Preload App: For Windows, select whether to make the application as a preloaded application. 3. Click Save. Registering a device application as a control application To register application installed on devices as control applications, follow the steps below: 1. Go to Devices & Users > Devices. 2. Enter a search term into the search box in the upper-right corner, and click. 3. Click the Mobile ID that you want the information about. 4. Click Application tab in Device Detailed Information window. 5. Select the application to register as control application from the Applications list and click. 6. Click Yes when the confirmation pop-up appears. Viewing control applications by platform To view Control applications on all platforms in the list, follow the steps below: 1. Go to Applications> Control Applications. 348

10 2. In the list, click on the left side of the platform that you wish to search for, or click Expand All groups at the top of the list. 3. To hide the list of Control applications, click Collapse All groups at the top of the list. Managing applications Administrator can register internal applications in Knox Manage Admin Portal so that users can download the applications from Knox Manage Biz App Store (BAS). If the internal applications run on ios, you can change the Mobile Device Management (MDM) settings for ios 7.0 or later version. You can change the settings for ios from Use ios Managed App Setting in Add Internal Application window. The configured settings are automatically applied when users log into Knox Manage on their devices. Register applications available in Google's Play Store, the Managed Google Play Store, and Apple's App Store as public applications and manage them. You can search for applications in app stores and register them as public applications, as well as also sync the information about the applications and keep them up-to-date. Activating internal / public applications Internal/public applications are activated upon registration. Device command is available only when the application is in service. To activate an application with completed service, follow the steps below: 1. Go to Applications > Internal Applications or Public Applications. 2. Click Start/End Date of the application that you want to activate. 3. Enter the service period from Change Service Status window. 4. Click Yes. Deactivating internal / public applications If the administrator changes the status of an application from in service to Completed Service, users cannot download or execute the application. When you deactivate an application with profile configuration, the application is automatically removed from Application Management Profile. To change the status of the internal applications, follow the steps below: 1. Go to Applications > Internal Applications or Public Applications. 349

11 2. Click Start/End Date of the application that you want to deactivate. 3. Click Yes when the confirmation pop-up appears.. Syncing public applications Information of public applications can be updated to the latest information registered in Google Play Store (Android) and Apple App Store (ios). To update public applications manually, follow the steps below: 1. Go to Applications > Public Applications. 2. Click of the application that you want to update. 3. Click next to Version from Modify Public Application window. Syncing Google managed apps Among the public applications in Knox Manage, you can sync Google managed apps with Managed Google Play. You can directly log in to the Google Play Console, and register the approved applications as Knox Manage's public applications. If the relevant applications have already been registered as Google managed apps, then their approval status is synced. To sync a Google managed app, follow the steps below: 1. Go to Applications > Public applications. 2. To sync a Google managed app, click Sync Google Managed App. 350

12 3. Click OK in the confirmation window. Any unapproved applications on the Google Play Console are also unapproved in Knox Manage. Configuring control applications on a profile When you set up policies for control application from Profiles > Device Management Profile, the control application is shown and can be whitelisted or blacklisted. You can apply the control application to the device by entering the control application in the Application black/whitelist settings of Application tab of the Modify Android policy window after clicking the profile name in Profiles > Device Management Profile. For more information, see Registering policies. If the preloaded app applied to profile is not installed on user device successfully, the detail status can be checked in the audit record. For information about audit logs, see Audit. Viewing internal application history You can check internal application history for versions, downloads and evaluations. To view the history, follow the steps below: 1. Go to Applications > Internal Applications. 2. Click Version, Downloads, Rating of the application. Version: You can check followings in Version History window - Date: Registered date - Version: Current version of the application - Changes: Note for each version. Click to modify content of Changes. Downloads: You can check followings in Download History window. - Version: Current version of an application - Downloads: Total download count - Date: Download date - User ID: ID of users who downloaded the version - User Name: Name of users who downloaded the version Rating: You can check reviews form users in Evaluation History window. - Review with Date, Version, User ID, User Name, Rating, and Postscripts. 351

13 Application categories Public and internal applications can be sorted by category. Administrator can register up to 15 categories. The categories are shown in the order you specified, and the order can be changed. Register a default category when registering the applications, and rearrange the category whenever needed. Adding categories To add a new category, follow the steps below: 1. Go to Applications > Categories. 2. Click. 3. Enter the name and description of the category in Add Category window and click Save. Changing the category order You can change the order of application categories shown on the user's device. To make a change, follow the steps below: 1. Go to Applications > Categories. 2. Select a category. 3. Click to move up. Or, click to move down. 4. Click to save. 5. Click Yes in confirmation pop-up. Changing the application category Default categories for internal and public applications are set during application registration. You can change categories from application information or category management. To change categories, follow the steps below: 1. Go to Applications > Categories. 2. Click Number of Apps of the category to change, and you can see the application information of the category. 3. Choose an application to change category in View Application window and click. 352

14 4. Select the Category to move to in Change Category window and click Save. 353

Strengths of Knox Manage Kiosk

Strengths of Knox Manage Kiosk 16 Kiosk Applications A kiosk application is an application that is installed on a stand-alone device, featuring a touchscreen interface that displays information, and used in public spaces or workplaces.