feat: new event to track LTI Launches via LTI Provider

[xitij2000]

Description

Triggers the new LTI_PROVIDER_LAUNCH_SUCCESS on successful launch as LTI provider.

The new event is added in: openedx/openedx-events#501

Supporting information

NA

Testing instructions

The easiest is to use the automated tests.

Here are the steps for manual testing:

• Enable the LTI provider functionality by setting ENABLE_LTI_PROVIDER: true in features. You can do that with the following tutor snippet

   hooks.Filters.ENV_PATCHES.add_item(("lms-env-features", 'ENABLE_LTI_PROVIDER: true'))

• We need an LTI embed URL to launch to. Here is one you can use for the demo course: http://local.openedx.io:8000/lti_provider/courses/course-v1:OpenedX+DemoX+DemoCourse/block-v1:OpenedX+DemoX+DemoCourse+type@sequential+block@4e1de5e13fc3422997fe246b40a43aa1
• We will use the saLTIre testing tool for LTI.
  • Visit that site and click on "Security Model" from the sidebar.
  • Fill in the above launch URL
  • Create a new LTI consumer via http://local.openedx.io:8000/admin/lti_provider/lticonsumer/
  • You can either use the credentials from the tool here or copy over the consumer key and shared secret to the tool.
  • Click save.
• You can launch using Connect, but to test the signal we need to have a handler registered.
• You can create a simple signal handler as follows:

  from openedx_events.learning.signals import LTI_PROVIDER_LAUNCH_SUCCESS
  LTI_PROVIDER_LAUNCH_SUCCESS.connect(lambda launch_data, **kwargs: print(f"{launch_data=}"))

  This can be put in any file imported by the platform, so the signal handler gets registered.
• Click connect and check the logs, you should see a record of the launch.

Deadline

"None"

Other information

A client would like to track LTI launches and would like to hook into the launch pipeline.

[openedx-webhooks]

Thanks for the pull request, @xitij2000!

This repository is currently maintained by @openedx/wg-maintenance-edx-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:

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

[tecoholic]

@xitij2000 👍

• I tested this: Test this along with openedx/openedx-events#501 and open-craft/platform-plugin-lti-launch-monitor#1 and verified that the events are generated and consumed as expected.
• I read through the code
• I checked for accessibility issues
• Includes documentation

NOTE: This requires merging openedx/openedx-events#501 and updating requirements file before merging.

[xitij2000]

@farhaanbukhsh Could you have a look at this PR.

[farhaanbukhsh]

I have added a few questions about the code.

[farhaanbukhsh]

👍

• ✅ I tested this with the testing instructions
• ✅ I read through the code
• ❌ I checked for accessibility issues
• ❌ Includes documentation

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX production environment.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX production environment.