Okta Device Access Setup Prompts Add an Account Repeatedly Following a Bluetooth Low Energy Transfer
Last Updated:
Overview
Okta Device Access registration repeatedly displays an Add an account prompt and fails to complete authentication after a Bluetooth Low Energy (BLE) account transfer. This occurs because the transfer imports the Okta Verify FastPass profile but does not populate the local macOS Platform Single Sign-On (SSO) user configuration binding. Resolve this by contacting Okta Support to enable the Device-Scoped Challenge Targeting Feature Flag.
The Okta Verify log displays the following errors:
{"TransactionPossessionChallenge": "Error: accountNotFoundForChallenge(OktaDeviceSDK.SignedNonceChallenge)"}
{"SSOExtensionCredentialBinding": "Failed to process request - Account not found"}
{"Handle SSO": "Account not found"}
{"Loopback HTTP Responder": "Loopback challenge handler failed with error: Device Authenticator error..."}
Applies To
- Okta Identity Engine (OIE)
- Okta Device Access
- Okta Verify for macOS
- macOS Desktop Password Sync
- Platform Single Sign-On (SSO)
- Bluetooth Low Energy (BLE) account transfer
Cause
The Add account from another device BLE transfer mechanism imports the Okta Verify FastPass profile into the Okta Verify application container but does not automatically populate the local macOS Platform SSO user configuration binding required by the Apple AppSSO framework. When Device Access prompts for FastPass authentication, Okta collects all valid FastPass candidate enrollments across all active devices into an unordered set and selects a key hint to send to the client. If Okta selects a key ID belonging to another device, Okta Verify on the new Mac searches the local macOS Keychain for that specific key ID and fails. Okta Verify then presents the inline Add an account prompt and interrupts registration.
Solution
Contact Okta Support to Enable the Device-Scoped Challenge Targeting Feature Flag
Okta has deployed a backend fix that implements device-scoped challenge targeting. With the fix in place, Okta explicitly filters FastPass candidate enrollments by the requesting device ID before generating the possession challenge. Okta will suppress foreign key hints from older devices, ensuring Okta Verify always receives a challenge targeting the local Mac keychain entry.
Administrators experiencing this issue should contact Okta Support to enable the feature flag.
