Found this content helpful? Log in or sign up to leave a like!
Common Cartridge Import - Link Matching Logic
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am a developer working on creating a thin common cartridge and importing LTI 1.3 links using the TCC into Canvas using the Import tool. However, when doing so, I am struggling to get the launch urls contained in the common cartridge to match to the external tool (LTI 1.3) I have installed (I have a domain set for the developer key and this domain matches the domains of the launch links). I am trying to find out what the matching criteria is for a TCC imported LTI link and if it is supposed to be different than the matching criteria for a manually created activity/assignment.
So far, this is what I have noticed:
- Only the Target Link URI set on the developer key is used to find a matching key, when importing a LTI link through TCC. I was expecting the domain to be used to match as well, if no matches were found using the target link URI
- After importing the TCC, when trying to open the imported content, initially Canvas displays a message saying no external tool was found for the created LTI link. If i then delete the external app that was created during the import for the LTI links, and try opening the content again, Canvas successfully matches the links to my external app. Some of these LTI links could only have matched to the domain.
Based on the above, it seems like Canvas seems to only use target link when trying to match to an external app during the TCC import process but otherwise uses the target link AND domain to match links.
