openedx / openedx/openedx-platform
[Course Live] Saving an LTI 1.1 configuration returns HTTP 500 in Studio
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.2k
- Forks
- 4.4k
- Avg merge
- 6d 18h
- Merged PRs (30d)
- 42
Description
Saving an LTI 1.1 configuration under Studio → Content → Pages & Resources → Live fails with:
We couldn't apply your changes.
Please check your entries and try again.
The underlying Studio APIs return HTTP 500.
Environment
- Open edX release line:
master - Site:
master.openedx.io - Course:
course-v1:OpenedX+CS51+2026 - LTI version: LTI 1.1
- Observed: July 31, 2026
Steps to reproduce
- Open a course in Studio.
- Go to Content → Pages & Resources.
- Open the Live settings.
- Select a provider.
- Enter the LTI 1.1 credentials and required configuration fields.
- Select Save.
Expected behavior
The Course Live configuration is saved successfully.
Actual behavior
Studio displays:
We couldn't apply your changes.
Please check your entries and try again.
A browser HAR captured the following failures:
2026-07-31T11:24:57.415Z
PATCH /api/course_apps/v1/apps/course-v1:OpenedX+CS51+2026
HTTP 500
2026-07-31T11:25:16.542Z
POST /api/course_live/course/course-v1:OpenedX+CS51+2026/
HTTP 500
2026-07-31T11:25:32.918Z
POST /api/course_live/course/course-v1:OpenedX+CS51+2026/
HTTP 500
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the save flow in Studio using the listed course and LTI 1.1 settings, then inspect the handlers for PATCH /api/course_apps/v1/apps/{course_id} and POST /api/course_live/course/{course_id}/. Done means both APIs return success and Studio saves the Course Live configuration without displaying the HTTP 500 error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100