akai-org / akai-org/put-wiki

Access control

未關閉
#31 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
area:backend type:task
主要語言
TypeScript
星號
6
分支
3
平均合併
3 天 17 小時
30 天內合併 PR
15

描述

## Summary
We need an authorization mechanism to manage backend permissions. Every API endpoint must be explicitly protected against unauthorized access. The system must differentiate privileges between Administrators, standard Users, and Guests (with posibility to extend it easily) using specific access control model (e.g. Roles, Claims).

## Acceptance criteria
- [ ] Evaluate and choose between RBAC (Role-Based Access Control) or CBAC (Claims-Based Access Control) documenting the decision.
- [ ] Ensure all existing and future endpoints require authentication by default, requiring explicit opt-outs for public endpoints (or in opposite if justified)
- [ ] Define and implement the base set of privileges within the chosen model.
- [ ] Ensure that backend consistently returns appropriate HTTP status codes and that they are documented in API docs.

## Visuals (optional)
screenshots, figma links, etc.

## Notes
This might help to determine what would fit best as an access control model for our app: https://stackoverflow.com/questions/22814023/role-based-access-control-rbac-vs-claims-based-access-control-cbac-in-asp-n

貢獻指南

開啟貢獻指南

評估

這個 Issue 還沒有評估資料。

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

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