Merge changes from #131 and #133.
Co-authored-by: Stefan Melmuk <stefan.melmuk@gmail.com>
Co-authored-by: GeekCornerGH <45696571+GeekCornerGH@users.noreply.github.com>
- Updated web-vault to v2023.1.1
- Added a small patch to allow scrolling the organizations menu when
there are a lot of organizations.
Fixes https://github.com/dani-garcia/vaultwarden/issues/3148
I also created a PR at bitwarden/clients, pending approval.
This PR updates the web-vault to v2022.11.1
It also replaces the main logo and top left icon to indicate it is
Vaultwarden.
And the footer text has been change to `Vaultwarden (unofficial Bitwarden® server)`
This hopefully helps causing less confusion.
This version has a new feature which isn't supported yet by vaultwarden.
It shouln't be that hard to add this functionality i think.
You can now revoke and restore user access to an org.
Updated the web-vault to the latest released version.
This version is also using the new repo `bitwarden/clients` instead of the old `bitwarden/web`.
All files have been changed where needed.
- Updated web-vault to v2022.05.0
- Made several changes to the build scripts for ease of building/patching etc...
You can now run `make checkout` to pull/update the repo to the wanted version
There is also a `make patch-web-vault` to patch the repo
A `make generate-patch` to create a patch file from the current changes
And many more changes
The patch is almost identical just some offsets are different.
This version does solve the multiple `/sync` requests which will benefit
the loading time and load on the server!
- Added support for v2.26.1
- Hide some more input fields we do not use
- Fixed building with npm (The audit fix breaks the build)
- Fixed the vaultwarden version json filename.
There needs to be a small change on the vaultwarden server for this to
be fully supported as far as i could tell.
So maybe not yet ready for merge/tagging.
This patch is missing changes to `src/app/settings/two-factor-u2f.component.ts`,
which doesn't exist anymore since upstream moved from U2F to its successor,
WebAuthn, which Vaultwarden doesn't have backend support for yet.
We already had a patch to warn users they need HTTPS when they login.
This was not working for the register form.
- Added a warning during the submit of the register form.
- Changed the check to see if `crypto.subtle` is defined or not.
- Removed the `webpack.config.js` patch, since this now is in upstream.
- Updated README.md shields and small comment regarding how to create
the patch because of changes to the submodule.
