Learn how to quickly add passkeys to your app using Authsignal’s pre-built UI.
Using passkeys within Authsignal's pre-built UI
mfa.authsignal.com
.
auth.example.com
then your Relying Party will default to example.com
.
Setting the Relying Party as your top-level domain is a good future-proof approach - it means that your users passkeys will be valid for Authsignal’s pre-built UI running on your custom domain (e.g. auth.example.com
) as well as on your top-level domain (e.g. example.com
) and any other subdomains.
https://
and a port if applicable e.g. :3000
.
For example, if your users can sign in with their passkey at https://auth.example.com
and reauthenticate on both https://example.com
and https://challenge.example.com
, then you would need to whitelist all three origins.
Configuring expected origins in the Authsignal Portal
Passkey uplift prompt