AppConnect for iOS key-value pairs

The following table summarizes the AppConnect for iOS key-value pairs used to configure various AppConnect features.

Table 47.  AppConnect for iOS key-value pairs

Key name

Description

Reference

MI_AC_DISABLE_OPEN_IN_ENFORCEMENT

When Yes, Open In is allowed to all apps.

Open-In data loss prevention policy details

MI_AC_DISABLE_SCHEME_BLOCKING

When true, Open In is allowed to the iOS native email app when the user taps the AppConnect app to launch an email app..

Open-In data loss prevention policy details

MI_AC_LOG_LEVEL

Specifies the log level for the app: error, info, verbose, or debug.

Configuring certificate authentication using AppTunnel with TCP tunneling for Android secure apps

MI_AC_LOG_LEVEL_CODE

Specifies the string that the device user enters to activate the verbose or debug log level.

Logging for AppConnect apps for iOS

MI_AC_ENABLE_LOGGING_TO_FILE

When Yes, an AppConnect app's logs are logged to files on the device.

Logging for AppConnect apps for iOS

MI_AC_WR_ENABLE_LOG_CAPTURE

When Yes,when emailing AppConnect-related log files from Mobile@Work, the logs of a wrapped app are emailed along with the logs of the AppConnect wrapper and the AppConnect librar

Logging for AppConnect apps for iOS

MI_AC_IOS_ALLOW_CUSTOM_KEYBOARDS

When true, the AppConnect app is allowed to use customer keyboards.

Custom keyboard control

MI_AC_WR_ALLOW_KEYBOARD_DICTATION

When true,a wrapped app can use dictation with the iOS native keyboard.

Dictation with the native keyboard is not allowed for wrapped apps

MI_AC_ENABLE_SCREEN_BLURRING

When false, screen blurring is disabled if the AppConnect app has given screen blurring control to the AppConnect library.

Screen blurring

MI_AC_CLIENT_CERT_#

Used in setting up certificate authentication from an AppConnect app to an enterprise service.

Certificate authentication from AppConnect apps to enterprise services

MI_AC_CLIENT_CERT_#_RULE

Used in setting up certificate authentication from an AppConnect app to an enterprise service.

Certificate authentication from AppConnect apps to enterprise services

MI_AC_CONTAINER_TYPE

When set to ENCLAVE, sensitive data, such as encryption keys, is stored in the Apple Secure Enclave on the device.

Heightened security for AppConnect apps using the Secure Enclave

MI_AC_USE_ORIGINAL_COOKIES_FOR_DOMAINS

Some web pages inject custom cookies into web requests. For example, when an end user taps on a link in a web page, the page's JavaScript injects a custom cookie. If a user makes such a request from a web page displayed in an AppConnect app, by default AppConnect does not include the injected cookies in the web request, which can cause the request to fail. AppConnect includes the custom cookies in the request if you include the following key in the app's app-specific configuration: MI_AC_USE_ORIGINAL_COOKIES_FOR_DOMAINS. The value of the key is a comma-separated string listing the domains for which the custom cookies should be included. Make sure no spaces are included in the value.

For example:

www.somewebsite.com,somename.someotherwebsite.com

Supported with apps built or wrapped with AppConnect 4.2.1 for iOS and supported newer versions.

 

AppConnect for Android key-value pairs