-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Organisation invitations via BWDC lead to faulty user profiles #4114
Comments
Can confirm this is an issue. I've noticed also that users show up as joined the organization, even though in reality they are still invited. Incase it helps for tracking down the issue I've noticed the following:
|
Can confirm BWDC is causing faulty issues here as well. Inside the vaultwarden Admin page it'll show they aren't part of the Organization. But on the vault itself in the Organization, they will show up as part of the Organization. |
Which version of BWDC are you all using? I can create accounts, login, confirm access and see the org ciphers. I also tested with SMTP/Mail disabled. So, i'm a bit confused regarding where this is coming from. Which type of Directory are you all using? |
BWDC (CLI) version: 2023.10.0
Here is a snippet from our BWDC config (some details censored):
SMTP is enabled in our scenario.
I will attempt to reproduce the bug and provide steps here in near future.
FreeIPA |
Version 2022.11.0 Windows Desktop
Snippet of my settings:
SMTP is enabled in my case. |
@ louisfgr i would suggest to update to the 2023 version of the Directory Connector, both Desktop and CLI, See https://github.com/bitwarden/directory-connector/releases |
I am able to reproduce the inconsistent user state event with the 2023.10 variant. I checked with some affected users that their org invite was still working, which it was, but the user was not able to fully join the org. Removing the user's access to the org and re-inviting him manually worked though. |
Invites expire after x amount of time. I would need to good step-by-step way to reproduce this, else i'm not really able to tackle this at all. |
At least in our deployment the problem presented itself with this string of actions:
|
Can confirm this is similar steps to what we've determined on our end as well. |
I looked at the log during synchronization but didn't notice anything unusual. Maybe someone else notices something. Those were my steps:
I also upgraded my BWDC to 2023.10.0 for this test. Log
|
I am seeing in the database table If you do revoke using the web vault, it'll update their If you do another revoke, after the user was moved to the invited tab from the first revoke, |
Thx for all the extra information. Hopefully i can reproduce this in some way. All other information is still welcome. I have not yet checked running it multiple times, but from memory, those didn't caused issues before. |
Multiple times may potentially be required. I've noticed in some testing that the first round of invites all show up fine in the Web Vault. But upon another round of invites (usually after clearing BWDC cache) does it start to show issues. |
I have been running into the same issue here using the Bitwarden Directory Connector. One of my sync settings was "Overwrite existing organization users based on current sync settings" - with this turned off, the issue doesn't appear to present. |
Looking at the configs shared above, others also have that set to false. |
Confirming that setting overwrite to off, The following was performed:
I'm thinking signs are pointing to something to do with the cache clearing process. |
I just had some time, and, clearing the cache, and run it again indeed triggers it for me to! Ill see what is going on here. |
Well, that was an easy fix on a stupid bug (caused by my self). |
Using the BWDC with a cleared cache caused invited users to be converted to accepted users. The problem was a wrong check for the `restore` function. Fixes dani-garcia#4114
Subject of the issue
Users who are invited to an organisation via BWDC are in a strange state between added and invited.
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
Steps to reproduce
-> Users are now listed as Invited in the Organisation and the Admin Panel
-> Users are now listed as a full member (Invite accepted and confirmed by Admin) in the Organisation but still as invited in the Admin Panel.
If I now manually create one of those users and log in, I can not access the Organisation.
Expected behaviour
User gets an Invitation and is able to join the Organisation. The described setup works perfectly on my 1.29.2 live system.
Actual behaviour
In the Admin Panel the User is not shown as part of any Organisation.
The Organisation shows the user as a full member.
The text was updated successfully, but these errors were encountered: