Enterprise Passkey Whitepaper. Practical guidance, rollout patterns and KPIs for passkey programs.
allowCredentials list in the server response
is the enumeration signal: it shows that an account exists and has a passkey, and its
shape can hint at the authenticator type.Sooner or later, many passkey projects at banks, retailers, public services and platforms with a strict security team hit the same wall. The product team wants the passkey dialog to open as soon as the user types their username, because that gives the highest passkey usage. The security team has a long-standing rule against account enumeration: an unauthenticated visitor must never learn whether an account exists. A username-first passkey login breaks that rule in a new way, because the step after the username now looks different for users with a passkey.
Without numbers, the discussion stalls. Security says "no signal", product says "no adoption without the automatic prompt", and nobody can say what each side gives up. This guide provides the material for a decision:
OWASP's Authentication Cheat Sheet sets the goal: login, recovery and registration should respond in a generic way, with the same message, the same HTTP status and the same processing time, whether the account exists or not. With passwords, the login step met that goal easily, because the password form looked the same for everyone. Passkeys add a step that depends on the account.
Login pages have always risked leaking that an account exists, that it is locked or where one-time codes are sent ("Code sent to j•••@gmail.com"). Most security teams already have a position on these. A username-first passkey login adds two facts that need a fresh decision:
In a username-first flow, the browser sends the username, the server looks up the account and returns WebAuthn request options. For an account with a passkey, those options contain the allowCredentials list, so the operating system shows only this account's passkey:
{ "challenge": "9fQ…", "rpId": "example.com", "allowCredentials": [ { "type": "public-key", "id": "Kx3q…9A", "transports": ["internal", "hybrid"] } ] }
For an account without a passkey or an unknown username, the server returns no options and the browser moves on to the password screen. An outsider who repeats the first request with a list of usernames can sort them into "has a passkey" and "does not". The W3C describes this in WebAuthn Level 3, section 14.6.2 Username Enumeration.
Section 14.6.3 Privacy leak via credential IDs
adds a second point: the length of a credential ID "might be a hint as to what type of
authenticator created it", and the number and lengths of IDs might work as a correlation
handle across sites. Combined with the transports values, this can help a phishing message
sound credible. The same section names the cleanest prevention: use discoverable
credentials, so the allowCredentials list is not needed at all.
The passkey itself cannot be phished. Knowing that an account has a passkey gives an attacker nothing against the passkey. The signal matters because of what surrounds it:
Many security teams therefore reject a visible signal during the phase when most users still log in with a password. Their concern is the fallback that follows the signal.
Get free passkey whitepaper for enterprises.
A passkey login starts either with the username or with the passkey. In practice, login pages combine several entry points, and each one has its own enumeration profile.
| Entry point | Who sees it | Reveals account state? | Main limitation |
|---|---|---|---|
| Typed username, then automatic passkey prompt | Everyone | Yes, through allowCredentials | Prompt on a new device ends in a QR code |
Typed username, empty allowCredentials | Everyone | No | Dialog lists every passkey for the site or a QR code |
| Passkey autofill (conditional UI) | Users with a passkey on this device | No | Password autofill competes in the same field |
| Generic passkey button | Everyone | No | Only around 10-25% of passkey holders press it |
| One-tap passkey button | Browsers with an earlier passkey login | No (only to that browser) | Gone after cookies are cleared or on a new browser |
Three observations matter for the decision:
allowCredentials list and the browser shows matching passkeys locally.
Some security teams still object to any page that lists passkeys before the user has
typed an identifier, mainly on shared devices. Clarify that position early, because it
decides whether conditional UI is
available to you at all.For the username-first prompt, the start rule matters too. Prompting every account with a passkey sends users on a new laptop into a QR code they do not expect. Good start rules only prompt where the passkey is likely available on this device, for example based on a cookie from an earlier passkey use or passkey intelligence.
Security teams can name the risk. Product teams need a number for the cost. The ranges below come from Corbado's aggregate observations across passkey rollouts and describe logins by users who already have a passkey. Your values depend on platform mix, audience and login frequency, so treat them as a starting hypothesis to validate.
Compared against a username-first login with a one-tap passkey button:
The press rate needs context. It is measured among users who already have a passkey. The passkey login rate across all logins, which earlier Corbado material puts at around 5% for button-only designs, is much lower because most users have no passkey yet. Both numbers point the same way: a button alone does not change login habits.
Two conclusions follow:
The share of all logins that use a passkey is the product of four factors: device support, availability of the passkey at login, enrollment and usage. The following illustrative comparison keeps the first three factors identical and changes only usage.
The values are illustrative. The pattern holds generally: an enumeration-safe design leaves enrollment untouched and can lower the passkey login rate by up to a factor of almost two, depending on how well the returning-browser shortcut works. Adoption forecasts built on username-first usage need to be recalculated whenever an enumeration-safe design is on the table.
A one-tap passkey button is enumeration-safe because it never reacts to a username the visitor types. After a successful passkey creation or login, the server sets a first-party cookie that records prior passkey use in this browser. On the next visit, the page offers a one-tap button for that account. A visitor without the cookie sees the normal page. For the shared-device side of remembered identifiers, see Remember Me & Passkeys.
How much one-tap recovers depends on how many users return while the cookie still exists:
document.cookie at seven days. Set the marker in
an HTTP response as Secure and HttpOnly, served from your own infrastructure and not
from a vendor subdomain behind a CNAME, where Safari can apply similar caps.signalUnknownCredential from the WebAuthn Signal API, which
the spec recommends over signalAllAcceptedCredentials toward unauthenticated callers.To estimate coverage, combine two distributions: the time between logins per user from your login logs and the practical cookie survival per browser and operating system. A service whose users log in weekly keeps most of the one-tap benefit. A service whose users log in twice a year loses a large part of it, and its usernameless gap moves toward the "without one-tap" case.

Authentication Analytics Whitepaper. Practical guidance, rollout patterns and KPIs for passkey programs.
An organization that accepts the username-first signal for higher passkey usage should manage it actively. The controls fall into three groups.
Make responses indistinguishable where possible:
Make harvesting slow and visible:
Protect what an attacker would do next:
The first two groups make enumeration slower and more expensive. They do not remove the disclosure. A patient attacker who tests a few hundred targeted usernames from distributed residential IPs stays below most rate limits, so existing bot and fraud tooling should be tested against targeted, automated and distributed enumeration attempts before anyone relies on it.
The third group has the most effect. The signal only helps an attacker who can follow it with a phishable step, so hardening the fallback protects the path an attacker would actually use.
WebAuthn Level 3 offers a middle path in section 14.6.2: for an unknown username, continue the ceremony with "plausible imaginary values". If every username, known or not, receives passkey request options, the response no longer tells accounts apart.
Decoys only work if they are indistinguishable from real responses:
Decoys also have hard limits:
Decoys fit teams that must keep a username-first page and can carry the engineering cost. For most, the usernameless route is easier to defend.

Passkey consulting - rollout materials, ROI tools & expert guidance. Used by PwC and EY.
For organizations with a strict enumeration rule, a usernameless login with a one-tap passkey button gives up the least passkey usage. It combines three entry points on the first login screen:
Design rules that keep it enumeration-safe:
residentKey: required work
in both login models, so the model can change later. Switching from usernameless to
username-first then changes how passkeys are used, while existing passkeys keep working.
See discoverable credentials
for the details.Users without a passkey on the device who press the generic button see a QR code or a "no passkeys available" message from the operating system. Label the button clearly ("Sign in with a passkey") and route a cancel or error back to the password field without a dead end.
Going usernameless also moves fraud holds, lock status and per-account risk checks from the identifier step to after the verified assertion. Usernameless Passkey Login: Fraud & Lock Checks shows where each control moves.
The enumeration signal and the cost of going usernameless both depend on how many users still have a phishable fallback. The following overview shows how both change from launch to a passkey mandate.
Two consequences matter for the decision:
Splitting the question into separate decisions helps both teams:
Igor Gjorgjioski
Senior Product Lead, VicRoads
We hit 80% mobile passkey activation across 5M+ users without replacing our IDP.
See how VicRoads scaled passkeys to 5M+ users, alongside their existing IDP.
Read the case studyCorbado helps enterprises base this decision on measured data. Corbado Connect adds passkeys on top of an existing identity provider, including conditional UI, a one-tap passkey button and passkey intelligence for start rules in either login model. Corbado Observe instruments the login page from the client side, so teams can see how often users press the passkey button, select autofill or use one-tap, and how the passkey login rate develops by operating system and browser after a change of login model.
See Method Uplift in Corbado Observe →Subscribe to our Passkeys Substack for the latest news.
Account enumeration in passkey login is a trade-off you can quantify. A username-first
flow reveals through the allowCredentials list which accounts exist and have a passkey.
Mitigations make that signal more expensive to harvest and leave it in place. Decoys can
hide it at a permanent consistency cost. A usernameless login avoids it, at a price in
passkey usage that depends mostly on whether a returning-browser shortcut such as a one-tap
passkey button is available.
For organizations with a strict enumeration rule, launching usernameless with one-tap is usually the most defensible starting point. Recalculate the forecast, measure from the client side and review the decision as the phishable fallbacks disappear.
Yes, if the server only returns WebAuthn request options with a populated
allowCredentials list for accounts that have a passkey. An outsider can submit any
username and read whether the response contains credential IDs. That reveals that the
account exists and has a passkey, and the number and length of the IDs can hint at the type
of authenticator.
From the server's perspective, yes. Conditional UI starts a WebAuthn request with an empty
allowCredentials list, so the server response is identical for every visitor. The browser
shows matching passkeys locally and the server learns nothing until the user selects a
passkey and completes user verification.
It depends mostly on whether a returning-browser shortcut such as a one-tap passkey button is available. With one-tap, usernameless login typically trails a username-first login with one-tap by around 10-20% of passkey logins. Without it, usernameless relies on passkey autofill and a generic button that only around 10-25% of passkey holders press, and the gap can reach half of the passkey logins.
W3C WebAuthn Level 3 suggests returning plausible imaginary values for unknown usernames, derived deterministically from the username. This hides account existence if the decoys match real responses in count, ID length, transports, timing and error behavior on every endpoint. Decoys do not hide the real credential IDs of real users and they show a passkey dialog to users without a passkey.
Related Articles
Table of Contents