Feature:
Allow to land on the Universal Login page where a passkey can be selected when using the login_hint parameter.
Description:
We use Auth0 to authenticate some users, while other users have to keep using our old authentication system. For this we have a custom sign in page where a user enter his email address; if this user is supposed to authenticate with our Auth0 tentant we’re using the /authorize endpoint to redirect the user to Universal Login.
I’m using the /authorize endpoint’s login_hint query string parameter so the user doesn’t have to enter his email address again.
The page that loads looks like this:
Some of our users will use a passkey to authenticate. Now, if they want to select a passkey, they have to click the Edit button in the email address field (Bewerken in the screenshot above):
We want a way to land immediately on this last screen.
Use-case:
Improve UX for people who want to use a passkey to authenticate.
See also
Is there any way to know if this feature is being actively considered and/or on a roadmap for delivery?
+1 from us this would be a meaningful improvement for our setup as well.
We’re building passkeys into our primary sign-up and authentication flow, and the goal is for passkeys to be the default experience rather than a fallback. The blocker today is exactly what’s described here: when we pass login_hint to /authorize, the user always lands on the password prompt and has to click “Edit” before they can select a passkey. That extra step undercuts the whole value proposition of passkeys, since the main reason we’re adopting them is to give users a smoother, password-free experience.
Being able to land directly on the passkey selection screen (while still keeping the email prefilled via login_hint) would let us make passkeys feel like a first-class flow instead of something hidden behind an edit action.
Is there any update on whether this is on the roadmap?
