General
Q: Can I use Okta FastPass to sign in to my computer (macOS / Windows login screen)?
A: No. Okta FastPass only works for signing in to Okta-protected web apps — not for unlocking your device or operating system.
Q: Can I use Okta FastPass without Okta Verify?
A: No. Okta Verify must be installed and your Samsara account must be added to it before FastPass will work.
Q: Do I need the latest version of Okta Verify for FastPass to work?
A: Yes. Always keep Okta Verify up to date. On macOS, check Managed Software Center; on Windows, check Company Portal.
Q: How should I access apps to get the best passwordless login experience?
A: We recommend launching apps by clicking the app tile from your Okta dashboard rather than using a direct URL or bookmark. This ensures you go through the correct login flow and can take advantage of Okta FastPass.
Q: The Okta sign-in screen is on "Verifying your identity." How can I sign in with a different account or a different factor?
A: On the "Verifying your identity" screen, click the "Cancel and take me to sign in" link at the bottom of the prompt. This exits the Okta FastPass verification attempt and returns you to the standard Okta sign-in screen, where you can sign in with a different account or choose a different factor to verify.
Note: You need to click the "Cancel and take me to sign in" link quickly — click it before the native Touch ID / Okta Verify prompt appears, otherwise the link will disappear and you will have to restart the sign-in flow.
Clamshell users (laptop closed / docked to an external monitor) can use this temporarily to sign in with their other enrolled factors.
Q: I notice it is asking me for a password or an additional factor when accessing my applications. Why is that?
A: This is a known behavior when accessing the app via a direct URL or bookmark. For the best passwordless login experience, launch the app by clicking its tile from your Okta dashboard. This ensures you go through the correct login flow and can take advantage of Okta FastPass.
Q: Is Okta FastPass supported on Linux or Chromebooks?
A: No. FastPass (via Okta Verify) is only supported on macOS and Windows (including Windows 365 W365). Linux and ChromeOS (Chromebooks) are not supported.
Q: Does Okta FastPass work with a YubiKey?
A: No. Okta FastPass and YubiKey are separate authentication methods. Your YubiKey will continue to work as usual for apps that require it.
Q: I enrolled in Okta FastPass on my laptop — will I still need a password to sign in on my phone?
A: Yes. At Samsara, Okta FastPass is deployed as a desktop-only experience and does not extend to mobile devices. When signing in on your phone (iOS or Android), you will still be prompted for your Okta username and password, followed by a push notification or TOTP code via the Okta Verify mobile app. FastPass only replaces the password experience on enrolled Samsara-managed Mac, Windows, or VDI devices.
Q: What if I lose my device or it’s stolen?
A: Report it immediately via #help-biztech. Your other enrolled devices will keep working. Enroll your replacement device using the standard FastPass enrollment guide.
Q: Can I approve Okta Verify push notifications from my Apple Watch?
A: No. While your Apple Watch can still receive an Okta Verify push and let you tap "Yes," it cannot complete the biometric/user-verification step that FastPass now requires, so the approval will be rejected. Per Okta, Okta Verify on the Apple Watch does not support number challenges, user verification, or biometrics. You may also see a "turn on biometrics" prompt on the watch even when biometrics are already enabled in your settings. To sign in, approve the push on your phone (using Face ID / Touch ID) or use the local Okta Verify App on macOS. This is expected behavior, not a bug.
Biometric issues
Q: I'm getting an "Enable biometrics in Okta Verify" error when signing in. How do I fix it?
A: Okta FastPass requires biometrics to work, but biometrics are not yet enabled for your Samsara account in the Okta Verify app. Make sure your Okta Verify App is up to date, and biometrics are enabled for your account by following the steps below.
iPhone / iPad:
Open Okta Verify and tap your Samsara account.
Under Security, toggle on "Face ID or Passcode confirmation".
You will be prompted to verify your identity. Click Next.
Copy the code displayed on your screen, then click Continue to verification.
When prompted, select Enter a code — Okta Verify and paste the code.
Enter your password to complete setup.
Android:
Open Okta Verify and tap your account.
Under Security, toggle on Screen lock confirmation.
You will be prompted to verify your identity. Click Next.
Copy the code displayed on your screen, then click Continue to verification.
When prompted, select Enter a code — Okta Verify and paste the code.
Enter your password to complete setup.
Q: Does Okta or Samsara have access to my fingerprint or face data when I use FastPass?
A: No. FastPass uses your device’s built-in biometrics (Touch ID or Windows Hello) only to unlock your device locally. Your fingerprint or face data never leaves your device — it cannot be extracted, transmitted, or accessed by Okta, Samsara, or any app.
Q: I don't want to use biometrics (Face ID or fingerprint) for Okta Verify. Can I use a passcode instead?
A: Yes! You can fall back to using a passcode. To do this, you'll need to remove biometrics from your phone's Settings (not from within the Okta Verify app):
- Open your phone's Settings app
- Navigate to Face ID & Passcode (iOS) or Fingerprint / Biometrics (Android)
- Disable or remove the biometric option (Face ID or fingerprint)
- Once removed, Okta Verify will automatically prompt you for a passcode instead
Q: My Face ID (iOS)/Biometrics (Android) shows a green tick under Device Health in Okta Verify, but I'm still getting a biometric error when signing in. Why?
A: Device Health and the per-account biometric status are two different checks. A green tick under Device Health → Face ID Is Enabled only confirms that Face ID is set up on your device — it does not confirm that Okta Verify can use it for your account. If your biometrics or passcode settings have changed (or Face ID was enabled but never used to confirm an Okta Verify sign-in), you'll see a separate yellow exclamation mark (⚠️) next to your account on the Okta Verify home screen. Open that account and follow the steps in the FAQ below to clear the warning via the Troubleshooter — that will resolve the biometric error.
Q: I see a yellow exclamation mark (⚠️) next to my account in Okta Verify. What does it mean?
A: This usually means Okta Verify has detected a change in your device's biometrics or passcode settings — most commonly when Face ID / Touch ID is enabled on your device but hasn't been used yet to confirm an Okta Verify sign-in. To resolve, tap the account → tap Possible Issues → Tap on Face ID & Passcode Confirmation, tap Update, then complete the Verify Your Identity flow using your Okta credentials (as shown above). Once finished, the troubleshooter will show No Issues and the warning will clear.
Q: What happens if my device doesn’t support biometrics or PIN (Touch ID / Windows Hello)?
A: If your device doesn’t support biometrics or a PIN, you won’t be able to add an account to Okta Verify or use FastPass on that device. Reach out to #help-biztech for assistance.
Q: I’m on Android 12 and I can’t enable biometrics in Okta Verify. What should I do?
A: On Android 12, biometrics cannot be enabled when Okta Verify is installed in your work profile (a known Android Enterprise limitation). If you’re hitting this while using Bluetooth bootstrapping from another device, use the desktop enrollment flow instead — start the FastPass sign-in from your laptop and complete enrollment from there. See Okta’s Desktop Enrollment Flow page for more details.
macOS / Apple ID
Q: After enrolling in FastPass, why do I see a “This Mac can’t connect to iCloud” error or a Managed Apple ID sign-in prompt?
A: This is expected behavior, not a FastPass bug. When your Okta authenticators change during enrollment, Apple’s trust framework invalidates your existing Managed Apple ID session and requires re-authentication. The prompt may not appear right away — it often surfaces only when you open Apple Account settings or an iCloud-aware app.
To fix it, open System Settings → [your name] on macOS (or Settings → [your name] on iOS), sign in with your Samsara credentials, and complete the Okta flow.
Android-specific issues
Q: Battery Saver / Battery Optimization is interfering with FastPass on Android. How do I fix it?
A: Android’s battery optimization can stop Okta Verify in the background, breaking seamless flows (especially Bluetooth bootstrapping). Set Okta Verify’s battery usage to Optimized or Unrestricted — not Restricted.
Path: Settings → Apps → Okta Verify → Battery → Unrestricted
(Exact menu names may vary by device manufacturer.)
Q: FastPass or push notifications are failing intermittently on Android. What should I check?
A: Make sure Allow background activity is enabled for Okta Verify. Some Android devices disable this by default.
Path: Settings → Apps → Okta Verify → Battery → Allow background activity
Q: I’m trying to add Okta Verify using Bluetooth, but it’s failing and not moving past the code transfer step. How can I enroll into FastPass?
A: If Bluetooth-based enrollment is getting stuck after the code transfer step, use the desktop flow as an alternative to complete your FastPass enrollment.
Comments
0 comments
Please sign in to leave a comment.