LTI Customer key

LTI Customer key

by Sand ipm -
Number of replies: 3

Hello,

I am using the LTI method for the first time, and I am stock ! I hope that someone can help me. I checked the moodle guide https://docs.moodle.org/311/en/Publish_as_LTI_tool and it says "You will also need to give the LTI consumer site a consumer key - this can be anything you want."

I cannot find where I generate the customer key ? As far as i understand, I can make it up myself, but where do I write it down ? 

Thank you so much for your help,


Average of ratings: -
In reply to Sand ipm

Re: LTI Customer key

by Jake Dallimore -
Picture of Core developers Picture of Moodle HQ Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers Picture of Testers
Hi,

You're right, the consumer key can be anything you like. You need to enter it in the tool settings in the consumer site. The first time the tool is launched, the provider will store information about the consumer, including the key you've used.

I will point out that there are implications to using different consumer keys across different tools on the consumer site, however. Because the Moodle provider code uses the consumer key in generating unique identifiers for user accounts, using different consumer keys can result in two user accounts being created on the provider, for the same user on the consumer site. This would occur if the same user launched two tools on the consumer using different consumer keys (i.e each tool is set up to use a different consumer key). If your use case is a single organisation using the tool(s), you probably want to just pick a key and stick with it, making sure that all launches a given user will result in that same account being reused on the provider site.

Hope that helps
Jake
In reply to Jake Dallimore

Re: LTI Customer key

by Sand ipm -
hello,
thank you so much for your answer, I think that explains why there are so many accounts being created for one single user.
I also have an issue with a module inside a module (external tools) being seen as an "abymed" window (a window in a window in a window) would you know why this is happening ?
Thank you so much