Repository navigation
Remove MVP-specific hard-coding #156
Description
Description
Several parts of the authorization logic include hard-coded behaviors introduced for the Ulmo MVP. These assumptions limit the framework’s ability to support additional scopes and create inconsistent behavior across different areas of the ecosystem if we plan to scale.
This issue tracks:
- Identifying all places where authorization logic depends on hard-coded assumptions.
- Documenting how these assumptions block support for additional scopes.
- Implement the needed long-term changes to remove these hard-coded paths and unify behavior across scope types.
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
BryanttV commentedon Aug 3, 2026
A review of the
openedx-authz/openedx-platformwas carried out, and no additional version-specific code (such as Ulmo or Verawood) that requires action on our part was found.Previously, a subtask specifically related to Ulmo (issue #127) was completed, which was handled by Diana Huang at the time. The issue tracking for that task was closed. Since there are no new findings, we are closing this preventive task. Should anything related arise in the future, the corresponding issues will be opened to address it.