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

EPIC: Permission based control for users #2272

Open
1 task
aindriu-aiven opened this issue Feb 9, 2024 · 0 comments
Open
1 task

EPIC: Permission based control for users #2272

aindriu-aiven opened this issue Feb 9, 2024 · 0 comments
Labels
epic Represents a bigger chunk of work, which is resolved by number of linked issues.

Comments

@aindriu-aiven
Copy link
Contributor

What is currently missing?

Currently Coral is allowing access to new screens based off the role type of users, "USERS" get access to Coral and "SUPERADMIN" users do not.

Some API Endpoints do not have sufficient guards put in place to prevent users from using curl or if some endpoints are available to users on coral they do not get the correct "unauthorized" response from the Back end API.

e.g. if a user does not have VIEW_TOPICS permission the API to GetTopics should return an unauthorized response.

How could this be improved?

All back end API endpoints should have correct api permission guards in place.

Coral can use the permission model to prevent some views from appearing when they do not have permissions or grey out buttons when not required.

e.g. If a user does not have VIEW_TOPICS permission Coral would not show the Topic Catalog.

Is this a feature you would work on yourself?

  • I plan to open a pull request for this feature
@aindriu-aiven aindriu-aiven added the epic Represents a bigger chunk of work, which is resolved by number of linked issues. label Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic Represents a bigger chunk of work, which is resolved by number of linked issues.
Projects
None yet
Development

No branches or pull requests

1 participant