Skip to content

feat: use authz permissions on xblock handler when enabled#38179

Merged
wgu-taylor-payne merged 1 commit intoopenedx:masterfrom
WGU-Open-edX:tpayne/xblock-authoring-authz
Mar 20, 2026
Merged

feat: use authz permissions on xblock handler when enabled#38179
wgu-taylor-payne merged 1 commit intoopenedx:masterfrom
WGU-Open-edX:tpayne/xblock-authoring-authz

Conversation

@wgu-taylor-payne
Copy link
Contributor

@wgu-taylor-payne wgu-taylor-payne commented Mar 17, 2026

Description

Use openedx-authz permissions for the /xblock/ endpoint, when the AUTHZ_COURSE_AUTHORING_FLAG is enabled for the given course. The mapping between actions in the CMS and the associated permission is found in this document.

If the AUTHZ_COURSE_AUTHORING_FLAG is disabled then the legacy permission checks will occur.

Supporting information

Closes #37925.

Testing instructions

Run pytest on the new test module cms/djangoapps/contentstore/tests/test_xblock_handler_permissions.py.

To test manually, make sure that the AUTHZ_COURSE_AUTHORING_FLAG is enabled for the course you are testing, and that openedx-platform is using openedx-authz >= 0.22.0. Run manage.py cms load_policies to ensure latest casbin policies have been loaded and then assign course related roles to the users you are testing. Go though the actions outlined in the document linked above and verify that the correct permissions are checked and applied for the given user.

Deadline

Verawood.

@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 Mar 17, 2026
@openedx-webhooks
Copy link

openedx-webhooks commented Mar 17, 2026

Thanks for the pull request, @wgu-taylor-payne!

This repository is currently maintained by @openedx/wg-maintenance-openedx-platform.

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 Mar 17, 2026
@wgu-taylor-payne wgu-taylor-payne marked this pull request as draft March 17, 2026 00:07
@wgu-taylor-payne wgu-taylor-payne force-pushed the tpayne/xblock-authoring-authz branch 4 times, most recently from eb5b8b6 to cfa5592 Compare March 17, 2026 19:44
@wgu-taylor-payne wgu-taylor-payne marked this pull request as ready for review March 17, 2026 21:06
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.

Tested a couple of use cases in my local and works as expected, looks good, thanks!

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.

Just one optional comment, otherwise looks good to me and works locally 👍

str: The permission identifier (e.g., 'courses.view_course'), or None if authz should be skipped
"""
if usage_key_string:
# Skip authz for library context
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you add more context about where enforcement is handled in content libraries here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure, I've added more context.

Copy link
Contributor

@dwong2708 dwong2708 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! Just one non-blocking suggestion and one question.

When I worked on Instructor Dashboard V2, I noticed that ORA2 (a custom XBlock) internally calls an endpoint via a custom XBlock handler:

http://local.openedx.io:8000/courses/course-v1:WGU+CS002+2025_T1/xblock/block-v1:WGU+CS002+2025_T1+type@openassessment+block@ff4f5fddf42d4b9787e69c1a8cbeb058/handler/get_ora2_responses

This points to cms/djangoapps/contentstore/views/component.py (component_handler).

This made me wonder whether we should also take this endpoint into account.

Image

elif request.method == "DELETE":
if block_type == "static_tab":
return COURSES_MANAGE_PAGES_AND_RESOURCES.action.external_key
return COURSES_EDIT_COURSE_CONTENT.action.external_key
Copy link
Contributor

Choose a reason for hiding this comment

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

It would be nice to standardize the use of the identifier. As I’ve seen, in other places the <AUTHZ_PERM>.identifier style is more commonly used and shorter

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks, I've changed those.

@wgu-taylor-payne
Copy link
Contributor Author

wgu-taylor-payne commented Mar 19, 2026

This made me wonder whether we should also take this endpoint into account.

@dwong2708 I scoped this PR to just the /xblock/ endpoint (specifically the cms.djangoapps.contentstore.views.block.xblock_handler view) based on the GitHub issue and the Spike issue. This endpoint has several different use cases.

As you have brought up, there are other xblock related endpoints that are called in different course related pages/contexts in the CMS, but I was thinking that those would be implemented as part of the existing M1 tasks. So, as we implement our tickets, we just need to be aware that only this specific xblock view has been covered and the others will need to be addressed as we go along. Does that sound right @rodmgwgu? Or should I look at more xblock endpoints here?

Co-authored-by: Kiro <noreply@kiro.dev>
@wgu-taylor-payne wgu-taylor-payne force-pushed the tpayne/xblock-authoring-authz branch from cfa5592 to 508e85d Compare March 19, 2026 22:41
@dwong2708
Copy link
Contributor

This made me wonder whether we should also take this endpoint into account.

@dwong2708 I scoped this PR to just the /xblock/ endpoint (specifically the cms.djangoapps.contentstore.views.block.xblock_handler view) based on the GitHub issue and the Spike issue. This endpoint has several different use cases.

As you have brought up, there are other xblock related endpoints that are called in different course related pages/contexts in the CMS, but I was thinking that those would be implemented as part of the existing M1 tasks. So, as we implement our tickets, we just need to be aware that only this specific xblock view has been covered and the others will need to be addressed as we go along. Does that sound right @rodmgwgu? Or should I look at more xblock endpoints here?

Makes sense. Whether we decide to address the other XBlock endpoints or not, I think scoping this task to the XBlock handler sounds good to me. Thanks.

@wgu-taylor-payne wgu-taylor-payne merged commit 82b5675 into openedx:master Mar 20, 2026
48 checks passed
@github-project-automation github-project-automation bot moved this from Needs Triage to Done in Contributions Mar 20, 2026
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). open-source-contribution PR author is not from Axim or 2U

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Task - RBAC AuthZ - Implement new permission checks on xblock endpoint

5 participants