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

Change authz killCursor behavior #26

Open
jacksontj opened this issue Mar 13, 2023 · 0 comments
Open

Change authz killCursor behavior #26

jacksontj opened this issue Mar 13, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@jacksontj
Copy link
Contributor

The current killCursor implementation simply maps to a global delete permission. This was "accurate" based on old mongo behavior (<4.2) -- but in later versions users are always allowed to killCursor on cursors they created. So to do this we simply need to change the plugin to check the cursor cache (assocatied with the connection) and if the cursor they are killing is in there -- it doesn't need permissions. Then if the cursorId is not in the cache -- then we should check the same global delete permission.

@jacksontj jacksontj added the enhancement New feature or request label Mar 13, 2023
jacksontj added a commit to jacksontj/mongoproxy that referenced this issue Mar 16, 2023
jacksontj added a commit to jacksontj/mongoproxy that referenced this issue Mar 16, 2023
jacksontj added a commit to jacksontj/mongoproxy that referenced this issue Mar 17, 2023
jacksontj added a commit to jacksontj/mongoproxy that referenced this issue Mar 17, 2023
jacksontj added a commit to jacksontj/mongoproxy that referenced this issue Mar 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

1 participant