Okta Verify

Where Okta Verify keeps its logs

Okta Verify logs to %WINDIR%\System32\config\systemprofile\AppData\Local\Okta Device Access\Logs\ on Windows. 1 other Windows log location is recorded below.

Okta Verify logs to ~/Library/Group Containers/B7F62B65BN.group.okta.macverify.shared/Logs/ on macOS.

Paths are printed exactly as Okta Verify writes them. Environment variables like %LOCALAPPDATA% and $XDG_STATE_HOME are never expanded, so a path can be pasted straight into a shell. Where a path differs between installer types or shipping flavours, each one is racked as its own card below - why that happens.

Finding your way around Windows and macOS.

How to turn on debug logging for Okta Verify

1. Windows: Set the managed app setting LogLevel to Debug (the default is Warning).
2. macOS: For Platform SSO, turn on debug logging with sudo log config --mode "level:debug,persist:debug" --subsystem com.apple.AppSSO.
3. macOS: Reset it afterwards with sudo log config --subsystem com.apple.AppSSO --reset.

How to collect Okta Verify logs

1. Windows: Right-click the Okta Verify icon in the notification area and choose Send feedback or Report Issue; the logs attach automatically.
2. If the option is missing, your organization has turned off sharing diagnostics with Okta.
3. macOS: Click Okta Verify in the menu bar and choose Send feedback to Okta or Report Issue.
4. macOS: Save recent Platform SSO activity with log show --last 5m | grep -i AppSSOAgent > AppSSOAgent.txt.
5. macOS: Run sudo sysdiagnose -f ~/Desktop for a full system diagnostic.
6. macOS: For Desktop MFA, run sudo log collect --start "<YYYY-MM-DD HH:MM:SS>" --output /tmp, then tar the .logarchive it writes.