mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #534] Create organization?? #342
Labels
No 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
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#342
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @MrMEEE on GitHub (Jul 15, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/534
Hi
I'm getting this, when I try to add an organization???
Shouldn't this be available??
@MrMEEE commented on GitHub (Jul 15, 2019):
Oh.. this is only if I built the web-vault myself... weird
@MrMEEE commented on GitHub (Jul 15, 2019):
No ... I was mistaken... same issue
@dani-garcia commented on GitHub (Jul 15, 2019):
This should work using the official docker images, if you are building the web vault yourself you need to apply the patches: https://github.com/dani-garcia/bw_web_builds/tree/master/patches
Or you can download the prebuilts from here: https://github.com/dani-garcia/bw_web_builds/releases
@MrMEEE commented on GitHub (Jul 15, 2019):
I have applied the patches..
I have just tried it with your prebuilts... still the same...
@dani-garcia commented on GitHub (Jul 15, 2019):
I'm not sure why that could be happening then. Make sure your browser doesn't have an old version cached or that bitwarden_rs is serving the correct version.
Also make sure you are building the web vault correctly after applying the patches (tho i'm pretty sure it's just
npm run dist).For reference this is what i'm getting:
@MrMEEE commented on GitHub (Jul 15, 2019):
Forget it, I must have done something wrong.. works now, sorry
@tabsnotspaces9 commented on GitHub (Mar 27, 2022):
Good call on the cached version. Switching over from official Bitwarden to Vaultwarden retained some Bitwarden restrictions in the web UI. Doing a hard reload resolved the problem and the Vaultwarden patches were correctly applied.