Aiven-Open / Aiven-Open/klaw

EPIC: Permission based control for users

未關閉
#2,272 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
epic
主要語言
Java
星號
195
分支
77
平均合併
8 天 9 小時
30 天內合併 PR
1

描述

# 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

貢獻指南

開啟貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。