doc/lti/10_example_tools.md
Here is a sample list of some of the LTI tools that exist in the Canvas ecosystem. Most of these are reference tools, used for testing, and directions for testing using these tools are found here
This tool is extremely simple but allows you to configure any placements you need. It displays launch parameters and allows the passing back of Content Items, both File-type and LtiLink-type. In addition, this tool also has a bare-bones 1.3 implementation to facilitate testing the 1.1 -> 1.3 migration process. More details on the 1.3 side of this tool are found on its home page and in the 1.3 section below.
Installation instructions are found on the tool's home page, and it's also possible to run and develop this locally following the instructions in the README.
This is a very simple tool that allows you to test 1.1 Grade Passback (also called Basic Outcomes). Manipulating the XML that gets passed from the tool to Canvas is also very easy.
Installation instructions are found in the repository's README file, and should still work with only a couple of small changes:
-rubygems from the start up commandThis tool is suitable for testing 1.1 launches from pretty much everywhere, and displays the parameters it was given on launch. It is a legacy app and lives in Weston Dransfield's Heroku account. Note that this is also a functioning LTI 2.0 tool!
Note that this tool is currently not functioning, since its ruby version is too old to run on ARM computers, and the Ruby 2.6 Heroku runtime is EOL. It's possible to run this locally, but not if you have an ARM chip. This tool is still listed here since it is helpful to have, but it's not recommended to use.
Other 1.1 tools in the Canvas ecosystem:
This tool is capable of testing 1.3 launches from all supported placements, and also supports all AGS actions (the 1.3 equivalent of Grade Passback). The README has instructions on how to configure Canvas to talk to this tool. This tool also supports multiple configurations within the same installation, which can be helpful for different types of testing.
This is a deployed-to-production tool that has a fairly simple Ruby implementation, and has been used as a reference for other internally-developed 1.3 tools. Note that it has other dependencies for it to fully work locally, but can be installed as a standalone way to test 1.3 launches.
This tool is extremely simple and was originally only a 1.1 tool. It now includes a 1.3 implementation to facilitate the testing of the 1.1 -> 1.3 migration process.
Locally, this tool can be configured to run against your local Canvas by editing the .env file. In production, there currently only exists one (1) registration/developer key for this tool, in Site Admin. To install this tool in your sandbox or other contexts, follow the instructions on the tool's home page linked above.
Other 1.3 tools in the Canvas ecosystem:
This tool is suitable for testing 2.0 launches from pretty much everywhere, and displays the parameters it was given on launch. It is a legacy app and lives in Weston Dransfield's Heroku account. Note that this is also a functioning LTI 1.1 tool! It is also totally possible to set this up locally, following the instructions in the README. The home page has a registration link for pasting into Canvas.
Note that this tool is currently not functioning, since its ruby version is too old to run on ARM computers, and the Ruby 2.6 Heroku runtime is EOL. It's possible to run this locally, but not if you have an ARM chip. This tool is still listed here since it is helpful to have, but it's not recommended to use.
This tool is particularly helpful when testing or troubleshooting the Plagiarism Detection Platform. The README has adequate instructions for setting it up.
About the only current use case for LTI 2.0 tools is the Plagiarism Platform, which is used by external tool providers like TurnItIn.