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.

Sign up for GitHub

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

Jump to bottom

[DQT] Implement permissions on data access #5152

Closed
ridz1208 opened this issue Aug 27, 2019 · 4 comments
Closed

[DQT] Implement permissions on data access #5152

ridz1208 opened this issue Aug 27, 2019 · 4 comments
Assignees
@driusan
Labels
Category: Feature PR or issue that aims to introduce a new feature Category: Security PR or issue that aims to improve security

Comments

@ridz1208
Copy link
Collaborator

ridz1208 commented Aug 27, 2019 •
edited
Loading

Users that have access to the DQT are not limited to the data of the sites and projects they belong to.

These permissions should be applied on data returned to the browser

Redmine: #10851
@johnsaigle johnsaigle added Category: Feature PR or issue that aims to introduce a new feature Category: Security PR or issue that aims to improve security labels Oct 16, 2019
@SantiagoTG SantiagoTG mentioned this issue Oct 3, 2021
Closed
14 tasks
@ridz1208
Copy link
Collaborator Author

Will be resolved by @driusan's revamp

@driusan
Copy link
Collaborator

driusan commented Nov 30, 2022

It's still an issue until thats done.

@driusan driusan reopened this Nov 30, 2022
@driusan
Copy link
Collaborator

driusan commented Dec 20, 2022

Permissions are enforced in the backend by #8268 but since no one will use that until there's a new frontend I think this needs to stay open.

@driusan
Copy link
Collaborator

driusan commented Jan 23, 2024

The frontend was merged in #8907. The new DQT still needs to be iterated on to incorporate all the information from the old CouchDB import scripts, but I think this can be closed as resolved now.

@driusan driusan closed this as completed Jan 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@driusan driusan

Labels
Category: Feature PR or issue that aims to introduce a new feature Category: Security PR or issue that aims to improve security
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@driusan @johnsaigle @ridz1208