-
Notifications
You must be signed in to change notification settings - Fork 62
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
Broken feature after update 2023.5.0 - Unable to add user access permissions on Organization Collections #186
Comments
Thank you for bringing this to our observation. I am unable to reproduce this issue, reasons been that the Bitwarden server version is on 2023.10.2 while you seem to be using an older version 2023.5.0 could you please update to the lasted version of Bitwarden and let us know if this issue persists. We use GitHub issues as a place to track bugs and other development related issues. If your issue persists, please write us back using our “Contact support” form located on our Help Center (https://bitwarden.com/help/). You can include a link to this issue in the message content. Alternatively, you can also search for an answer in our help documentation (https://bitwarden.com/help/) or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/). The issue here will be closed. Thanks! |
I felt hopeful after reading the changelog of the 2023.12.0 release "Bug fix for users with custom permissions import to organization". |
Same here... in api.log:
I'm using Version 2023.12.0. |
I found the cause of my issue. |
still there, any news? |
I'm unable to add user to a Collection in my Organization after the docker image upgrade. If i add a Group instead it works. The procedure gives a green pop up but the user is not added to the Collection access rules.
Tried with every user role (Owner, Administrator etc etc).
The feature worked until bitwarden 2023.5.0, i'm unable to downgrade to any older version because there's no beta tag that can go further past. I'm stuck with the latest bitwarden/self-host:beta now
I have no error in the browser console or the kubernetes container
The text was updated successfully, but these errors were encountered: