-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Org managers can't create or manage collections #1136
Labels
bug
Something isn't working
enhancement
New feature or request
low priority
Won't fix anytime soon, but will accept PR if provided
Comments
We are facing with the same issue. Is there any workaround? |
@blacklist-arcc, and i don't think there actually is a workaround at this point |
BlackDex
added
bug
Something isn't working
enhancement
New feature or request
low priority
Won't fix anytime soon, but will accept PR if provided
labels
Oct 9, 2020
@BlackDex Any progress on it? It is not really a low priority for us :( |
Closed
Closed
We will test this in our staging environment. Feedback in the next business days |
BlackDex
added a commit
to BlackDex/vaultwarden
that referenced
this issue
Nov 27, 2020
This has been requested a few times (dani-garcia#1136 & dani-garcia#246 & forum), and there already were two (1:1 duplicate) PR's (dani-garcia#1222 & dani-garcia#1223) which needed some changes and no followups or further comments unfortunally. This PR adds two auth headers. - ManagerHeaders Checks if the user-type is Manager or higher and if the manager is part of that collection or not. - ManagerHeadersLoose Check if the user-type is Manager or higher, but does not check if the user is part of the collection, needed for a few features like retreiving all the users of an org. I think this is the safest way to implement this instead of having to check this within every function which needs this manually. Also some extra checks if a manager has access to all collections or just a selection.
BlackDex
added a commit
to BlackDex/vaultwarden
that referenced
this issue
Dec 2, 2020
This has been requested a few times (dani-garcia#1136 & dani-garcia#246 & forum), and there already were two (1:1 duplicate) PR's (dani-garcia#1222 & dani-garcia#1223) which needed some changes and no followups or further comments unfortunally. This PR adds two auth headers. - ManagerHeaders Checks if the user-type is Manager or higher and if the manager is part of that collection or not. - ManagerHeadersLoose Check if the user-type is Manager or higher, but does not check if the user is part of the collection, needed for a few features like retreiving all the users of an org. I think this is the safest way to implement this instead of having to check this within every function which needs this manually. Also some extra checks if a manager has access to all collections or just a selection. fixes dani-garcia#1136
Koisell
pushed a commit
to Koisell/vaultwarden
that referenced
this issue
Feb 17, 2021
This has been requested a few times (dani-garcia#1136 & dani-garcia#246 & forum), and there already were two (1:1 duplicate) PR's (dani-garcia#1222 & dani-garcia#1223) which needed some changes and no followups or further comments unfortunally. This PR adds two auth headers. - ManagerHeaders Checks if the user-type is Manager or higher and if the manager is part of that collection or not. - ManagerHeadersLoose Check if the user-type is Manager or higher, but does not check if the user is part of the collection, needed for a few features like retreiving all the users of an org. I think this is the safest way to implement this instead of having to check this within every function which needs this manually. Also some extra checks if a manager has access to all collections or just a selection. fixes dani-garcia#1136
thelittlefireman
pushed a commit
to thelittlefireman/bitwarden_rs
that referenced
this issue
Mar 19, 2021
This has been requested a few times (dani-garcia#1136 & dani-garcia#246 & forum), and there already were two (1:1 duplicate) PR's (dani-garcia#1222 & dani-garcia#1223) which needed some changes and no followups or further comments unfortunally. This PR adds two auth headers. - ManagerHeaders Checks if the user-type is Manager or higher and if the manager is part of that collection or not. - ManagerHeadersLoose Check if the user-type is Manager or higher, but does not check if the user is part of the collection, needed for a few features like retreiving all the users of an org. I think this is the safest way to implement this instead of having to check this within every function which needs this manually. Also some extra checks if a manager has access to all collections or just a selection. fixes dani-garcia#1136
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
enhancement
New feature or request
low priority
Won't fix anytime soon, but will accept PR if provided
According to https://bitwarden.com/help/article/user-types-access-control/#user-types, org managers should be able to:
Attempting to create a new collection via the web vault results in
and log messages
Attempting to manage an existing collection via the web vault results in the
Your login session has expired
UI message, and log messages(This issue was first reported at https://bitwardenrs.discourse.group/t/manager-can-not-create-a-collection/287.)
The text was updated successfully, but these errors were encountered: