Okta Verify configurations for iOS devices

You can use your mobile device management (MDM) solution to deploy Okta Verify configurations to domains. The configurations enable Okta Verify functionality.

Always deploy managed app configurations to both of these preference domains:

  • Preference domain 1: com.okta.mobile
  • Preference domain 2: com.okta.mobile.auth-service-extension

Use the following keys and values to configure Okta Verify:

OktaVerify.OrgUrl

Use this configuration to pre-populate the sign-in URL so that end users don't have to enter this value when they add an Okta Verify account. For example, example.okta.com. This configuration is available for Okta Verify 7.2.0 and later.

Value (string): $org_sign-in_URL

managementHint

Use this configuration to specify a secret key, which indicates that a device is managed. For example, 3zr7Q~vw4C16FS2bH8UfS1gJ5cL6sj~x_U9PQ .

Value (string): $secret_key

OktaVerify.UDID

Enable the collection of unique device identifiers on managed devices.

Value (string): $UDID

<UDID> is a predefined macro provided by the MDM provider. If this value can't be retrieved, Okta Verify reports empty values.

OktaVerify.SerialNumber

Enable the collection of serial identifiers on managed devices.

Value (string): $serial_number

$serial_number is a predefined macro provided by the MDM provider. If you can't retrieve this value, Okta Verify reports empty values.