Hi,
I'm working on developing an external tool for Moodle that is authenticated using LTI. I currently have authentication working properly on clicking the link in Moodle to my external tool. During the sign in, Moodle passes the parameter lis_result_sourcedid, which looks something like this:
{"instanceid":"1","userid":"5","typeid":"1","launchid":740494135},"hash":"500124560eba26b6673d07f04c61ccc3ba6861f874d439b60d378ea7b798ac1d"}
Then, later, when I'm attempting to pass grades back, I need to pass back a sourcedid parameter in my LTI xml. Am I supposed to pass all of this?
Or just the launchid or something like that? I haven't been able to find any clear answers about what's supposed to be passed back through LTI as LTI's documentation has been pretty hard to find.
If you are a member of IMS you may get more help there than here. But let's see if I can help.
For reference, here is what moodle passes back in its provider.
716c919df5a065dd7a3fc5702544d33a:::115:::249:::{"data":{"instanceid":"3","userid":"249","launchid":180548532},"hash":"290ab06bcf0ed944243b530718bdad0d33277884842e3f304cfb95c56c91b752"}Here is what the test tool provider passes back.
716c919df5a065dd7a3fc5702544d33a:::S3294476:::29123:::dyJ86SiwwA9
Here is the documentation, although you might have already found it http://www.imsglobal.org/specs/ltiv1p1/implementation-guide#toc-17
Hi Will - fwiw, in our tool we are passing back that entire sourcedid and it works (which you have likely discovered by now). I was surprised that the sourcedid had this much info and changed on every launch, and still haven't quite figured out if we can always just send back a score for the latest one of these for a particular student.
lis_result_sourcedid=83873872987329873264783687634
This field contains an identifier that indicates the LIS Result Identifier (if any) associated with this launch. This field identifies a unique row and column within the TC gradebook. This field is unique for every combination of resource_link_id / user_id. This value may change for a particular resource_link_id / user_id from one launch to the next. The TP should only retain the most recent value for this field for a particular resource_link_id / user_id. This field is optional.