Enforce Okta Device Trust for Native Apps and Safari on MDM-managed iOS devices
Okta Device Trust for iOS allows you to prevent unmanaged iOS devices from accessing enterprise services through browsers and native applications.
Requirements
- iOS devices running Okta-supported versions of iOS
- MDM provider support:
- Minimum – any Mobile Device Management (MDM) provider that supports managed appAn abbreviation of application. Essentially, it is a web-based site used to perform any number of specific tasks, and requires authentication from end users by signing in. configuration
- Recommended – MDM providers that support (1) managed app configuration and (2) the ability to convert an end user-installed Okta Mobile app instance to a managed app
- Apps:
Procedures
This procedure has three main steps:
STEP ① — Enable the global Device Trust setting for your org
- From the Okta AdminAn abbreviation of administrator. This is the individual(s) who have access to the Okta Administrator Dashboard. They control the provisioning and deprovisioning of end users, the assigning of apps, the resetting of passwords, and the overall end user experience. Only administrators have the Administration button on the upper right side of the My Applications page. console, go to Security > Device Trust.
- In the iOS Device Trust section, click Edit.
- Select Enable iOS Device Trust.
- Select the option(s) that correspond to your MDM provider:
- Trust is established by: VMware
- Integration type: Okta Mobile-based (Workspace ONE UEM)
- Trust is established by: Microsoft Intune
- Trust is established by: MobileIron
- Trust is established by: Other
- Integration type: Okta Mobile-based.
- Click Next.
-
Copy the provided Secret Key to your clipboard by clicking the copy icon
adjacent to the field. You'll enter the Secret Key later in your MDM provider's app configuration as described in STEP ②. Important: Make a note of the provided Secret Key Value, as this is the only time it will appear in Okta. If you generate a new Secret Key by clicking the Reset iOS secret Key button, make sure to also update your MDM configuration with the new key.
- In the Mobile device management provider field, add or modify the name of your MDM providerOkta pre-populates this field if you selected VMware, Microsoft Intune, or MobileIron in Trust is established by.. The content of this field is displayed to end usersIn Okta literature, we generally refer to "end users" as the people who have their own Okta home page (My Applications), using apps to authenticate into all of their apps. End users do not have any administrative control. When we refer to "users" we are generally referring to the individual(s) who have administrative control. when they enroll their device.
- In the Enrollment link field, enter a web address for redirecting end users with unenrolled devices. For example, you may want to redirect these users to a page with enrollment instructions or the enrollment page of your selected MDM (assuming the MDM provider supports web-based enrollment).
- Click Save. Screenshot
- Proceed to STEP ②.
| MDM | Options |
|---|---|
| Workspace ONE UEM
(formerly AirWatch) |
|
| Microsoft Intune |
|
| MobileIron |
|
| None of the above |
Important: Don't select the SAML-based option. It does not apply to this Device Trust solution.
|
STEP ② — Integrate Okta into your third party MDM provider
Click: Important to know before you begin
Recommended MDM capabilities
At minimum, your MDM must support managed app configuration. For best results, we recommend that you integrate with an MDM that can do the following:
- Set Okta Mobile to be a managed app
- Set Okta Mobile to install on end-user devices silently and automatically when they enroll in your chosen MDM
- Set the MDM to convert end user-installed Okta Mobile app instances to a managed app
- Use the managed app configuration to configure the key-value pair
Ensure the best end user experience
Your end users will have a better experience when accessing your managed corporate resources if their iOS device is already enrolled in your MDM provider and Okta Mobile was already installed silently on the device through the MDM provider's app store. If Okta Mobile is not installed already, end users are guided to install it through the MDM app store. If Okta Mobile is installed but not already managed by the MDM provider, end users are guided through the app management process before they can access device trust-secured apps.
- Configure your MDM provider to manage Okta Mobile and to install it on end user devices if it is not installed already.
- Configure the key/value pair through your MDM provider's managed app configuration as described in their documentation:
- DomainA domain is an attribute of an Okta organization. Okta uses a fully-qualified domain name, meaning it always includes the top-level domain (.com, .eu, etc.), but does not include the protocol (https).: Enter the URL of your Okta orgThe Okta container that represents a real-world organization.
- Key:managementHint
- Value: Use the Secret Key value that you saved in Step 1.
- Click Next.
- Proceed to STEP ③.
Note: The Key/Value pair is case sensitive.
STEP ③ — Configure app Sign On policy rules in Okta
Click: Important to know before you begin
- Only App, Org, and Super admins can configure app Sign On policies.
- When processing a Sign On policy rule for an app configured with the Trust or Not trusted condition, Okta suspends normal rule processing and uses Okta Mobile to assess whether or not the device is trusted. If Okta assesses the device to be untrusted, one of the following occurs:
- If you configured a Sign On policy rule to deny untrusted devices, users are prompted to enroll in your MDM provider.
- If you configured a Sign On policy rule to issue an MFA challenge to users with untrusted devices, such users are presented an MFA challenge.
Overview
By default, all ClientEssentially, a client is anything that talks to the Okta service. Within the traditional client-server model, Okta is the server. The client might be an agent, an Okta mobile app, or a browser plugin. options in the App Sign On Rule dialog box are pre-selected. Notice that the Trusted and Not trusted options in the Device Trust section are not selectable unless you deselect the following options in the Client section Screenshot:
- Exchange ActiveSync or Legacy Auth client
- Other mobile (e.g. BlackBerry)
- Other desktop (e.g. Linux)
To configure more granular access to the app, selectively apply conditions as you create one or more prioritized rules based on:
- Who users are and/or the groupsGroups allow you to organize your end users and the apps they can access. Assigning apps to large sets of end users is made easier with groups. to which they belong
- Whether they are on or off network or within a defined network zone
- The type of client running on their device (Office 365 apps only)
- The platform of their mobile or desktop device
- Whether or not their devices are Trusted
Whitelist approach to creating Sign On policy rules
- Create one or more permissive rules to support the scenarios that will allow access to the app, then assign those rules the highest priority.
- Create a Deny catch-all rule that will apply to users who don't match the permissive scenarios you created in Step 1. Assign the Deny catch-all rule the lowest priority, just above Okta's Default RuleThe Default Rule is already created and cannot be edited. The Default Rule is designed to allow access to all client types from any device and platform and network locations. It is applied to users who don't match any of the more restrictive rules that have higher priority. . In the whitelist approach described here, the Default rule is never reached because it is effectively negated by the Deny catch-all rule.
For important information about creating Sign On policy rules, see Add Sign On policies for applications.
Procedure
Note: This example shows Device Trust rules for managing access to Office 365. For other apps, note that the section If the user's client is any of these is not present.
- In Okta, go to Applications and click the SAML or WS-Fed-enabled app that you want to protect with Device Trust.
- Click the Sign On tab, scroll down to the Sign On Policy, and click Add Rule.
- Configure one or more rules using the following examples as a guide.
This example illustrates how you can design an app sign on policy that allows access to web browsers and Modern Auth clients, requires MFA for all access, and denies access to untrusted iOS devices.
Example Whitelist
Click the image to enlarge
- Enter a descriptive name for the rule.
CONDITIONS
- Under People, specify whether to apply the rule to individuals only or to individuals and groups. The People option you select must be the same for all the rules you create for this example.
- Under Location, specify the user location to which the rule will apply. The Location option you select must be the same for all the rules you create for this example.
- Configure client settings:
- Configure Device Trust.
- Exchange ActiveSync or Legacy Auth client
- Other mobile (e.g. BlackBerry)
- Other desktop (e.g. Linux)
Type:
þ Web browser or Modern Auth client is selected.
¨ Exchange ActiveSync client is is unselected.
Mobile:
þ iOS is selected.
¨ Android is unselected.
¨ Other mobile is unselected.
Desktop:
¨ Windows is unselected.
¨ macOS is unselected.
¨ Other desktop is unselected.
Tip: To make Trusted and Not Trusted options selectable:
Trusted and Not trusted options in the Device Trust section are selectable only when all of the following options in the Client section are not selected:
¨ Any is unselected.
þ Trusted is selected.
¨ Not trusted is unselected.
ACTIONS
- Configure Access:
- Click Save.
- Create Rule 2.
Allowed is selected.
þ Prompt for factor is selected.
Click the image to enlarge
- Enter a descriptive name for the rule.
CONDITIONS
- Under People, select the same People option that you selected in Rule 1. The People option must be the same for all rules in this example.
- Under Location, select the same Location option that you selected in Rule 1. The Location option must be the same for all rules in this example.
- Configure client settings:
- Configure Device Trust.
- Exchange ActiveSync or Legacy Auth client
- Other mobile (e.g. BlackBerry)
- Other desktop (e.g. Linux)
Type:
þ Web browser or Modern Auth client selected.
¨ Exchange ActiveSync client is unselected.
Mobile:
¨ iOS is unselected.
þ Android is selected.
þ Other mobile is selected.
Desktop:
þ Windows is selected
þ macOS is selected
þ Other desktop is selected
Tip: To make Trusted and Not Trusted options selectable:
Trusted and Not trusted options in the Device Trust section are selectable only when all of the following options in the Client section are not selected:
þ Any is selected.
¨ Trusted is unselected.
¨ Not trusted is unselected.
ACTIONS
- Configure Access.
- Click Save.
- Create Rule 3.
Allowed is selected.
þ Prompt for factor is selected.
Click the image to enlarge
- Enter a descriptive name for the rule.
CONDITIONS
- Under People, select the same People option that you selected in Rule 1. The People option you select must be the same for all rules you create for this example.
- Under Location, select the same Location option that you selected in Rule 1. The Location option you select must be the same for all rules you create for this example.
- Configure client settings:
- Configure Device Trust.
- Exchange ActiveSync or Legacy Auth client
- Other mobile (e.g. BlackBerry)
- Other desktop (e.g. Linux)
Type:
þ Web browser or Modern Auth client selected.
¨ Exchange ActiveSync client is unselected.
Mobile:
þ iOS is selected.
¨ Androd is unselected.
¨ Other mobile is unselected.
Desktop:
¨ Windows is unselected.
¨ macOS is unselected.
¨ Other desktop is unselected.
Tip: To make Trusted and Not Trusted options selectable:
Trusted and Not trusted options in the Device Trust section are selectable only when all of the following options in the Client section are not selected:
¨ Any is unselected.
¨ Trusted is unselected.
þ Not trusted is selected.
ACTIONS
- Configure Access.
- Click Save.
Denied is selected.
- Enter a descriptive name for the rule.
CONDITIONS
- Under People, select the same People option that you selected in Rule 1. The People option you select must be the same for all rules you create for this example.
- Under Location, select the same Location option that you selected in Rule 1. The Location option you select must be the same for all rules you create for this example.
- Configure client settings:
- Configure Device Trust.
- Exchange ActiveSync or Legacy Auth client
- Other mobile (e.g. BlackBerry)
- Other desktop (e.g. Linux)
Type:
þ Web browser or Modern Auth client selected.
þ Exchange ActiveSync client is selected.
Mobile:
þ iOS is selected.
þ Android is selected.
þ Other mobile is selected.
Desktop:
þ Windows is selected.
þ macOS is selected.
þ Other desktop is selected.
Tip: To make Trusted and Not Trusted options selectable:
Trusted and Not trusted options in the Device Trust section are selectable only when all of the following options in the Client section are not selected:
þ Any is selected.
¨ Trusted is unselected.
¨ Not trusted is unselected.
ACTIONS
- Configure Access.
- Click Save.
Denied is selected.
Rule 5: Default sign on rule – Any client, All platforms; Any Trust; Allow access
The Default sign on rule is already created and cannot be edited. In this example, the Default rule is never reached because it is effectively negated by Rule 4.
Click the image to enlarge
Caveats
- Securing access to Box — To secure access to the Box app, we recommend that you use Box for EMM. If you want to use this Okta Device Trust solution instead of Box for EMM, you must contact Box Support and ask them to enable Safari View Controller (SVC) for your Box tenant
- If Device Trust and Okta Mobile Connect are both enabled — End users trying to access an app enabled for Okta Mobile Connect (OMC) and secured by Device Trust go through the Device Trust authentication flow if the app has been configured with any Device Trust Sign On policy rule. Otherwise, they go through the OMC flow.
- End users are not redirected to the app sign-in page under some circumstances — When this Device Trust solution is enabled, if end users sign into an Okta-federated Gmail or Salesforce account and later delete the account, they are redirected to the Okta Home page instead of the app's sign out page.
- Okta supports password-less authentication only for Office 365 apps (assumes that Okta Mobile is installed) — For all other apps, end users are presented the Okta Sign In page to enter credentials. Users are then prompted to let Okta Mobile assess the trust status of their device. If the device is trusted (MDM-enrolled), end users can access the app. If Okta Mobile assesses the device to be untrusted, one of the following occurs:
- If you configured a Sign On policy rule to deny untrusted devices, users with such devices are prompted to enroll in your MDM provider.
- If you configured a Sign On policy rule to present an MFA challenge to users with untrusted devices, such users are challenged with MFA.
- Web-based MDM enrollment fails for SVC-enabled apps — For customers integrated with an MDM provider that supports web-based enrollment (such as MobileIron), the automatic enrollment flow designed to occur in this device trust solution fails if end users try to access a Safari View Controller-enabled native app (SVC). This happens because SVC apps do not support opening the device’s Settings page, which is required to complete MDM enrollment. If the app includes a button to launch Safari, end users can tap the button and complete MDM enrollment.
- End users might disable Universal Links inadvertently and be prevented from accessing Device Trust-secured apps — If Okta Mobile is installed on the device and an end user taps the upper right corner of the screen (where breadcrumbs are typically located), the user is prompted to install Okta Mobile even though it's already installed. This happens because tapping that part of the screen inadvertently disables the Universal Link configured to open Okta Mobile. An Okta Mobile session is required in order for the user to be authenticated into the app. Advise affected end users that they can open Okta Mobile in this case by performing the following workaround:
- Open the Notes app.
- Create a new note containing this URL: https://login.okta.com/auth/oktamobile
- Click Done. This is necessary to make the URL a hyperlink.
- Long press on the link https://login.okta.com/auth/oktamobile.
- Securing an Okta-federated MDM application with this Device Trust solution — Okta recommends that you not apply a Not Trusted - Deny app sign policy to your Okta-federated MDM application. Doing so will prevent new users from enrolling their device in your MDM application and accessing other device trust-secured apps.
-
Device Trust-secured apps are shown as locked on end-user Okta Home pages — End-user Okta Home pages viewed on desktop and mobile browsers (but not in Okta Mobile) display a lock icon on all Device Trust-secured app icons if :
(1) Device Trust is enabled for the org, and . . .
(2) The device is not trusted, and . . .
(3) The end user tried to access any Device Trust-secured app from their Home page.
The lock icon remains for the duration of the session.
Known Issues
- If Intune is your MDM provider, O365 is not supported when using this Device Trust solution — If Microsoft Intune is your MDM provider and is federated to Okta, applying a Not Trusted --> Deny app sign-on policy to an Okta-federated O365 app will block end users with unmanaged iOS devices from enrolling their device in Intune. This happens because your O365 app sign-on policy is applied to Intune as well. Okta is investigating this issue. In the mean time, Okta recommends that you use Microsoft Intune MAMMobile Application Management, software and services responsible for provisioning and controlling access to internally developed and commercially available mobile apps used in business settings on both company-provided and “bring your own” smartphones and tablet computers. to manage access to O365 apps and this Okta Device Trust solution to manage access to other sensitive apps.
-
- To prevent iPadOS devices from bypassing iOS app sign-on policies configured in Okta (if any), configure a Deny/Catch-All app sign-on policy rule that applies to macOS and iPadOS devices. Place this rule last among the rules you create, just above the Default rule (Applications > Applications > app > Sign On tab).
- To prevent iPadOS device users from being affected by macOS policies app sign-on policies configured in Okta (if any), advise users to perform one of the following options:
- Option 1. All websites accessed from Safari (iPadOS 13 and higher) – In iPad settings, go to Safari settings > Request Desktop Website and then turn off the All Websites setting.
- Option 2. Per-website basis – Open Safari, tap Aa on the left side of the search field, and then tap Request Mobile Website.
- Option 3. Access the target app through its Native App version or through Okta Mobile instead of through Safari.
Related topics
From Okta
Add Sign On policies for applications
External resources
VMware
Intune
What is Microsoft Intune app management?
App configuration policies for Microsoft Intune
How to add an app to Microsoft Intune
MobileIron
The AppConfig Community
Security and Configuration Framework for iOS
Apple
Introducing Safari View Controller (for best results, open this link in Safari)