openedx / openedx/openedx-authz
Audit: Review Authz Mapping Decisions for LMS Permissions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 9
- Avg merge
- 13d 9h
- Merged PRs (30d)
- 9
Description
Description
This issue serves as a reminder to audit the permission mapping decisions made during the migration from the legacy authz system to the new framework.
When the LMS Permissions review begins, we must re-evaluate the "best-effort" matches implemented to ensure they align with the platform's security model and architectural standards.
Key Areas to Re-examine
- Legacy vs. New Parity: Review cases where a 1:1 match wasn't possible and a manual mapping was chosen.
- Content Library Decisions: Re-audit the specific logic applied to Content Library permissions to ensure consistency.
- MFE Impact: Ensure these mappings correctly authorize actions in the
frontend-app-learningandfrontend-app-authoringinterfaces.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the legacy-to-new authorization mappings, then review the best-effort matches and Content Library decisions against the platform security model; check their effects in frontend-app-learning and frontend-app-authoring. Done means the mappings have been audited for parity, consistency, and correct authorization behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authorization, frontend, security
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100