Skip to content

fix(courseware): restore anonymous video viewing on public courses#38324

Closed
kingoftech-v01 wants to merge 1 commit intoopenedx:masterfrom
kingoftech-v01:fix/bug-38019
Closed

fix(courseware): restore anonymous video viewing on public courses#38324
kingoftech-v01 wants to merge 1 commit intoopenedx:masterfrom
kingoftech-v01:fix/bug-38019

Conversation

@kingoftech-v01
Copy link
Copy Markdown

@kingoftech-v01 kingoftech-v01 commented Apr 10, 2026

Withdrawn by author.

I submitted 36 pull requests in a short window and mass-tagged the maintenance working group. That was the wrong way to approach this repository. I apologise to @kdmccormick and to the @openedx/wg-maintenance-openedx-platform members for the notification noise.

For the security-related patches, I should have used the private disclosure channel at security@openedx.org rather than public pull requests. The original body of this PR included exploit paths and affected line numbers; that content has been removed here to avoid indexing. Any legitimate security finding will be re-reported privately through the proper channel.

For the bug-fix patches, I plan to re-engage the community through the correct process: discussing on https://discuss.openedx.org first, then submitting one focused change per PR, and only tagging maintainers when a PR has passed CI and an individual reviewer asks to be involved.

No further action requested on this PR.

Three distinct defects combined to break anonymous (unauthenticated)
access to video blocks on public courses with the unenrolled-access
waffle enabled:

1. CourseNavigationBlocksView.completions_dict queried BlockCompletion
   with request.user, which raised TypeError for AnonymousUser and
   returned a 500 from the navigation API. Short-circuit with an empty
   mapping for anonymous users.
2. _has_access_course.can_load did not bypass check_course_open_for_learner
   for anonymous users on public courses, so public courses with future
   start dates returned StartDateError and render_xblock converted it to
   a 404. Grant load access when the course is public and the waffle is
   enabled.
3. _has_access_to_block.can_load had the same gap at the block level,
   causing blocks with inherited future start dates to 404 even after
   the course-level check passed. Mirror the public-access bypass at
   the block level, keyed off the CourseOverview.

Gating in all three sites reuses check_public_access, so the existing
COURSE_ENABLE_UNENROLLED_ACCESS_FLAG + COURSE_VISIBILITY_PUBLIC contract
continues to govern who sees what. Authenticated users, masquerading
staff, and non-public courses are unaffected.

Closes openedx#38019
@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

Thanks for the pull request, @kingoftech-v01!

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
🔘 Submit a signed contributor agreement (CLA)

⚠️ We ask all contributors to the Open edX project to submit a signed contributor agreement or indicate their institutional affiliation.
Please see the CONTRIBUTING file for more information.

If you've signed an agreement in the past, you may need to re-sign.
See The New Home of the Open edX Codebase for details.

Once you've signed the CLA, please allow 1 business day for it to be processed.
After this time, you can re-run the CLA check by adding a comment below that you have signed it.
If the CLA check continues to fail, you can tag the @openedx/cla-problems team in a comment for further assistance.

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

@kingoftech-v01
Copy link
Copy Markdown
Author

CLA signed via DocuSign. Re-triggering the check.

Other checklist items:

  • Product approval: not required — bug/security fix, no new feature or product surface change.
  • Context: full intent analysis, fix scope, test plan, and refs are in the PR description.
  • Green build: will run once the CLA gate unblocks CI.

@openedx/wg-maintenance-openedx-platform — marking ready for engineering review when you have capacity. Thanks!

@github-project-automation github-project-automation bot moved this from Needs Triage to Done in Contributions Apr 10, 2026
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: Done

Development

Successfully merging this pull request may close these issues.

3 participants