feat: enforce authz permissions for Pages & Resources endpoints

[wgu-taylor-payne]

Description

When the authz.enable_course_authoring flag is enabled use openedx-authz based permissions to authorize calls to the endpoints that support the Pages & Resources pages and functionality in Studio.

Supporting information

Closes openedx/openedx-authz#192.

Testing instructions

Automated tests:

pytest --ds="cms.envs.test" \
  cms/djangoapps/contentstore/rest_api/v0/tests/test_tabs_permissions.py \
  cms/djangoapps/contentstore/tests/test_tabs_permissions.py \
  openedx/core/djangoapps/course_apps/rest_api/tests/test_views_permissions.py \
  openedx/core/djangoapps/discussions/tests/test_views_permissions.py

Manual tests:
Prerequisite: Enable the authz.enable_course_authoring waffle flag for the test course. Assign users to authz roles: course_admin, course_staff, course_auditor, and one user with no role.

View Access

After selecting a course in the Studio course list, navigate to Pages & Resources from the Content dropdown. Course admin, staff, and auditor users should all see the page load with course app cards (Wiki, Discussions, Calculator, etc.). A user with no authz role should see a permission denied error.

Toggle Course Apps

From the Pages & Resources page, toggle a course app (e.g., Wiki) on or off. Course admin and staff should be able to toggle successfully. Course auditor should be denied — the toggle should either be disabled or return a 403.

Discussion Settings

Click the Discussion card to open discussion settings. Admin, staff, and auditor should all be able to view the providers list and current settings. Admin and staff should be able to change settings (e.g., toggle anonymous posting) and save. Auditor should be denied when attempting to save changes.

Custom Pages

Navigate to Custom Pages. Admin, staff, and auditor should see the list of existing custom pages. Admin and staff should be able to create a new page, edit an existing page's title/content, delete a page, reorder pages via drag- and-drop, and toggle tab visibility. Auditor should be denied on all write operations. A user with no role should not be able to view the custom pages list at all.

Deadline

Verawood

Other information

Co-authored with Kiro.

[openedx-webhooks]

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.

🔘 Update the status of your PR

Your PR is currently marked as a draft. After completing the steps above, update its status by clicking "Ready for Review", or removing "WIP" from the title, as appropriate.

---

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:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

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.