mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #920] Sign up after invitation is broken #654
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#654
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 @paradeiser on GitHub (Mar 19, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/920
It's not possible to create account after invitation
my variables are
hence: Public signups are disallowed, but invited email addresses are able to create an account.
Before the latest update all worked as expected - no changes to setup since then.
Behaviour as expected when using vault.bitwarden.com
My environment
Steps to reproduce
Expected behaviour
Actual behaviour
tried different browsers, cleared all cookies and browser-data; restarted docker.
@BlackDex commented on GitHub (Mar 19, 2020):
I think this will be fixed with the latest build based upon the latest commit which is not build as of yet.
I can't check at this moment if that is the case, but if i check the link it uses it should.
@BlackDex commented on GitHub (Mar 19, 2020):
Well just tested it. Doesn't solve it. So this is something else.
@Stiefmeister commented on GitHub (Mar 20, 2020):
Got the same problem - first thought it had something to do with my reverse proxy setup (letsencrypt); but behavior is the same locally. Tried different browsers as well, no luck
@BlackDex commented on GitHub (Mar 20, 2020):
This has something to do with the new policies in the latest web-vault 2.13.1.
@Stiefmeister commented on GitHub (Mar 20, 2020):
Had a look at the logs, seems some kind of access token is expected for invited users!?
[2020-03-20 09:32:34][request][INFO] GET /api/organizations/_/policies/token?token=#################
[2020-03-20 09:32:34][auth][ERROR] Unauthorized Error: No access token provided
[2020-03-20 09:32:34][response][INFO] GET /api/organizations/<org_id>/policies/<pol_type> (get_policy) => 401 Unauthorized
@BlackDex commented on GitHub (Mar 20, 2020):
Yea, we found what the issue is.
This is because of the new policy rules which are available in the latest web-vault.
There you can enforce specific password policies etc..
That is what is breaking the invites now.
@BlackDex commented on GitHub (Mar 20, 2020):
btw. you can workaround this by using an older web-vault which does not have this.
You need to download https://github.com/dani-garcia/bw_web_builds/releases/tag/v2.12.0e extract it in a specific folder in your data folder. And then configure bitwarden_rs via the
WEB_VAULT_FOLDERenv variable to use that specific folder.@paradeiser commented on GitHub (Mar 20, 2020):
Thanks!
Is there an ETA for a release that fixes this bug?
@BlackDex commented on GitHub (Mar 20, 2020):
Fix is committed, now we have to wait for the all mighty docker hub to finish the new build.
@Stiefmeister commented on GitHub (Mar 20, 2020):
Thanks for the swift fix/ support!
@paradeiser commented on GitHub (Mar 20, 2020):
superb! merci and thanks a lot!
@paradeiser commented on GitHub (Mar 20, 2020):
I can confirm: latest build is up and fixed the issue. Thanks a lot!
@dani-garcia commented on GitHub (Mar 21, 2020):
This should be fixed now in 1.14.1, but it might take some hours for the docker images to build still.
@samgaw58 commented on GitHub (May 28, 2021):
I am running Vaultwarden V1.21.1 on Portainer and I am getting the same error. If I invite a new user, click the email link and then click create account I get the same error that the user already exists.
Is there any workaround I can do?
@samgaw58 commented on GitHub (May 28, 2021):
Here are the last three lines of the logs
[2021-05-28 19:02:35.196][request][INFO] POST /api/accounts/register
[2021-05-28 19:02:35.196][vaultwarden::api::core::accounts][ERROR] User already exists
[2021-05-28 19:02:35.196][response][INFO] POST /api/accounts/register (register) => 400 Bad Request