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:
- managementHint
- OktaVerify.AuthenticatorOperationMode
- OktaVerify.AutoRegistration
- OktaVerify.DeviceRegistrationSecret
- OktaVerify.EnrollmentOptions
- OktaVerify.OrgUrl
- OktaVerify.SerialNumber
- OktaVerify.UDID
- ReportApplicationPerformance
- ReportBugs
- ReportCrashLogs
- ReportDiagnostics
- ReportLocalFileLog
managementHint
Use this configuration to specify a secret key, which indicates that a device is managed.
| Value [String] | Description |
|---|---|
|
|
The secret key for management attestation. |
OktaVerify.AuthenticatorOperationMode
Early Access release
Use this configuration on shared devices to block user enrollments in Okta Verify.
| Value [String] | Description |
|---|---|
|
|
Blocks user enrollments on the device. Use this value for shared devices. |
This configuration is available in Okta Verify 9.73.0 and later.
OktaVerify.AutoRegistration
Early Access release
Enables Sensor Mode on managed devices.
Sensor Mode allows devices to register in Okta through a device registration secret and send device signals without requiring user enrollment.
By default, this setting isn't enabled.
| Value [String] | Description |
|---|---|
|
|
Enables Sensor Mode at the device level. The value is case sensitive. |
This configuration is available in Okta Verify 9.73.0 and later.
OktaVerify.DeviceRegistrationSecret
Early Access release
Use this configuration to specify the device registration secret that lets a managed device register with Okta without a user.
Configure this setting together with OktaVerify.AutoRegistration, OktaVerify.OrgUrl, and OktaVerify.SerialNumber.
| Value [String] | Description |
|---|---|
|
|
The value of the device registration secret. Okta shows this value only once, when you create the secret. See Create a device registration secret. |
This configuration is available in Okta Verify 9.73.0 and later.
OktaVerify.EnrollmentOptions
Early Access release
Configure whether users are prompted to enroll in Okta Verify. For shared devices that use Sensor Mode, set the value to Disabled. This option isn't required for registration, but it lets a universal link skip inline enrollment and collect device signals without a user.
| Value [String] | Description |
|---|---|
|
|
Users are prompted to enroll in Okta Verify if they sign in with Okta FastPass but don't yet have an Okta Verify account on their device. |
|
|
Users are prompted to add an Okta Verify account if the app is running and they try to access a resource that has a registered or managed device condition. |
|
|
Users aren't prompted to enroll in Okta Verify. Use this value for shared devices that use Sensor Mode. |
This configuration is available in Okta Verify 9.73.0 and later.
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.
| Value [String] | Description |
|---|---|
|
|
The sign-in URL for your org. For example, |
OktaVerify.SerialNumber
Enable the collection of serial identifiers on managed devices.
| Value [String] | Description |
|---|---|
|
|
A predefined macro provided by the MDM provider. For details, check the requirements of your MDM provider. If the MDM configuration doesn't provide this value, Okta Verify reports an empty value. |
OktaVerify.UDID
Enable the collection of unique device identifiers on managed devices.
| Value [String] | Description |
|---|---|
|
|
A predefined macro provided by the MDM provider that contains the unique device identifier. For details, check the requirements of your MDM provider. If the MDM configuration doesn't provide this value, Okta Verify reports an empty value. If your org implements user-driven device enrollment, the MDM doesn't have a UDID value. Substitute the UDID with the generated device ID value. For example, in Jamf Pro this is |
ReportApplicationPerformance
Configure the collection of app performance reports.
| Value [Boolean] | Description |
|---|---|
|
|
Performance reports are collected. This is the default. |
|
|
Performance reports aren't collected. |
Choosing this value might affect the Okta team's ability to assist with troubleshooting.
This configuration is available in Okta Verify 9.29 and later.
ReportBugs
Configure whether users can submit bug reports.
| Value [Boolean] | Description |
|---|---|
|
|
Users can submit feedback and include bug reports. This is the default. |
|
|
The Send feedback menu is unavailable. |
Choosing this value might affect the Okta team's ability to assist with troubleshooting.
This configuration is available in Okta Verify 9.29 and later.
ReportCrashLogs
Configure the inclusion of console logs in crash reports.
| Value [Boolean] | Description |
|---|---|
|
|
Crash reports include console logs. This is the default. |
|
|
Crash reports don't include console logs. |
Choosing this value might affect the Okta team's ability to assist with troubleshooting.
This configuration is available in Okta Verify 9.29 and later.
ReportDiagnostics
Configure the app diagnostics collection.
| Value [Boolean] | Description |
|---|---|
|
|
App use diagnostics such as non-fatal errors are recorded. This is the default. |
|
|
Diagnostics of app use are disabled. |
Choosing this value might affect the Okta team's ability to assist with troubleshooting.
This configuration is available in Okta Verify 9.29 and later.
ReportLocalFileLog
Configure local file logging and export. This configuration is available for Okta Verify 9.29 and later.
| Value [Boolean] | Description |
|---|---|
|
|
Users can save logs locally and export them from the Send feedback menu. This is the default. |
|
|
Logs aren't included when users submit feedback. |
Choosing this value might affect the Okta team's ability to assist with troubleshooting.
This configuration is available in Okta Verify 9.29 and later.