Skip to content

Conversation

@BryanttV
Copy link
Contributor

@BryanttV BryanttV commented Oct 23, 2025

Description

This PR adds a custom matcher to the Casbin model. The matcher allows validating permissions based on library or user attributes, similar to how it’s currently handled with bridgekeeper.

For now, it only checks whether the user is staff or a superuser to grant all permissions.

This implementation is based on the work done in #101

Related Issues

Testing Instructions

Using Tutor:

  1. Install this plugin with the changes in this PR.
  2. Run the migrations by running tutor dev exec lms python manage.py lms migrate
  3. Load the default policies by running tutor dev exec lms python manage.py lms load_policies
  4. Test custom enforcements by running tutor dev exec lms python manage.py lms enforcement and verify that staff and superuser users have granted permissions in any library in any action.

Merge Checklist:

Check off if complete or not applicable:

  • Version bumped
  • Changelog record added
  • Documentation updated (not only docstrings)
  • Fixup commits are squashed away
  • Unit tests added/updated
  • Manual testing instructions provided
  • Noted any: Concerns, dependencies, migration issues, deadlines, tickets

@openedx-webhooks openedx-webhooks added open-source-contribution PR author is not from Axim or 2U core contributor PR author is a Core Contributor (who may or may not have write access to this repo). labels Oct 23, 2025
@openedx-webhooks
Copy link

openedx-webhooks commented Oct 23, 2025

Thanks for the pull request, @BryanttV!

This repository is currently maintained by @openedx/committers-openedx-authz.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

  • If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
    • This process (including the steps you'll need to take) is documented here.
  • If it doesn't, simply proceed with the next step.
🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

  • Dependencies

    This PR must be merged before / after / at the same time as ...

  • Blockers

    This PR is waiting for OEP-1234 to be accepted.

  • Timeline information

    This PR must be merged by XX date because ...

  • Partner information

    This is for a course on edx.org.

  • Supporting documentation
  • Relevant Open edX discussion forum threads
🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details
Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

  • The size and impact of the changes that it introduces
  • The need for product review
  • Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

@github-project-automation github-project-automation bot moved this to Needs Triage in Contributions Oct 23, 2025
@BryanttV BryanttV force-pushed the bav/attribute-checking branch from 3b0c476 to dcffff2 Compare October 27, 2025 13:57
@mphilbrick211 mphilbrick211 added the FC Relates to an Axim Funded Contribution project label Oct 27, 2025
@mphilbrick211 mphilbrick211 moved this from Needs Triage to Waiting on Author in Contributions Oct 27, 2025
@BryanttV BryanttV force-pushed the bav/attribute-checking branch from 70bffb1 to 75942e6 Compare October 31, 2025 21:57
@BryanttV BryanttV marked this pull request as ready for review October 31, 2025 22:45
@mariajgrimaldi mariajgrimaldi moved this to Ready for review in RBAC AuthZ Board Nov 3, 2025
@mariajgrimaldi mariajgrimaldi self-assigned this Nov 3, 2025
@mariajgrimaldi
Copy link
Member

Bryann is off this week so I'll be pushing this forward!

SyncedEnforcer: Configured Casbin enforcer with adapter and auto-sync
"""
# Avoid circular import
from openedx_authz.engine.matcher import check_custom_conditions # pylint: disable=import-outside-toplevel
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a way we can avoid this circular import?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I moved this and it didn't fail. I'll deploy this so I can test it remotely!


adapter = ExtendedAdapter()
enforcer = SyncedEnforcer(settings.CASBIN_MODEL, adapter)
enforcer.add_function("custom_check", check_custom_conditions)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we could call this: is_staff_or_superuser

("lib:AnyOrg1:ANYLIB1", True),
("lib:AnyOrg2:ANYLIB2", True),
("lib:AnyOrg3:ANYLIB3", True),
("sc:AnyScope1", False),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a note that I think sc here is out of date

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

True! I updated the tesr cases

User.objects.create_superuser(username="superuser", email="super@example.com", password="test")
User.objects.create_user(username="regular_user", email="regular@example.com", password="test")

@data(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need a test that handles non-existent library keys? I assume that would return False, right?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes! I added a test case here: 7805698

Copy link
Contributor

@bmtcril bmtcril left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Copy link
Contributor

@rodmgwgu rodmgwgu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thanks

Copy link
Contributor

@MaferMazu MaferMazu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this.

@mphilbrick211 mphilbrick211 moved this from Waiting on Author to In Eng Review in Contributions Nov 6, 2025
@mariajgrimaldi mariajgrimaldi merged commit b7e82cc into openedx:main Nov 11, 2025
13 checks passed
@github-project-automation github-project-automation bot moved this from Ready for review to Done in RBAC AuthZ Board Nov 11, 2025
@github-project-automation github-project-automation bot moved this from In Eng Review to Done in Contributions Nov 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core contributor PR author is a Core Contributor (who may or may not have write access to this repo). FC Relates to an Axim Funded Contribution project open-source-contribution PR author is not from Axim or 2U

Projects

Archived in project
Status: Done

Development

Successfully merging this pull request may close these issues.

Bug: As an admin or superuser, I can't manage access for a library

7 participants