Skip to content
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

Potential race condition with ACL & group editing #26

Open
ctdk opened this issue Nov 17, 2014 · 2 comments
Open

Potential race condition with ACL & group editing #26

ctdk opened this issue Nov 17, 2014 · 2 comments
Labels
Status: To be prioritized Indicates that product needs to prioritize this issue. Triage: Try Reproducing Indicates that this issue needs to be reproduced. Type: Bug Does not work as expected.

Comments

@ctdk
Copy link

ctdk commented Nov 17, 2014

As I've been working on adding orgs+RBAC to goiardi, I noticed that the behavior oc-chef-pedant expects when you edit the ACL or groups is to provide a list of the actors and groups to be in the group, whereupon the existing actors and groups in the ACL or group is cleared out and the actors and groups in the request are added back in.

This leads to a situation where if two people are simultaneously editing a group or ACL, or if a user is being created at the same moment a group is being edited, one of the changes could be overwritten. This could lead to strange situations where a user that's been added to an org is not in the users group, or trying to remove access from a group or actor gets overwritten and they retain their access.

It may be better to explicitly add and remove users from ACLs and groups to prevent this. It might be a little more cumbersome for the tooling, but I think it would be safer all around.

@mmzyk
Copy link
Contributor

mmzyk commented Nov 17, 2014

@ctdk I believe we caught this exact issue earlier and it's been updated in either RC5 or RC6. Let me see if I can dig it up and you can verify if it's the same.

@ctdk
Copy link
Author

ctdk commented Nov 17, 2014

Has oc-chef-pedant been updated to reflect that? That would be awesome.

-j

On Mon, Nov 17, 2014 at 1:24 PM, Mark Mzyk [email protected] wrote:

@ctdk https://github.com/ctdk I believe we caught this exact issue
earlier and it's been updated in either RC5 or RC6. Let me see if I can dig
it up and you can verify if it's the same.


Reply to this email directly or view it on GitHub
#26 (comment).

@sdelano sdelano added this to the help-wanted milestone May 20, 2015
@PrajaktaPurohit PrajaktaPurohit added the Status: Untriaged An issue that has yet to be triaged. label Oct 11, 2019
@PrajaktaPurohit PrajaktaPurohit added Triage: Try Reproducing Indicates that this issue needs to be reproduced. Type: Bug Does not work as expected. Aspect: Correctness Status: To be prioritized Indicates that product needs to prioritize this issue. and removed Status: Untriaged An issue that has yet to be triaged. labels Jul 31, 2020
@stevendanna stevendanna removed this from the help-wanted milestone Sep 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: To be prioritized Indicates that product needs to prioritize this issue. Triage: Try Reproducing Indicates that this issue needs to be reproduced. Type: Bug Does not work as expected.
Projects
None yet
Development

No branches or pull requests

6 participants