A QR based cross device authentication attempt can still fail because the FIDO flow depends on local proximity between the mobile device and the WebAuthn client that generated the QR code. If proximity is missing, the request should time out and fail. Attackers may pass one factor, but that does not guarantee completion of the full authentication workflow.
Why a successful password check does not complete the whole QR-based flow
The password step and the QR-based cross-device step are related, but they are not the same event. Password authentication can establish one part of the login transaction, while the FIDO/WebAuthn handoff still needs the second device to be present, responsive and close enough to satisfy the local proximity check. If that handoff cannot be completed, the overall sign-in still fails.
That separation matters because many users assume the first success means the whole login should succeed. In practice, cross-device authentication is a chained workflow, so the browser, the phone and the authenticator exchange must all complete within the expected session window. A successful password only proves the first factor, not that the second device completed the approval path.
For a QR-based sign-in to finish, the originating client must keep the transaction alive long enough for the mobile device to respond. If the user scans the code too late, moves out of range, closes the browser, or switches contexts before approval, the request can expire even though the password was correct. That is normal failure behaviour, not a paradox.
Why proximity and timing are part of the security model
Cross-device FIDO flows use proximity as a practical anti-relay control. The QR code is not the credential by itself; it is the rendezvous point that allows the second device to prove local presence and bind the response to the originating session. The security value comes from completing the transaction on the intended nearby device, not from the QR image alone.
That design reduces remote abuse, but it also introduces a dependency on transport, device state and user interaction. If Bluetooth, browser support, mobile app state or platform attestation is unavailable, the flow may fail even though the password was accepted. For this reason, organizations should treat QR-based cross-device login as a multi-step control with a narrower success envelope than password-only sign-in.
Good implementations also enforce short-lived challenges and a timeout if proximity is not confirmed. That timeout is part of the control, because a long-lived QR login would be easier to relay, replay or leave open for opportunistic abuse. The result is that a legitimate user can still see a failed login when the second factor is delayed or when the client cannot confirm the expected nearby device relationship.
For a broader view of this pattern, the Cross-Device Flow Security Guide covers cross-device flow patterns, proximity verification and the controls that keep QR-based login from becoming a weak relay path.
What usually causes the failure in practice
The most common causes are simple operational ones: the phone is not nearby, the authenticator app is not ready, the user is on an unsupported browser or the session expired before the approval completed. Any of those can break the chain after the password has already succeeded. In other words, the password result is necessary but not sufficient for the full login.
Users may also see failure when they start the flow on one device and then interrupt it by refreshing the page, opening a new tab or letting the workstation lock. Those actions can invalidate the original challenge or sever the browser state needed to complete the WebAuthn ceremony. The login then fails cleanly rather than silently downgrading to a weaker path.
Organizations that support shared or frontline devices should account for this workflow friction explicitly. The Passwordless for Frontline and Shared Devices Guide explains why QR and other passwordless methods behave differently on shared tablets, kiosks and pooled PCs, where session state and device availability are less predictable.
Risk and Threat Considerations
QR-based cross-device login can fail for legitimate users, but the same design also helps resist relay attacks and remote prompt abuse. The security trade-off is that the flow depends on a live, local second-device interaction, so availability and usability are part of the control, not just convenience features.
Failure mechanism: The password authenticates the user to the first step, but the FIDO ceremony still needs a nearby device to complete the challenge before the session expires; if proximity, timing or client state is missing, the transaction fails.
Impact: Users experience intermittent sign-in failures, help desk calls and fallback pressure, and teams may be tempted to weaken the timeout or relax the proximity requirement, which would reduce the protection that makes the QR flow safer in the first place.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-63, NIST SP 800-53 Rev 5 and OWASP ASVS set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-63 | Digital Identity Guidelines | QR cross-device FIDO sign-in is governed by authentication assurance and phishing-resistant flow guidance. |
| Recommendation — Use NIST 800-63 to verify the cross-device flow meets the required authenticator assurance and phishing-resistant properties. | ||
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | The flow depends on authenticator lifecycle and challenge completion, not password success alone. |
| Recommendation — Apply IA-5 to manage authenticator lifecycle, timeout, and recovery behavior for the cross-device flow. | ||
| OWASP ASVS | V10 — OAuth and OIDC | The answer concerns authentication ceremony completion and redirect/session behavior across devices. |
| Recommendation — Test the end-to-end login ceremony so the second-device step cannot silently fail after initial credential success. | ||
Practitioner Guidance
What to verify: Confirm that the browser, mobile authenticator and platform all support the same cross-device FIDO path, and verify that the timeout is long enough for normal use but short enough to preserve the anti-relay benefit.
What good looks like: A valid user can complete the flow quickly from a nearby device, while delayed, distant or interrupted attempts fail consistently and visibly rather than degrading into an unclear partial success state.
Decision rule: If password success is followed by QR failure, treat it first as a ceremony completion problem, not as proof that authentication is “working but broken”; only then decide whether the issue is user proximity, session expiry, device compatibility or a policy constraint.
Practitioner takeaway: The key judgement is to preserve the security properties of the cross-device flow while making the failure mode understandable, because a QR login that is too forgiving becomes easier to abuse, and a QR login that is too strict becomes unusable.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org