Okta Issues

Okta does not open at all

“Something Went Wrong. Please Try again Later”

- https://support.okta.com/help/s/article/enrollment-issue-for-okta-verify-something-went-wrong-please-try-again-later?language=en_US

Okta Fastpass

- Okta Verify with managed and not managed - Not have okta setup until they are approved on setting up the Intune Company Portal then only have the managed work profile Okta Setup. User has two Okta Verify

Device Known issues

- https://help.okta.com/oie/en-us/content/topics/identity-engine/devices/known-issues.htm

Okta Verify won’t open

- https://support.okta.com/help/s/article/users-cannot-open-okta-verify-for-a-shared-device-in-windows?language=en_US
- Solution:

#Stop Okta Verify for ALL users
Stop-Process \-Name "OktaVerify" \-Force \-ErrorAction SilentlyContinue

#Remove the database file from the current context
remove-item "$env:localappdata\\Okta\\OktaVerify\\datastore.db" \-verbose \-Force \-ErrorAction SilentlyContinue

Part 2

The following PowerShell script removes the Okta Verify database from the Default user profile. To execute, it needs to run in the System or Admin context.

#Remove the database file from the Default user folder remove-item "C:\Users\Default\AppData\Local\Okta\OktaVerify\datastore.db" -verbose -Force -ErrorAction SilentlyContinue

Option 2: Target all users on a device

If there is only 1 user on the device or if there are multiple affected users, you can use this simplified script to stop Okta Verify and remove the database file from all user profiles.

Do not execute this script if there are any users with working FastPass enrollments on the device. Do not push this script to all devices. Doing so will cause previously unaffected users to lose their FastPass enrollments.

#Stop Okta Verify for ALL users Stop-Process -Name "OktaVerify" -Force -ErrorAction SilentlyContinue #Remove the database file for ALL users on the machine remove-item "C:\Users\*\AppData\Local\Okta\OktaVerify\datastore.db" -verbose -Force -ErrorAction SilentlyContinue