Mobile device management: Difference between revisions

Jump to navigation Jump to search

Mobile device management (view source)

Revision as of 08:36, 28 September 2022

1,577 bytes added ,  28 September 2022
→‎Third-party MDM providers
Line 9: Line 9:
== Third-party MDM providers ==
== Third-party MDM providers ==


[[Resco Mobile CRM]] app can be managed by MDM providers, such as '''Microsoft Intune''' or '''MobileIron'''. Contact your MDM provider to check if they support Resco.
[[Resco Mobile CRM]] app can be managed by MDM providers, such as '''Microsoft Intune''', '''Citrix Xen Mobile''' or '''Google Enterprise Distribution'''. Our App Store / Play Store app can be used for MDM distribution with limited support of security features (see the [[Mobile device management#Security|Security section]] below). More advanced MDM integration requires requesting a [[Custom mobile apps|custom mobile app]] with MDM integration.


MDM admins can control which version of Resco app is installed on the managed devices, or even restrict certain features of our app. However, Resco apps require a [[Resco_mobile_apps#App_permissions|set of permissions]] for their function, too strict control can break the app.
MDM admins can control which version of Resco app is installed on the managed devices, or even restrict certain features of our app. However, Resco apps require a [[Resco_mobile_apps#App_permissions|set of permissions]] for their function, too strict control can break the app.
Line 27: Line 27:
For example, if you have a custom JavaScript solution that you have meticulously tested with a certain version of the app or a finetuned custom integration solution, you might decide to skip some releases so that you don't have to test everything anew. However, in order to be eligible for Resco support, you need to update your app at least once a year. Also, the operating systems on mobile devices should be kept up to date at least once a year.
For example, if you have a custom JavaScript solution that you have meticulously tested with a certain version of the app or a finetuned custom integration solution, you might decide to skip some releases so that you don't have to test everything anew. However, in order to be eligible for Resco support, you need to update your app at least once a year. Also, the operating systems on mobile devices should be kept up to date at least once a year.


If you want to use MDM for centralized distribution of the app on a larger number of devices, this should not be a problem. To this date, the Resco support team has been able to help with any requested MDM solution. In this scenario, the MDM provider should request a custom version of the Resco app, either as an IPA file (iOS) or APK/AAB file (Android). Resco support will provide a version of the app ready to be signed by the customer's provisioning profile and certificate.
If you want to use MDM for centralized distribution of the app on a larger number of devices, this should not be a problem. To this date, the Resco support team has been able to help with any requested MDM solution. In this scenario, the MDM provider should request a custom version of the Resco app, either as an IPA file (iOS) or APK/AAB file (Android). Resco support will provide a version of the app ready to be signed by the customer's provisioning profile and certificate. In the case of [[Custom mobile apps|Custom Mobile App]], you have full control over requesting the new version, and you’ll be served by our semi-automated build system.


We have received reports from our customers, that in the case of iOS, many have successfully used the app store version of the app for distribution - no need for a custom installation file from Resco. However, we are happy to provide such custom files if needed. Contact Resco support for more information.
We have received reports from our customers, that in the case of iOS, many have successfully used the app store version of the app for distribution - no need for a custom installation file from Resco. However, we are happy to provide such custom files if needed. Contact Resco support for more information.
Line 34: Line 34:


In the case of security, the situation can be more complicated. The common use cases for security features of MDM include:
In the case of security, the situation can be more complicated. The common use cases for security features of MDM include:
* Using key-value pairs for prefill URL, name, or even password of the CRM
* Using app-specific configuration (key-value pairs) for prefilling URL, name, etc. See [[Mobile_device_management#App-specific configuration support|App-specific configuration support section]].
* Setting up Exchange or SharePoint access
* Setting up Exchange or SharePoint access
* Restricting the communication between the managed Resco app and non-managed apps
* Restricting the communication between the managed Resco app and non-managed apps
* Blocking features like copy/paste, taking screenshots, and much more.
* App-specific restrictions blocking features like copy/paste, taking screenshots, enforcing encryption, and much more
* Initiating a private VPN to access protected enterprise resources
* Enabling conditional access to enterprise resources


{{Note|Keep in mind that if you block email clients, the app cannot send a log file to the support email address.|Warning}}
{{Note|Keep in mind that if you block email clients, the app cannot send a log file to the support email address.|Warning}}


The process is the same as for distribution - you need a custom IPA/APK/AAB file. However, in this case, the MDM needs to add their custom wrapper for our app. The exact procedure depends on the MDM, often, this is a website where you upload the app to receive a wrapped version, or there is a program for that. In some cases, a wrapped iOS app needs to be re-signed; sometimes this is done by the wrapping process. The customer and their MDM provider are responsible for the wrapping - Resco support is ready for consultations.
Enabling security features varies across different MDM providers and platforms. Some of them (e.g., Citrix on iOS or MS Intune on Android) require '''Mobile Application Management (MAM) SDK''' to be included in the app, while others (e.g., MS Intune on iOS) provide wrapping tools that take app installation (IPA / APK / AAB) and inject protection layer on a binary level. Some of the scenarios are described below.


A different option is to use SDK. The MDM provider gives us their SDK and we have to integrate it into our app. However, this approach is generally discouraged: the SDK is a black box from our point of view and we cannot predict how the code will react, because we use Xamarin. We recommend using key-value pairs in the case of iOS.
=== MDM support on iOS ===


For Android and Windows Store versions, we do have an app with integrated Intune SDK that we can build on-demand, without the need for wrapping (in theory, as the MDM requirements can change any time).
iOS has support for MDM systems incorporated in the operating system. Some of the security features are supported out-of-the-box, even for apps having no specific MDM support. Here is the list of supported security features for specific MDM providers:
 
{| class="wikitable sortable"
! Feature || Microsoft Intune || Citrix Xen Mobile || Other MDMs
|-
| Deployment || AppStore app & custom apps || AppStore app & custom apps || AppStore app & custom apps
|-
| App-specific configuration || AppStore app & custom apps || AppStore app & custom apps || AppStore app & custom apps
|-
| App-specific restrictions || Custom app wrapped with Intune App Wrapping Tool || Custom app with Citrix MAM SDK || No support
|-
| Private VPN support and CA || Custom app wrapped with Intune App Wrapping Tool || Custom app with Citrix MAM SDK || No support
|}
 
=== MDM support on Android ===
 
Currently, we support only Microsoft Intune and Google Enterprise Distribution on Android. Google Enterprise Distribution is supported without any requirements for the app: even the Google Play store version can be used. Microsoft Intune support requires a custom-built mobile app with MS Intune MAM SDK opted in.
 
Integrating the Android app with MDM is straightforward. You can typically choose the Play Store app from the list. In the case of custom mobile apps, choose the “Line-of-business app” option and upload the APK installation produced by our branding process.


=== Use enterprise authentication on Windows apps ===
=== Use enterprise authentication on Windows apps ===
Retrieved from "https://docs.resco.net/wiki/Special:MobileDiff/7398"

Navigation menu