Not prompting to create passkey? #447

New issue

Open

opened 2026-05-27 01:25:30 -05:00 by spin-drift · 4 comments

spin-drift commented

2026-05-27 01:25:30 -05:00

(Migrated from github.com)

Despite having a device which definitely supports passkeys (iPhone 17 Pro), after logging in to a test account with a password I was not prompted to create a passkey, as shown in the docs:

However, I do already have passkeys from other accounts in my phone.

Is this question supposed to show up under different circumstances than I assumed, or does it somehow fail to show unless I have zero passkeys saved?

Despite having a device which definitely supports passkeys (iPhone 17 Pro), after logging in to a test account with a password I was not prompted to create a passkey, as shown in the docs: <img src="https://voidauth.app/public/screenshots/passkey_dialog.png" height="240px"/> However, I _do_ already have passkeys from other accounts in my phone. Is this question supposed to show up under different circumstances than I assumed, or does it somehow fail to show unless I have _zero_ passkeys saved?

spin-drift commented

2026-05-27 12:42:48 -05:00

(Migrated from github.com)

Ah, I see now:
github.com/voidauth/voidauth@588300f1f0/frontend/src/app/services/passkey.service.ts (L163-L169)

I guess my suggestion would be for non-privileged users to also get prompted for passkeys on account creation, as just a standard feature.

This is based on my understanding of a typical user flow:

Signs up
Can choose password or passkey
If they choose passkey, they can only login on devices linked to that passkey system
Therefore, they should probably create a password first
If they create a password first, they'll need to log in again on passkey devices to create a passkey

By prompting them to create a passkey (on supported devices) right after they create an account with a password, for golden-path cases where their device supports passkeys, they get all future use cases handled immediately.

Ah, I see now: https://github.com/voidauth/voidauth/blob/588300f1f05f07e0a43f22c33bca5cd5e0724aa8/frontend/src/app/services/passkey.service.ts#L163-L169 I guess my suggestion would be for non-privileged users to also get prompted for passkeys on account creation, as just a standard feature. This is based on my understanding of a typical user flow: - Signs up - Can choose password or passkey - If they choose passkey, they can only login on devices linked to that passkey system - Therefore, they should probably create a password first - If they create a password first, they'll need to log in again on passkey devices to create a passkey By prompting them to create a passkey (on supported devices) right after they create an account with a password, for golden-path cases where their device supports passkeys, they get all future use cases handled immediately.

notquitenothing commented

2026-05-30 16:12:30 -05:00

(Migrated from github.com)

In this case user.isPrivileged indicates that the session of the signed in user has the ability to perform sensitive actions like changing profile settings and setting a passkey. Thank you for opening a PR related to this issue, I will take a look at it when I get the chance

In this case `user.isPrivileged` indicates that the _session_ of the signed in user has the ability to perform sensitive actions like changing profile settings and setting a passkey. Thank you for opening a PR related to this issue, I will take a look at it when I get the chance

spin-drift commented

2026-05-30 16:24:15 -05:00

(Migrated from github.com)

In this case user.isPrivileged indicates that the session of the signed in user has the ability to perform sensitive actions like changing profile settings and setting a passkey. Thank you for opening a PR related to this issue, I will take a look at it when I get the chance

Ah, my bad, thanks! I'll put that check back in the PR.

> In this case `user.isPrivileged` indicates that the _session_ of the signed in user has the ability to perform sensitive actions like changing profile settings and setting a passkey. Thank you for opening a PR related to this issue, I will take a look at it when I get the chance Ah, my bad, thanks! I'll put that check back in the PR.

spin-drift commented

2026-06-01 12:21:50 -05:00

(Migrated from github.com)

Done! Strange, though, that the check didn't seem to fire initially (hence this issue).