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

Fix project permissions: anybody in org could see the list of projects #4201

Merged
merged 1 commit into from
Jan 20, 2022

Conversation

nmanovic
Copy link
Contributor

Motivation and context

All in organization could see the list of projects due to incorrent filter definition in the rules (it cannot be covered by opa tests and Django tests are not here yet).

How has this been tested?

Manually

Checklist

  • I submit my changes into the develop branch
    - [ ] I have added a description of my changes into CHANGELOG file
    - [ ] I have updated the documentation accordingly
    - [ ] I have added tests to cover my changes
    - [ ] I have linked related issues (read github docs)
    - [ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
    cvat-core, cvat-data and cvat-ui)

License

  • I submit my code changes under the same MIT License that covers the project.
    Feel free to contact the maintainers if that's a concern.
  • I have updated the license header for each file (see an example below)
# Copyright (C) 2022 Intel Corporation
#
# SPDX-License-Identifier: MIT

@nmanovic nmanovic merged commit 5e59ba1 into develop Jan 20, 2022
@nmanovic nmanovic deleted the nm/fix_project_perms branch January 20, 2022 07:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant