Mobile@Work 12.11.10 for iOS
Release Notes
April 12, 2021
For complete product documentation see: Ivanti Product Documentation page.

Copyright © 2021, Ivanti. All rights reserved.
Privacy and Legal

Contents
About Mobile@Work for iOS

3

About these release notes

3

Mobile@Work upgrade information3

New features and enhancements summary

3

General features and enhancements

4

Mobile Threat Defense (MTD) features and enhancements

5

Support and compatibility
Mobile@Work for iOS supported and compatible table

66Language Support

6

Resolved issues

7Known issues

7Limitations

7

Documentation resources

8

Mobile@Work for iOS documentation

8|2About Mobile@Work for iOS
Mobile@Work for iOS is the client app that works with Core. Device users download Mobile@Work, which
automatically configures the device to function in an enterprise environment by enforcing the configuration andsecurity policies that the administrator set in Core.

About these release notes
These release notes only contain resolved and known issues, limitations, and upgrade information particular tothis patch release. For new feature and other information about the major release, please see the release notes
for that release on the Ivanti Product Documentation page.

Mobile@Work upgrade information
Use the information in this section for upgrade information specific to this release.
l

To fix an AppConnect startup issue in Wrapped apps, before upgrading to Mobile@Work version 12.3.0
or newer versions, wrap all AppConnect wrapper apps using AppConnect 4.5.2 for iOS.

NOTE: AppConnect apps built with SDKs older than version 4.5.2 will no longer work.
After an upgrade to Mobile@Work 12.11.10, if an AppConnect passcode is required, device users are prompted
to set up a new AppConnect passcode when they first launch Mobile@Work or launch an AppConnect app.
If the AppConnect passcode policy is changed to require a new passcode and Mobile@Work is upgraded,device users are prompted to set a new AppConnect passcode or biometric when they launch Mobile@Work orlaunch an AppConnect app. After some time, they are prompted again for their AppConnect passcode orbiometric.
For more information, see "AppConnect for iOS: Mandatory Updates for Client App Compatibility" at
https://help.mobileiron.com/s/article-detail-page?Id=kA12T000000kAYNSA2.

New features and enhancements summary
This section provides summaries of new features and enhancements available in this release. References todocumentation describing these features and enhancements are also provided, when available.
lGeneral features and enhancementslMobile Threat Defense (MTD) features and enhancements

For new features and enhancements provided in previous releases, see the release notes for those versions.

|3

General features and enhancements
This release includes the following new features and enhancements.
lllContent changes for re-branding and distribution: Product documentation has been re-branded toalign with Ivanti standards and is now available on the Ivanti Product Documentation page.
FIDO (Fast ID Online) devices appear in the Authenticate list: When the devices prompt the deviceuser to authenticate, Mobile@Work now displays the list of authenticator and FIDO registered desktops
in the Authenticate screen. The device user can remove/de-reigster the FIDO devices from the list.
Support for the following AppConnect Passcode history option updates in the AppConnect
Global policy in Core:oThe value options are updated to 12. This means that you can restrict device users from reusing anypassword up to the past 12 passwords.

oThe passcode reuse is case insensitive. This means that the passcode case is not considered forreuse. Devices users cannot change the case for past passcodes and reuse it. Password andpassWord are considered the same.

This feature requires Core 11.1.0.0.
For more information, see the description for Passcode history in the AppConnect Global policy field
description table in the AppConnect Guide for Core.
lMobile@Work registration updated: New UI and steps for registering for Mobile@Work are as
follows:
1. In the Mobile@Work login page, enter your Username and tap Continue.
2. Enter the Server information and tap Continue.
3. Enter the password. If a PIN is required, enter the PIN. Tap Register.

lOAuth endpoint for mutual certification authentication: If the "Mutual Authentication" feature isenabled, the security of the My Devices tab in the iOS app is further enhanced for Core server versions
11.1 or newer versions. When the iOS app's My Devices tab contacts Core, it presents the server with
the Mutual Authentication certificate. Core confirms the certificate before it evaluates the user
credentials (user name and password) sent to it. The purpose of this is to prevent a hacker fromattempting to guess the user credentials via brute-forced guessing.
NOTE: If migration path for Mobile@Work to use mutual certification authentication is notenabled, then older client installations will continue to lack mutual authentication
functionality, including the My Devices certificate pinning that has been added to theversion 11.1.0.0 Core release.

llSettings screen updated: The Mobile@Work settings screen was updated to improve consistency,
look and feel.
AppConnect passcode user interaction updates: This release streamlines and provides
improvements in the authentication user experience for AppConnect apps. The following describes the|4AppConnect passcode user interaction updates:
oIf the AppConnect passcode expires, users see an alert that the passcode has expired after theyauthenticate. Previously, the alert was visible during authentication.

oPasscode history is preserved even after AppConnect is disabled and re-enabled. Previously, thepasscode history was lost when AppConnect was disabled and re-enabled.

oIf the number of incorrect authentication attempts exceeds the number specified in the AppConnect
policy, the AppConnect app is retired or blocked depending on the action selected for the Maximum
Number of Failed Attempts Action. Previously, after the 5th attempt, users were presented with
progressively longer intervals up to the number specified before the action as configured in Core
was applied.

oAfter a passcode reset due to too many incorrect authentication attempts, the client does not flip tothe AppConnect app. Previously, the client automatically flipped to the AppConnect app.

oIf Touch ID or Face ID (biometric) authentication is enabled on Core, when users first launch anAppConnect app they are prompted to authenticate using Touch ID or Face ID. They are notprompted for the AppConnect passcode. Previously, users were prompted for their AppConnect
passcode when the AppConnect app was first launched.

oIf Touch ID or Face ID with fall back to device passcode is enabled, only device passcode is used for
fall back authentication. Previously, if the device did not have a Touch ID or Face ID set up,authentication switched to the AppConnect passcode.

oWhen changing or disabling Face ID or Touch ID, users are prompted to authenticate only if they
were not already authenticated. Previously, users were always prompted to authenticate with Face
ID or Touch ID.

oFor Face ID or Touch ID with fallback to AppConnect passcode authentication, if users Cancel
AppConnect authentication during registration, they are prompted to set up authentication when
they launch an AppConnect app. After they set up AppConnect authentication, they are not flippedback to the AppConnect app.

For more information, see "AppConnect global policy field description" and "Secure apps on iOS
Devices - User Perspective" in the AppConnect Guide for Core for the AppConnect passcode settings
field descriptions and device user experience.

Mobile Threat Defense (MTD) features and enhancements
Mobile Threat Defense (MTD) protects managed devices from mobile threats and vulnerabilities affecting
device, network, and applications. For information on MTD-related features, as applicable for the current
release, see the Mobile Threat Defense Solution Guide for Core for your platform, available under the MOBILETHREAT DEFENSE section on the Ivanti Product Documentation page.
NOTE: Each version of the MTD guide contains all Mobile Threat Defense features that are currently fully
tested and available for use on both server and client environments. Because of the gap between|5

server and client releases, new versions of the MTD guide are made available with the final releasein the series when the features are fully functional.

Support and compatibility
This section includes the components that are supported, or are compatible, with this release of the product.
NOTE: The information provided is current at the time of this release. For product versions available after
this release, see that product version’s release notes for the most current support and compatibility
information.

TABLE 1. DEFINITIONS FOR SUPPORTED AND COMPATIBLE
TermDefinition

Supported productversions

The functionality of the product and version with currently supported releases wassystematically tested as part of the current release and, therefore, will besupported.

Compatible productversions

The functionality of the product and version with currently supported releases has
not been systematically tested as part of the current release, and therefore notsupported. Based on the previous testing (if applicable), the product and version isexpected to function with currently supported releases.

Mobile@Work for iOS supported and compatible table
TABLE 2. SUPPORTED COMPONENTS
Component

Supported Version

Compatible Version

Core10.8.0.1, 11.0.0.0, 11.1.0.0

8.0.0.0 - 10.7.0.1

iOSiOS 12.0 - 14.4

iOS 11.0

Standalone Sentry

9.12.07.6.0 - 9.10.0

Mobile Threat Defense

management console: zConsole 4.28.14

Not applicable

Language Support
The following languages are supported with this product release:l

Chinese (Simplified)lChinese (Traditional)lDutch (Netherlands)|6lEnglishl

French (France)lGerman (Germany)l

Italian (Italy)lJapanesel

Koreanl

PolishlPortuguese (Brazil)lRomanian (Romania)l

Slovakl

Spanish (Latin America)

Resolved issues
For resolved issues fixed in previous releases, see the "Resolved issues" section in the release notes for thosereleases.
There are no resolved issues in this release.

Known issues
For known issues found in previous releases, see the "Known issues" section in the release notes for thosereleases.
There are known issues in this release.
l

IOS-16553: When an AppConnect app switches to Mobile@Work for authentication and a new
passcode policy update is performed at the same time, device users may not be able to enter a newpassword.
Workaround: Re-launch Mobile@Work. The New Passcode prompt will display.

lIOS-16368: In MAM-only mode, the App Threats section is visible, even though Mobile@Work cannot
detect malicious apps. This section is transient and disappears after the configuration is received fromCore.

Limitations
For limitations found in previous releases, see the "Limitations" section in the release notes for those releases.

|7

There are limitations in this release.
lIOS-16100: Device is not getting removed from the Microsoft Azure portal when device is de-registeredfrom the Microsoft Authenticator portal. As a result, Microsoft 365 Access status is not getting updated
on the device. There is no workaround for this issue.

Documentation resources
Product documentation is available on the Ivanti documentation website.
To access documentation, navigate to a specific product and click the > symbol next to the name to view all
documents in that product category.
Current release documentation is available in the main section. For prior versions, navigate to the ARCHIVEDDOCUMENTATION section at the bottom of the page.

Mobile@Work for iOS documentation
The following is a list of the documentation:lMobile@Work for iOS Release Notes
Contains the following release-specific information: new feature summary, support and compatibility,
known and resolved issues, and limitations.
For information about device registration, see the Getting Started with Core and Core Device
Management Guide for iOS and macOS Devices.

|8