Make Version Number visible in Web UI

gmservice · August 5, 2024, 6:07pm

More often than not client issues are caused by an outdated installation. The version number should be visible in the UI.

BlackDex · August 5, 2024, 6:33pm

It is on the login screen.

gmservice · August 5, 2024, 6:45pm

Have you heard of this thing when you don’t see the forrest because of too many trees. You are right.

okoetter · August 12, 2024, 4:12pm

But it would be really nice if the server version (currently 1.32) would also be visible in the UI. It is shown in the admin interface’s diagnostics but usually I disable the admin interface for security reasons.

gmservice · August 12, 2024, 5:06pm

@BlackDex actually thinking about it a basic page containing the information for bug reports also in the webclient might really be useful.

BlackDex · August 15, 2024, 1:11pm

All bug report info can be generated via the Vaultwarden Admin.
We will not add a custom page with this info since that would take too much customization.

shadowjig · August 27, 2024, 12:33pm

While I can appreciate the effort is probably not worth the value of making this change. I will say the versioning is annoying. When I’m looking at releases on Github, they are listed as 1.32.0. But on the login page it’s 2024.6.1. It’s annoying to have to visit the release page on GitHub to translate between the two version numbering schemes.

Can you at least publish the 1.32.0 on the login page too? Or pick one version number you use when communicating changes?

shadowjig · August 27, 2024, 2:36pm

Ok, so I think I just realized that the 2024.6.1 is the web vault version and 1.32.0 is the server version. It would be helpful to see both on the login page if possible.

Is there an app diagram which can help me visualize all the parts of Vaultwarden and what’s in scope (what you maintain) vs out of scope (what’s Bitwarden or other external code/app)?

stefan0xC · August 28, 2024, 2:49am

Nope. I mean the problem is that “Vaultwarden” for you apparently means both the server and the shipped web-vault but to us it mainly refers to the server backend (“an unofficial rewrite of the Bitwarden® server”) while the “modified version of the Bitwarden® Web Vault” client is “Vaultwarden Web” (as stated on the login page).
btw: In earlier version of the web-vault, this distinction was not made and it used to only say “Vaultwarden” with the web-vault version, so to me the status quo is already a huge improvement in this regard.

github.com/dani-garcia/bw_web_builds

update to web-v2023.8.2 and rename to `Vaultwarden Web`

dani-garcia:master ← stefan0xC:rename-vaultwarden-web

opened 06:32PM - 15 Aug 23 UTC

stefan0xC

+518 -5

It seems that in the next release, the translation key `pageTitle` will be remov…ed (see https://github.com/bitwarden/clients/pull/5780) and replaced by a new one called `bitWebVault` where Bitwarden is hardcoded in the `messages.json` files. I would use that as opportunity to rectify the issue that @tessus has brought up in #131 by reverting the change and renaming the modified web-vault to `Vaultwarden Web` instead (omitting the last Vault as we already have that in Vaultwarden itself). If we want to credit Bitwardenı® Web Vault in the client itself (which arguably we don't have to), I think we could add another row to the footer, where we can have a better phrase without parentheses, e.g. > Vaultwarden is an unofficial rewrite of the Bitwarden® server. The Vaultwarden Web client is a modified version of the Bitwarden® Web Vault. > The Vaultwarden project is not associated with the Bitwarden® project nor Bitwarden Inc. ![vaultwarden-footer](https://github.com/dani-garcia/bw_web_builds/assets/509385/98e27264-4052-44f9-a9ed-f9cdf559ea12) Since we don't use this 404 page anymore, I think it would make sense to remove it from the patch file and just don't ship it in `apps/web/webpack.config.js`. And because I have been testing a different way of managing the changes (see #137), I would appreciate it, if we could run a linter and prettier before creating a patch, so it's easier to keep the changes in sync. I mean, those are mostly superficial changes but I think they don't really hurt either and we also require `cargo fmt` and `clippy` for Vaultwarden.

Regarding parts we don’t maintain: Our dependencies probably count as external code we don’t maintain. And regarding other parts of a functioning “Vaultwarden” setup (e.g. database backend, reverse proxy, etc.) this will depend on your system configuration.

The other Bitwarden clients are not maintained by the Vaultwarden project.

Currently the web-vault is build independently from the server and the web-vault version that is displayed is hard-coded in the client at build time, so it’s not really feasible.

To also display the server version, the client would either have to ask the server what the server version is (which the web-vault does not) or the server would have to modify the app/main.*.js file from the web-vault directory somehow (e.g. when returning the file or by a startup script).

Given that we try to keep the changes to the web-vault minimal (cf. bw_web_builds repository) either of these approaches would be a bit cumbersome to implement.

btw: The first approach would probably not be that helpful because we don’t return the actual server version in the /api/config anymore due to a client-side version check

github.com

dani-garcia/vaultwarden/blob/978f0092937c3a62f2de4ddc487137429754d3c0/src/api/core/mod.rs#L196-L201


      
          // Note: The clients use this version to handle backwards compatibility concerns
          // This means they expect a version that closely matches the Bitwarden server version
          // We should make sure that we keep this updated when we support the new server features
          // Version history:
          // - Individual cipher key encryption: 2023.9.1
          "version": "2024.2.0",

BlackDex · August 28, 2024, 9:49pm

I’m not sure what the problem is here.
Just go to /admin/diagnostics and you have all the info you request and more.

You can also run a cli command to get the Vaultwarden version.
vaultwarden --version and via docker it could look something like this docker exec -it vaultwarden /vaultwarden --version

Also, note that a lot of people who are security minded probably do not want any version printed anywhere which is public.

shadowjig · August 29, 2024, 9:13pm

@stefan0xC that’s helpful thank you. I’m familiar with app development, but I was having a hard time deciphering what you maintain and would consider changing per feature requests.

I agree the clients, and any docker dependencies (db, proxy, etc) shouldn’t be maintained by you.

So now I understand that the server is what you rewrote (using Rust) and I appreciate that. It’s clearly much faster than the official Bitwarden server. So that’s basically 100% your code.

But now I’m curious about the web vault. It sounds like you’ve basically cloned the official Bitwarden web vault and made some of your own customizations to it. Is that accurate? What are some high level functionality you’ve added to the web vault?

I recently started up the official Bitwarden stack using docker and it uses too many system resources (again thank you for re-writing it in Rust). One big thing I noticed is that the free license doesn’t allow me to create organizations. How did you get around this limitation? Allowing it on the server side I assume instead of making an adjustment in the web vault code?

Regards,
John

stefan0xC · August 29, 2024, 10:16pm

If you check the linked repository above you’ll see that the patches we apply when building the web-vault don’t really add much functionality but mainly remove certain parts (or hide them via CSS) that are not supported by Vaultwarden (like the billing and subscription modules, or login via SSO) and also we rebrand the web-vault due to trademark issues.

Personally, I’d recommend checking specifically the v2024.5.0.patch file as the current one for web-v2024.6.2 is a bit messy due to the backported commit 71e8fdb to fix #4628.

Vaultwarden does not have different plans or a subscription system, so there are no restrictions on how many organizations you can create on the server side. Since the web-vault would require a license key for self-hosted Bitwarden instances, we have adapted it to Vaultwarden by patching this behavior out (so there is no license key required and you also won’t be asked to select a plan).

Viking · October 11, 2024, 4:38pm

After reading this thread I am still confused.
My docker installation of Vaultwarden is using a container image version 1.32.1 but the logon page says Vaultwarden Web Version 2024.6.2
I’m sure both is correct, but how are these o be understood? I was expecting that the docker image version also would be possible to find somewhere in the GUI

BlackDex · October 11, 2024, 8:34pm

It is. In the admin interface /admin/diagnostics

stefan0xC · October 11, 2024, 8:53pm

“Vaultwarden Web” refers only to the patched web-vault (which is why it’s using the Bitwarden version scheme 2024.6.2, when technically it’s already the third iteration of the rebranded version). While the server backend (Vaultwarden) is on version 1.32.1.

Viking · October 25, 2024, 7:55pm

No such path
Where in the VW menu can diagnostics be found?

BlackDex · October 25, 2024, 8:08pm

What do you mean no such path?

You need to go to https://your.domain.tld/admin/diagnostics

Topic		Replies	Views
Should the version # on the website match the release # on github? Help	1	765	August 9, 2021
Bitwarden announcement regarding version Help	3	436	November 7, 2022
Image Release Tags Feature Requests	4	303	February 27, 2023
Option to Not publicly display the current version installed Feature Requests	0	416	February 23, 2024
How to update web-vault Help	8	2938	February 1, 2021

Make Version Number visible in Web UI

Related topics