Part of the Passkeys project. Parent: #36. Depends on the authentication ceremony.
Scope
Surface passkey sign-in on the login page alongside email and password.
Requirements
Feature-detect WebAuthn and hide or disable the passkey option where it is unavailable, rather than offering a button that fails. Password login stays the fallback in every case.
A cancelled or failed passkey prompt must return the customer to a usable password form, not a dead end.
The error surface has to stay quiet about whether an account exists — same rule as the authentication ceremony.
Verification note
This is the one issue in the project that cannot be fully proven in QA. Credentials are bound to the Relying Party ID, so a passkey registered against the QA hostname will not work in production. QA verifies the flow, the fallbacks, and the copy; production needs its own smoke test with a real registration afterwards.
Part of the Passkeys project. Parent: #36. Depends on the authentication ceremony.
## Scope
Surface passkey sign-in on the login page alongside email and password.
## Requirements
- Feature-detect WebAuthn and hide or disable the passkey option where it is unavailable, rather than offering a button that fails. Password login stays the fallback in every case.
- A cancelled or failed passkey prompt must return the customer to a usable password form, not a dead end.
- The error surface has to stay quiet about whether an account exists — same rule as the authentication ceremony.
## Verification note
This is the one issue in the project that cannot be fully proven in QA. Credentials are bound to the Relying Party ID, so a passkey registered against the QA hostname will not work in production. QA verifies the flow, the fallbacks, and the copy; production needs its own smoke test with a real registration afterwards.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Part of the Passkeys project. Parent: #36. Depends on the authentication ceremony.
Scope
Surface passkey sign-in on the login page alongside email and password.
Requirements
Verification note
This is the one issue in the project that cannot be fully proven in QA. Credentials are bound to the Relying Party ID, so a passkey registered against the QA hostname will not work in production. QA verifies the flow, the fallbacks, and the copy; production needs its own smoke test with a real registration afterwards.