
Configuring passkeys
In the Authsignal Portal we have configuredlocalhost as the Relying Party for the purposes of local development.
We also whitelist both the login server and the application server as expected origins.

https://localhost:5002, then reauthenticate with the same passkey when signing in to IdentityServer running on https://localhost:5001.
Enrolling a passkey
Once the user has logged in with MFA, we can use the Authsignal Web SDK to allow the user to add a passkey. This can be done by adding a button to the application server (i.e. the WebClient).
enrollmentToken here is fetched server-side in /src/WebClient/Pages/Passkeys.cshtml.cs when the page loads.
Signing in with a passkey
Now that the user has enrolled a passkey, there are two ways to offer passkey sign-in on the IdentityServer login page.Passkey autofill
Passkey autofill is an unobtrusive approach where the user’s available passkeys are suggested automatically when they focus the username field. First we need to ensure that the input field has the valueusername webauthn in the autocomplete attribute.

Sign-in button
A dedicated sign-in button launches the passkey prompt immediately when clicked, making passkeys a clearly visible option on your login page. Add a button to your IdentityServer login page:signIn() without the autofill flag:

