What to check first
Check which verification methods Okta allows for the pilot admin group and keep a separate admin who can restore policy access.
KeySigner setups
- Test an Okta Identity Engine authenticator code →KeySigner on iPhone or Mac with Sign-in codes
KeySigner setup requirements →
Provider availability
Authenticator app codes in Okta Identity Engine. The enrollment policy for the test user must allow the Google Authenticator method. Check provider requirements →
Provider walkthroughs
- Pilot an Okta access policy without locking out adminsRun the same test with a pilot user and a backup administrator so you know what your policy covers and how you can roll it back.
- Rehearse account recovery with 1Password and OktaCheck that your team can regain 1Password vault access when someone loses a device or access to Okta is interrupted.
- Test Cloudflare dashboard access with OktaCheck the complete access and rollback path on a dedicated test domain before requiring Okta for Cloudflare dashboard access.
- Check authenticator app policiesSee where to check whether Okta, Microsoft Entra ID, Google Workspace, or JumpCloud allows time-based authenticator codes for a test account.
What it covers
The policy for an employee's app can differ from the policy for the Okta admin console.
Troubleshooting
Does the pilot user have a passkey while the admin console still asks for another factor?
Compare the effective rule for the admin console with the rule used by the pilot app. Use the same pilot user for both checks.
Check Okta status for reports on the Okta cell that serves your organization.
Documentation and support
Okta documentation
Review passkey access controls
Review verification rules for the Okta Admin Console
Check Google Authenticator enrollment