This is an Early AccessEarly Access (EA) features are opt-in features that you can try out in your org by asking Okta Support to enable them. Additionally, the Features page in the Okta Admin Console (Settings > Features) allows Super Admins to enable and disable some EA features themselves. feature. To enable it, please contact Okta Support.
Enforce Okta Device Trust for Native Apps and Safari on OMM-managed iOS devices
This Okta Device Trust solution for Native Apps and Safari on OMMAn acronym for Okta Mobility Management. OMM enables you to manage your users' mobile devices, applications, and data. Your users enroll in the service and can then download and use managed apps from the Apps Store. Managed apps are typically work-related, such as Box or Expensify. As an administrator, you can remove managed apps and associated data from users' devices at any time. You can configure policies, such as data sharing controls, on any of your managed apps. See Configuring Okta Mobility Management for more information. managed iOS devices allows you to prevent unmanaged iOS devices from accessing enterprise services through browsers and native applications.
Key benefits
- Ensures that only users with OMM-enrolled iOS devices can access SAMLAn acronym for Security Assertion Markup Language, SAML is an XML-based standard for exchanging authentication and authorization data between an identity provider (IdP) and a service provider (SP). The SAML standard addresses issues unique to the single sign-on (SSO) solution, and defines three roles: the end user, the IdP, and the SP. Here's how SAML works through Okta: SP-initiated flow: the end user requests (principally through a browser) a service from the SP. The SP requests and obtains an identity assertion from the IdP (in this case, Okta). On the basis of this assertion, the SP can decide whether or not to authorize or authenticate the service for the end user. IdP-initiated flow: with Okta as the IdP, an end user goes to the Okta browser and clicks on an app, sending a SAMLResponse to the configured SP. A session is established with the SP, and the end user is authenticated. and WS-Fed cloud apps.
- Provides a frictionless end user experience by utilizing Okta Mobile for iOS
Requirements
- Works with:
- Any SAML or WS-Fed cloud 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. in the Okta Integration Network
- iOS apps that support web-based federation to Okta, and the Safari mobile browser
- Devices are running Okta-supported versions of iOS
- Okta Mobility Management (OMM) is configured for the orgThe Okta container that represents a real-world organization.
- Okta Mobile app is installed on end user devices (otherwise, 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. are prompted to install it)
- End-user devices are OMM-enrolled (otherwise, end users are guided through the enrollment flow)
Procedure
This procedure has two parts:
Part Ⓐ — Enable the global Device Trust setting for your org
- Configure OMM 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. Dashboard, go to Security > Device Trust.
- Click Edit.
- In the iOS Device Trust section, select Enable iOS Device Trust.
- In Trust is establish by..., make sure Okta Mobility Management is selected.
- Click Save.
Part Ⓑ — 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.
- The Sign On policy example below shows how to create Device Trust rules to manage access to Office 365. For other apps, the section If the user's 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. is any of these is not present.
- When processing a Sign On policy rule for an app configured with the Trust or Not trusted condition, Okta suspends normal rule processing and redirects the user to Okta Mobile to assess whether the device is trusted or not (that is, OMM-enrolled). If Okta assesses the device to be untrusted, the user is prompted to enroll in OMM.
- While it is possible to create rules that include the Not trusted condition, Okta will not apply such a rule in this Early Access version of the feature. This is because end users with untrusted devices are forced to enroll their device in OMM to become trusted. Therefore, we recommend that you create a Trusted-Allow rule similar to Rule 2 below, with our without the MFA action.
Overview
By default, all Client 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
- 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 example as a guide.
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.
Example Whitelist
- 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 needs to be the same for all rules you create for this example.
- Under Location, specify the user location to which the rule will apply. The Location option you select needs to be the same for all rules you create for this example.
- Configure client settings:
- Configure Device Trust.
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.
¨ Any is unselected.
þ Trusted is selected.
¨ Not trusted is unselected.
ACTIONS
- Configure Access:
-
þ Prompt for factor is selected.
- Click Save.
- Create Rule 2.
Allowed 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 needs to 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 needs to be the same for all rules in this example.
- Configure client settings:
- Configure Device Trust.
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
þ Any is selected.
¨ Trusted is unselected.
¨ Not trusted is unselected.
ACTIONS
- Configure Access.
-
þ Prompt for factor is selected.
- Click Save.
Allowed 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 needs to be the same for all the rules you create for this example.
- Under Location, select the same Location option that you selected in Rule 1. The Location option you select needs to be the same for all the rules you create for this example.
- Configure client settings:
- Configure Device Trust.
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.
þ Any is selected.
¨ Trusted is unselected.
¨ Not trusted is unselected.
ACTIONS
- Configure Access.
- Click Save.
Denied is selected.
Rule 4: — 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 3.
Known Issues
- Box currently is not supported with this Device Trust solution. We recommend using Box for EMM.
- Trust message may cause confusion — In the Device Trust section of the Add/Edit Sign On Rule dialog box, the message "Trusted" and "Not trusted" are available only after configuring Device Trust displays in some circumstances when Device Trust is configured in Security > Device Trust, which may cause confusion. Make sure that you have selected the correct platforms in the Client section of the dialog box.
- Change Device Trust settings to Any under some circumstances — If you decide to ask Okta Support to disable Device Trust capability for your org, make sure to first change the Device Trust setting in the app sign on policy rules to Any (Applications > app > Sign On). If you do not make this change and then later have Okta Support re-enable Device Trust capability for your org, the Device Trust setting in app sign on policy rules will take effect immediately, which you may not have expected.
Caveats
-
Device Trust does not apply to apps accessed via chicletsThe "buttons" that appear on an end user's Home page and represent each application they wish to access through Okta. Clicking the button allows the end user to instantly sign in and authenticate themselves into their chosen app. This term is obsolete and has been replaced by the term "app". within Okta Mobile.
- Okta supports password-less authentication only for Office 365 apps — 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 (OMM-enrolled), end users can access the app. If the device is not trusted, end users are prompted to enroll in Okta Mobility Management (OMM).
- End users are not returned to the Settings app under some circumstances — When iOS end users who are not OMM-enrolled use the iOS Settings app to add a Gmail account to the native Mail app, they are prompted to enroll in OMM. Following enrollment, end users are prompted to tap the Home button to return to Settings. Instead of being redirected to the Gmail sign-in screen, end users see the Okta MDM Configuration page. Advise affected end users to try to configure Gmail again.
- 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.
-
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.
Top