-
-
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
Single Orginization policy erroneously removed all members from org #4205
Comments
What happened is the expected behavior as described at Bitwarden. |
@BlackDex I've read the passage you linked multiple times and it's still unexpected to me.
None of the ejected memebers were part of multiple orgs. Sorry I'm being dense here, can you point out the exact wording that I'm missing that would make this expected behavior?
There is that passage, but I'm pretty sure this is refering to members that have accepted an invite to an org but not yet been confirmed by an admin. |
Are you sure the users were not part of any other org? It checks if the count of organisations is greater then 1 and if there user isn't an admin or owner or not in an invited state, if then the count is more then 1, those users will be deleted. So that tells me the users should be in a different organization too. |
@BlackDex Unless they are talking about orgs outside my instance then yes, there is only one org on my instance: |
And the user count there doesn't match the amount of users you are expecting? Those 18 are all admin or owner level users? |
Looks like the query which does the count is wrong. |
There was an error in the single org policy check to determine how many users there are in an org. The `or` check was at the wrong location in the DSL. This is now fixed. Fixes dani-garcia#4205
@BlackDex sorry for asking in this PR, but it is related. Isn't every user in the pseudo org |
That is only a group used for invites, nothing used for anything else. |
There was an error in the single org policy check to determine how many users there are in an org. The `or` check was at the wrong location in the DSL. This is now fixed. Fixes #4205
There was an error in the single org policy check to determine how many users there are in an org. The `or` check was at the wrong location in the DSL. This is now fixed. Fixes dani-garcia#4205
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: DOMAIN, ADMIN_TOKEN
Steps to reproduce
I was trying to turn on the
Account recovery administration
org policy but it required theSingle Organization
policy to be turned on first. When turning on theSingle Organization
policy it does warn that:But I didn't expect this to apply to anyone on our vaultwarden instance because our instance only has a single org on it.
Expected behaviour
I would have expected the policy to turn on and that no one would be removed from my org.
Actual behaviour
All non-admin/owners were removed from my org.
The text was updated successfully, but these errors were encountered: