akai-org / akai-org/put-wiki

Access control

Aberta
#31 1 comentário 0 reações 0 responsáveis Ver no GitHub
area:backend type:task
Linguagem predominante
TypeScript
Estrelas
6
Forks
3
Merge médio
3d 17h
PRs com merge (30d)
15

Descrição

## 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

Guia de contribuição

Abrir o guia de contribuição

Avaliação

Esta issue ainda não foi avaliada.

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.