Unable to fetch ServerConfig: Failed to decode access token: JWT must have 3 parts

[fritzfranzke]

Subject of the issue

Bitwarden client on Linux fails to load password (infinite spinner) with the error Unable to fetch ServerConfig: Failed to decode access token: JWT must have 3 parts shown in the logs. Server logs show no errors. iOS client as well as Webvault works without issues. If this is solely Bitwarden client related feel free to close.

Deployment environment

• vaultwarden version: 1.30.5

• Install method: Docker Compose

• Clients used: Official Bitwarden Linux Client Version 2024.4.0

• Reverse proxy and version: Caddy v2.7.6

• Other relevant details:

Steps to reproduce

Deploy vaultwarden and official Bitwarden Linux client and try to log in.

Expected behaviour

Login loads passwords

Actual behaviour

Infinite spinner is shown in UI

[denysvitali]

I had a similar issue (while logged in).

My workaround was to logout and then log back in, after that, syncing works again and "Failed to decode access token: JWT must have 3 parts" doesn't appear anymore.

[farzadha2]

yeah currently having the same issue

[farzadha2]

just reversed to version 2024.3.0 and it worked

[foozzi]

The same problem on Archlinux

[chrpinedo]

same problem here with ArchLinux

[rhoot]

I had this problem on Arch, and the issues linked below helped explain why: They made the Bitwarden client store tokens in whatever wallet you have. In my case, I had kwallet installed... but I wasn't using it, and my login manager was not configured to open it when I log in. So Bitwarden tried to use it but couldn't.

Fixing that still didn't seem to solve it, but deleting the Bitwarden config afterward did.

So my full fix was:

1. Configure kwallet to unlock on login
2. Log out, and back in of my DE
3. rm -rf ~/.config/Bitwarden
4. Launch and authenticate in Bitwarden again

A bit annoying that it requires using a secrets manager now, but it sounds like they're working on a fix to fall back to the old file-based behavior when one isn't available. And it probably also works with other secret managers, kwallet just happened to be what I picked.

Edit: The above is also why that snap command works for people using the snap; it gives the snap access to the secrets manager.

[BlackDex]

Seems a client issue

• Error when syncing the vault on Linux desktop bitwarden/clients#8651
• Error: Failed to decode access token: JWT must have 3 parts in 2024.3.2 Desktop release bitwarden/clients#8662
• Unable to login.  bitwarden/clients#8823
• Failed to decode access token: JWT must have 3 parts bitwarden/clients#8841

Amongst others.