Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Using Restrictions on Contacts Export for Caller ID in Workspace ONE Boxer for iOS (78210)

Last Updated: 6/4/2020Categories: InformationalTotal Views: 4891Language:
JapaneseEnglish

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Details

Boxer has the ability to provide Caller ID functionality for contacts which are saved in the app via CallKit and Contact Export. This article covers nuances of using Contact Export capabilities. With the release of iOS 11.3, Apple introduced enhanced security specific to the behavior for an existing MDM restriction. Prior to iOS 11.3, the MDM restriction for securing data within managed applications and accounts from being leaked to unmanaged destinations did allow contacts to not adhere to this restriction. This exception to the restriction allowed users to access contacts from managed apps like VMware Workspace ONE Boxer and transfer them to personal apps such as the native Contacts app.

There are two ways for Boxer users to get Caller ID. The most secure and recommended option is using iOS CallKit. End users must enable this method of Caller ID manually by following the instructions in the app Settings under Caller ID. There are limitations on this method, namely, that Caller ID capabilities will only apply to incoming calls.
Note: CallKit integration is not affected at all by what document restrictions are set in the iOS profile.

The second option called Export Contacts. The rest of this document will cover this option and the nuances that have been introduced through changes in how Apple classifies contacts in terms of moving contacts between managed and unmanaged apps.

As a result of the changes introduced in 11.3, contacts are now classified as documents and are required to adhere to restrictions related to how documents are passed between managed and unmanaged applications. The native iOS Contacts application is considered an unmanaged destination whereas Boxer is a managed destination.

There are two restrictions that admins can set on how documents and now contacts flow between managed and unmanaged apps. These options can be found when making a new iOS profile and selecting the Restrictions section:

Allow documents from managed sources to unmanaged destinations

Allow documents from unmanaged sources to managed destinations

Export contacts will only work if admins have both of the above restrictions allowed. The following configurations will result in the exporting of contacts to fail.

Allow documents from managed sources to unmanaged destinations option is unchecked

Allow documents from unmanaged sources to managed destinations option is unchecked

If both options above are unchecked, no documents regardless of source or destination, can move between managed and unmanaged apps

If only one of the restrictions above is unchecked, export contacts will not work.

If your company’s security stance does not allow for the allowing both of the restrictions above, the recommendation from Apple is to deploy a Contacts only EAS profile via the Workspace ONE UEM Console. This action results in contacts being pushed from your mail server to the device without going through Boxer. Mail and Calendar functionality will need to be disabled or end users will be able to use native iOS mail that doesn’t have the DLP protections that Boxer does:

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

KB
•
内置容器 root 密码过期，导致无法在现有部署上安装 vRealize Automation 8.0 和 8.0.1 或累积更新修补程序 (78235)

KB
•
Azure Windows：安装 NSX Agent 后，无法通过 RDP 连接到启用了加速网络的 Windows 虚拟机 (78071)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Workspace ONE

Related Versions:

Take Our Survey

Support Assistant