MDM app configuration

Configuration settings for Mobile Device Management (MDM) apps.

Configuration settings

App configuration settings can be specified for individual accounts or globally for all accounts.

If you are using AppConfig for iOS or Android Enterprise, then refer to those topics for more comprehensive configuration support.

Some configuration settings can be used across the mobile apps HCL Connections, HCL Connections Chat, HCL Connections Meetings, and HCL Verse. These settings use a prefix of "com.ibm.mobile" instead of "com.ibm.mobile.connections".

MDM app setting keys

Use the following keys to configure account information:

com.ibm.mobile.connections.serverURL
The account URL for the Connections server. This key is required to create an account.
com.ibm.mobile.connections.serverName
The label of the account. This key is optional. The default is to use the server host name.
com.ibm.mobile.user
com.ibm.mobile.connections.user

The user ID for the account. This key is required to create an account.

Leave this setting empty when using OAuth authentication. It is not possible to specify a user name (or password) in this environment.

com.ibm.mobile.password
com.ibm.mobile.connections.password

The password for the user. This key is optional.

Leave this setting empty when using OAuth authentication. It is not possible to specify a user name (or password) in this environment.

To configure multiple accounts, add a dot followed by a numeric suffix to the end of the key.

With many MDM solutions that support app configuration, you can use substitution variables for the user ID and password. For more information about which substitution variables are supported, see your MDM provider's documentation. For example, to create three accounts that share credentials, use the following parameters:
Note: The $USERID$ variable is used by MobileIron and %email% is used by MaaS360.
com.ibm.mobile.connections.serverURL.1=http://server.com/mobile
com.ibm.mobile.connections.serverName.1="Test Account"
com.ibm.mobile.connections.serverURL.2=http://server2.com/mobile
com.ibm.mobile.connections.serverName.2="Server2 Account"
com.ibm.mobile.connections.serverURL.3=http://server3.com/mobile
com.ibm.mobile.connections.serverName.3="Server3 Account"
com.ibm.mobile.user=$USERID$
com.ibm.mobile.password=$PASSWORD$
To create two accounts with different user IDs, use the following parameters:
com.ibm.mobile.connections.serverURL.1=http://server.com/mobile
com.ibm.mobile.connections.serverName.1="Test Account"
com.ibm.moible.connections.user.1=TestUser1
com.ibm.mobile.connections.serverURL.2=http://server2.com/mobile
com.ibm.mobile.connections.serverName.2="My  personal Account"
com.ibm.mobile.connections.user.2=%email%

The following configuration settings apply either for individual accounts or globally for all accounts. To associate these settings with an account, add the same numeric suffix used to define the account. If the configuration settings should be applied globally to all accounts, don't specify a suffix.

com.ibm.mobile.connections.RememberPassword

This key allows users to save their login password on the mobile device. When this key is set to true, users have the option to save their password so they do not need to enter their passwords each time the HCL Connections app needs to authenticate with the HCL Connections server. To prevent passwords from being saved, set the key value to false. This forces users to enter a password each time the HCL Connections app needs to authenticate with the HCL Connections server.

com.ibm.mobile.connections.InactivityTimeout

A timeout value, in minutes, that results in users being logged out of the client if no activity has taken place for the time period that is defined in this property. When the user is logged out due to inactivity, that user is required to re-enter their password, even if the password is remembered by the app. Specifying a value of 0 results in users never being logged out due to inactivity.

com.ibm.mobile.RequireDevicePasscode
com.ibm.mobile.connections.RequireDevicePasscode

This key is only supported on iOS. This key requires that a device passcode is set before a user can log in to a Connections server. Device passcodes are required in order to enable the data protection encryption feature used by the Connections app.

When this key is set to true:
  1. A device passcode must be set before the user can log in to an account.
  2. If the passcode is removed from the device, data associated with accounts that have been previously used to log in will be wiped.
If your MDM deployment pushes out device configuration profiles to devices, it is suggested you setup a passcode profile to enforce setting of the passcode on the device. This configuration setting can be used if you only push out app configurations settings.

The following configuration settings are applied globally to all accounts.

com.ibm.mobile.connections.AllowRemoveAccount

This key allows you to specify whether users can delete accounts without logging in to the accounts. This key overrides what is specified on the server configuration and if you set the value to true, any account can be deleted.

Valid values are true and false. The default value is false, which prevents deleting accounts without logging in.

com.ibm.mobile.connections.AllowExternalBrowserDomains

This key allows you to open supported http/s URLs in an external browser instead of the embedded browser in the HCL Connections application. Supported URLs are specified by the SupportedExternalBrowserDomains key.

Valid values are true and false . The default value is false , which opens the URLs in the embedded browser in the HCL Connections app.

Note: If the specified URL is a deep link or a universal link that is supported by a native application and is installed on the user's device, the URL is opened in the native application instead of an external browser.
com.ibm.mobile.connections.SupportedExternalBrowserDomains

This key specifies the domain/subdomain patterns for the websites that uses an external browser instead of the embedded browser within the HCL Connections mobile app. This value is applicable only when AllowExternalBrowserDomains is set to true.

Use a comma to separate multiple domain patterns. This key accepts wildcard subdomains ( * ) and can be specified only at the beginning. This key does not support Regular Expressions.

The following snippet shows an example how you can specify domain/subdomain rules:

  • Ensure that the AllowExternalBrowserDomains key is set to true if you want the supported URLs to open in an external browser
    <AllowExternalBrowserDomains>true</AllowExternalBrowserDomains>
  • Here www is a subdomain and hcl.com is the domain. Once you specify this rule, you would be able to open any link that exactly matches domain and subdomain. For example you would be allowed to open www.hcl.com/somepage.html but not 'somesubdomain.hcl.com
    <SupportedExternalBrowserDomains>www.hcl.com</SupportedExternalBrowserDomains>
  • Here is an example of using a wildcard * domain and using multiple domains. Using this rule, the mobile user would launch an external browser when tapping any link that was part of *.hcl.com or matched www.example.com exactly. For example, these pages would all launch an external browser on the mobile device: www.hcl.com/somepage.html, somesubdomain.hcl.comand www.example.com.
    <SupportedExternalBrowserDomains>*.hcl.com,www.example.com</SupportedExternalBrowserDomains>
com.ibm.mobile.connections.ThemeColor
This key allows you to set the Connections app theme colors. The value is a 6 character string that represents a hexadecimal color code. The default value is blank.
Note: If a value is not specified for the ForegroundColor or ThemeColor property, the default app color is used.
This setting overrides the setting for ThemeColor that is specified in the mobile configuration on the Connections server.
com.ibm.mobile.connections.ForegroundColor
This key is only supported on iOS. If you customize the HCL Connections app theme color using com.ibm.mobile.connections.ThemeColor, this key allows you to customize the color of the text and icons that are displayed in areas where the theme color is shown. The value is a 6 character string that represents a hexadecimal color code. The default value is blank.
Note: If a value is not specified for the ForegroundColor or ThemeColor property, the default app color is used.
This setting overrides the setting for ForegroundColor that is specified in the mobile configuration on the HCL Connections server.
com.ibm.mobile.connections.useSecureBrowser

This key allows you to enable the HCL Connections app to open non-HCL Connections URLs in the MDM's secure web browser instead of using the browser embedded in the HCL Connections app. This is helpful if your HCL Connections content contains URLs that can only be accessed from the MDM secure browser. Valid values are true and false. The default value is false, which specifies opening non-HCL Connections URLs in the browser embedded in the HCL Connections app.

Note: This key is only required for MaaS360 if you want to set secureBrowserPattern. For MaaS360, if the secure browser is enabled in the persona policy then the Connections app will use it for all non-HCL Connections URLs without this key set. See Configuring MaaS360 for Workplace Integration for more information.
com.ibm.mobile.secureBrowserPattern
com.ibm.mobile.connections.secureBrowserPattern
This key controls which non-HCL Connections URLs are opened in the MDM's secure browser. The value is a regular expression. If the URL that the user is attempting to open matches the regular expression, then the URL will be opened in the MDM's secure browser. If it does not match, then the URL is opened in an internal web view within the Connections app.
com.ibm.mobile.connections.DefaultNavigationOrder
This key controls the initial order of the Connections apps in the main app navigation. The value is a list of Connection app identifiers. Valid values for the Connections apps are updates, communities, files, profiles, favorites, blogs, forums, wikis, offlinefiles, activities, and bookmarks. For example,
 com.ibm.mobile.connections.DefaultNavigationOrder.1=(updates,communities,files,profiles,favorites,blogs,forums,wikis, offlinefiles,activities,bookmarks)
Also, if you add application extensions, you can specify the application extension name in the list. This setting overrides the setting for DefaultNavigationOrder that is specified in the mobile configuration on the Connections server.