make webauthn more optional #422

New Issue

MrUnknownDE · 2026-04-05T21:13:19+02:00

MrUnknownDE commented

2026-04-05 21:13:19 +02:00

Originally created by @stefan0xC on 8/9/2025

I don't think that we need initialize webauthn on startup (which currently fails if you set DOMAIN to an IP address because webauthn requires a domain name as rp_id). I've also hidden it as an option if you have setup the domain to be an IP address.

This won't touch on the other issues that were reported but I do think that it's important that Vaultwarden can start with something like DOMAIN=http://127.0.0.1:8000.

*Originally created by @stefan0xC on 8/9/2025* I don't think that we need initialize webauthn on startup (which currently fails if you set `DOMAIN` to an IP address because [webauthn requires a domain name as `rp_id`](https://www.w3.org/TR/webauthn-2/#relying-party-identifier)). I've also hidden it as an option if you have setup the [domain](https://docs.rs/url/2.5.4/url/struct.Url.html#method.domain) to be an IP address. This won't touch on the other issues that were reported but I do think that it's important that Vaultwarden can start with something like `DOMAIN=http://127.0.0.1:8000`.

MrUnknownDE closed this issue

2026-04-05 21:13:19 +02:00

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#422