starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-03-01 11:19:52 +03:00
Code Issues 32 Packages Projects Releases 12 Wiki Activity

Fido2 Webauthn broken on latest version of Android app (2.13.0) #1115

New Issue
Closed
opened 2026-02-04 23:56:52 +03:00 by OVERLORD · 3 comments
OVERLORD commented 2026-02-04 23:56:52 +03:00
Owner
Copy Link

Originally created by @krzmaz on GitHub (Sep 26, 2021).

Subject of the issue

It seems that with the recent version of the mobile app some changes were introduced to FIDO2 Webauthn authentication - https://github.com/bitwarden/mobile/pull/1519
After updating, there is a 404 error when trying to authenticate, as the app is trying to connect to an unimplemented endpoint, example below:
https://vault.mydomain.com/webauthn-mobile-connector.html?data=[DATA]=&parent=bitwarden%3A%2F%2Fwebauthn-callback&v=2

Deployment environment

  • vaultwarden version: 1.22.2

  • Install method: docker image

  • Clients used: Android

  • Reverse proxy and version:

  • MySQL/MariaDB or PostgreSQL version:

  • Other relevant details:

Steps to reproduce

Try to authenticate with Fido2 Webauthn using the latest (2.13.0) mobile app

Expected behaviour

Authentication is possible

Actual behaviour

Error 404 happens

Troubleshooting data

Originally created by @krzmaz on GitHub (Sep 26, 2021). <!-- # ### NOTE: Please update to the latest version of vaultwarden before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * https://github.com/dani-garcia/vaultwarden/issues/1180 * https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue <!-- Describe your issue here. --> It seems that with the recent version of the mobile app some changes were introduced to FIDO2 Webauthn authentication - https://github.com/bitwarden/mobile/pull/1519 After updating, there is a 404 error when trying to authenticate, as the app is trying to connect to an unimplemented endpoint, example below: https://vault.mydomain.com/webauthn-mobile-connector.html?data=[DATA]=&parent=bitwarden%3A%2F%2Fwebauthn-callback&v=2 ### Deployment environment <!-- ========================================================================================= Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab. That will auto-generate most of the info requested in this section. ========================================================================================= --> <!-- The version number, obtained from the logs (at startup) or the admin diagnostics page --> <!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden --> <!-- Remember to check if your issue exists on the latest version first! --> * vaultwarden version: 1.22.2 <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: docker image * Clients used: <!-- web vault, desktop, Android, iOS, etc. (if applicable) --> Android * Reverse proxy and version: <!-- if applicable --> * MySQL/MariaDB or PostgreSQL version: <!-- if applicable --> * Other relevant details: ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start vaultwarden? --> Try to authenticate with Fido2 Webauthn using the latest (2.13.0) mobile app ### Expected behaviour <!-- Tell us what you expected to happen --> Authentication is possible ### Actual behaviour <!-- Tell us what actually happened --> Error 404 happens ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data -->
OVERLORD commented 2026-02-04 23:57:06 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Sep 26, 2021):

I think it should work fine. Are you using a reverse proxy, and if so which one? Does it has caching functionally? Did you clear the cache if so?

@BlackDex commented on GitHub (Sep 26, 2021): I think it should work fine. Are you using a reverse proxy, and if so which one? Does it has caching functionally? Did you clear the cache if so?
OVERLORD commented 2026-02-04 23:57:15 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Sep 26, 2021):

Sorry, i just saw that this specific endpoint is available within the current testing image, and thus already fixed. But not in the current latest version

Either use the testing image or wait for a new release.

@BlackDex commented on GitHub (Sep 26, 2021): Sorry, i just saw that this specific endpoint is available within the current testing image, and thus already fixed. But not in the current latest version Either use the testing image or wait for a new release.
OVERLORD commented 2026-02-04 23:57:19 +03:00
Author
Owner
Copy Link

@krzmaz commented on GitHub (Sep 26, 2021):

Thank you for the quick response!
The latest testing docker image is panicking and not starting on my Raspberry Pi 4, so I guess I'll wait for a release :)
Thank you for all the work on this project!

@krzmaz commented on GitHub (Sep 26, 2021): Thank you for the quick response! The latest testing docker image is panicking and not starting on my Raspberry Pi 4, so I guess I'll wait for a release :) Thank you for all the work on this project!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
troubleshooting
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#1115
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?