Skip to content

feat: add authz permission to search_reindex endpoint#38348

Open
dwong2708 wants to merge 2 commits intoopenedx:masterfrom
WGU-Open-edX:dwong2708/authz_on_search_reindex
Open

feat: add authz permission to search_reindex endpoint#38348
dwong2708 wants to merge 2 commits intoopenedx:masterfrom
WGU-Open-edX:dwong2708/authz_on_search_reindex

Conversation

@dwong2708
Copy link
Copy Markdown
Contributor

@dwong2708 dwong2708 commented Apr 10, 2026

Description

This PR adds authorization enforcement to the search reindex endpoint as part of the course list page permissions work.

The original ticket introduced new permissions behind a feature flag for multiple course-related endpoints, but the following endpoint was not covered:

GET /course/{course_id}/search_reindex/

This change ensures the endpoint is now protected and aligned with the overall AuthZ strategy.

Changes

  • Enforce AuthZ permission on search_reindex endpoint
  • Guard the behavior behind the existing feature flag
  • Keep consistency with previously implemented course-level permission

Permission Applied

courses.create_course

This permission is currently used as the closest available match for restricting access to this operation, ensuring that only authorized users can trigger a reindex.

Supporting information

This PR completes the missing piece from the ticket: #38129

Testing instructions

Please provide detailed step-by-step instructions for testing this change.

Deadline

Verawood

Other information

Closes:

@openedx-webhooks openedx-webhooks added the open-source-contribution PR author is not from Axim or 2U label Apr 10, 2026
@openedx-webhooks
Copy link
Copy Markdown

openedx-webhooks commented Apr 10, 2026

Thanks for the pull request, @dwong2708!

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 Apr 10, 2026
@dwong2708 dwong2708 marked this pull request as ready for review April 10, 2026 23:23
@dwong2708 dwong2708 requested a review from Copilot April 10, 2026 23:39
if not has_course_author_access(user, course_key):
if not user_has_course_permission(
user=user,
authz_permission=COURSES_CREATE_COURSE.identifier,
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I'm leaning more towards the edit course or publish course permissions for this, pending confirmation from product.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Adds AuthZ-based authorization enforcement for the Studio course search reindex endpoint (GET /course/{course_id}/search_reindex/) to align with the broader course authoring permissions rollout behind the existing feature flag.

Changes:

  • Enforce AuthZ permission (courses.create_course) in reindex_course_and_check_access.
  • Gate course_search_index_handler behavior on the course authoring AuthZ feature flag (legacy behavior when disabled).
  • Add an AuthZ-focused test class for the reindex endpoint.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File Description
cms/djangoapps/contentstore/views/course.py Switches reindex access checks to user_has_course_permission(...) and adjusts endpoint gating under the AuthZ feature flag.
cms/djangoapps/contentstore/views/tests/test_course_index.py Adds an AuthZ test class intended to validate allow/deny behavior for reindexing.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

open-source-contribution PR author is not from Axim or 2U

Projects

Status: Needs Triage

Development

Successfully merging this pull request may close these issues.

4 participants