Simple enrolment
Pre-fill your Okta address so people do not type it, and pass the device serial number from your MDM's macro.
{
"domainName": "example.okta.com",
"OktaVerify.SerialNumber": "{{DeviceSerialNumber}}"
}Android app directory · Identity and security
These are the managed app configuration keys Okta documents for Okta Verify on Android. They help IT make enrolment simpler, mark the device as managed through management attestation and decide how much diagnostic data and feedback the app can send. Okta notes that key names are case-sensitive, so copy them exactly. Some keys need a minimum Okta Verify version.
com.okta.android.auth Common setups
Copy a setup into the managed configuration of a policy, then adjust the values. Each one uses only keys explained below.
Pre-fill your Okta address so people do not type it, and pass the device serial number from your MDM's macro.
{
"domainName": "example.okta.com",
"OktaVerify.SerialNumber": "{{DeviceSerialNumber}}"
}Add the management hint so Okta can treat the device as managed, together with the org address.
{
"domainName": "example.okta.com",
"managementHint": "a-long-random-secret"
}Stop performance, diagnostic and crash-log collection on regulated devices. Okta warns this can limit support help.
{
"ReportApplicationPerformance": false,
"ReportDiagnostics": false,
"ReportCrashLogs": false
}Managed configuration
Key names and value types come from the vendor’s documentation. The explanations are written by Nomid.
| Key | Type | What it does | Example |
|---|---|---|---|
| Enrolment and device trust | |||
domainName | Org sign-in address | Pre-fills your Okta address when someone adds an account, so they do not type it. Needs Okta Verify 7.2.0 or later. | example.okta.com |
managementHint | Secret key | A secret key that tells Okta the device is managed, used for management attestation. It must match the Secret Key from your Okta device management setup. | a-long-random-secret |
OktaVerify.SerialNumber | Serial number placeholder | Enables collection of the device serial number on managed devices. Use the macro your MDM provider offers; if the MDM does not supply a value, Okta Verify reports an empty value. | {{DeviceSerialNumber}} |
| Diagnostics and feedback | |||
ReportApplicationPerformance | On or off | Controls whether the app collects performance reports. It is on by default; Okta says switching it off may limit its troubleshooting help. Needs Okta Verify 7.42.0 or later. | true |
ReportBugs | On or off | When off, the Send feedback menu is unavailable, so people cannot submit bug reports from the app. | true |
ReportCrashLogs | On or off | Decides whether console logs are included in crash reports. | true |
ReportDiagnostics | On or off | Controls recording of usage diagnostics such as non-fatal errors. | true |
ReportLocalFileLog | On or off | When on, people can save logs on the device and export them from the feedback menu. When off, logs are left out of feedback. | true |
Deploy with Nomid
Find it on Google Play from the policy’s apps list and choose how it is installed.
In the policy, set the app’s managed configuration with the keys and values from this page.
Devices in the policy receive Okta Verify and its configuration on their next sync.
Questions
com.okta.android.auth. Use it to find the app when you add it to a policy.
Yes. Okta states that the key-value pair is case-sensitive in its MDM integration article, so copy key names exactly.
It is a secret that tells Okta the device is managed by you. Keep it out of shared documents and rotate it if it leaks.
Okta documents what each key controls. For example, turning off ReportBugs hides the Send feedback menu, and turning off performance reports may limit Okta's troubleshooting help. Review each key before switching it off.
Add the app to a Nomid policy, set its configuration and choose its permissions.