search

Timshel / vaultwarden

Fork from dani-garcia/vaultwarden to add OpendID support.
GNU Affero General Public License v3.0
76 stars 12 forks source link

Extension not syncing - web vault working fine #30

Closed whallin closed 7 months ago

whallin commented 7 months ago

I'm currently testing the build 1.30.2-6 with authentik as the identity provider on a fresh install. I've got all SSO options configured successfully via the environmental variables and the /admin endpoint (for the sake of testing).

Authentication works as expected. I can sign up and sign in using my authentik instance—no questions asked. However, the web vault is the only thing that is actually in sync.

Any changes made via the web vault do not show up when signed in to the browser extension (at least on Chromium-based browsers). However, if the change is made via the browser extension, the changes do show up in the web vault. Once present in the web vault, any changes there will sync to the browser extension.

Trying to "Sync vault now" via the browser extension settings ends up in an infinite loading with no console output with LOG_LEVEL set to DEBUG.

I've gone ahead and attached the debug logs from when I authenticated through the browser extension.

vaultwarden-console-browser-ext-auth-logs.txt

EDIT 1: Clarification on "change"; let's say I create an item via the browser extension. That shows in the web vault, and can also be deleted from there. The deletion will sync over to the browser extension—no problem. The other way around, however, does not work for me.

EDIT 2: Felt the need to try it out on the official Bitwarden app for iOS. The issue is not present there, works just as expected. No troubles with authentication via SSO either.

Timshel commented 7 months ago

Hey, Had a similar bug (in the web) when I made a change which resulted in returning no refresh_token but should never happen now. Will try to reproduce.

whallin commented 7 months ago

@Timshel I've gone ahead and attached my Docker stack for troubleshooting. The SSO settings are currently set via the /admin endpoint.

docker-compose.dev.yml.txt

whallin commented 7 months ago

Update: I wiped the data and recreated the Vaultwarden instance. It seems to work now. However, I'll try to continue reproducing as I'm quite clueless.

whallin commented 7 months ago

I've sadly yet been able to recreate the issue. I'm gonna go ahead and close this. If someone experiences something similar, feel free to reopen this.