feat: split read vs write authz checks for certificates

[wgu-taylor-payne]

Description

Updates the certificates REST API v1 endpoint to use courses.view_certificates for GET access and courses.manage_certificates for write access. Adds a can_manage flag to the API response so the frontend can conditionally render edit controls.

Previously, the GET handler checked COURSES_MANAGE_CERTIFICATES with LegacyAuthoringPermission.WRITE, which blocked Course Editors and Auditors from viewing certificates entirely. Per the design in openedx/openedx-authz#283 and openedx/openedx-authz#329, users with view access should see the page in read-only mode.

User roles impacted: Course Editor, Course Auditor — can now view (but not edit) certificates when authz is enabled.

Changes:

• cms/djangoapps/contentstore/rest_api/v1/views/certificates.py: Use VIEW_CERTIFICATES for access gate, add can_manage check
• cms/djangoapps/contentstore/rest_api/v1/serializers/certificates.py: Add can_manage field
• Tests: Updated and added tests for staff (can_manage=True), editor/auditor (can_manage=False), and unauthorized (403)

Rollback: Gated behind AUTHZ_COURSE_AUTHORING_FLAG — disabling the flag reverts to legacy behavior.

Supporting information

• Closes Add courses.view_certificates enforcement in openedx-platform openedx-authz#395
• Related: Task - Add the courses.view_certificates permission openedx-authz#329, Design: Course Editor & Course Auditor screen restrictions openedx-authz#283

Testing instructions

1. Enable AUTHZ_COURSE_AUTHORING_FLAG for a course
2. Assign a user the course_editor role
3. GET /api/contentstore/v1/certificates/{course_id} → 200 with can_manage: false
4. Assign course_staff role → 200 with can_manage: true
5. User with no role → 403

Deadline

None

[openedx-webhooks]

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

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

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:

• 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.