Moodle in English: Basiclti.xml authentication approach

LTI and Moodle

Basiclti.xml authentication approach

This discussion has been locked because a year has elapsed since the last post. Please start a new discussion topic.

Basiclti.xml authentication approach

by Shail Jai - Friday, May 12, 2017, 1:39 PM

Hello Friends,

I created one common cartridge package with BLTI module.

My assumption is that when client import CC package in his/her LMS platform, then everything should get import including authorisation key. There should not be any manual intervention.

As per online documentation and sample; in my basiclti.xml file I put all three parameters

1. launch url 2 consumer key (guid) 3 secret key, but when I import my package in moodle, except guid & secret key everything gets imported. I also checked this package with canvas and I am facing same problem there.

Herewith I am also attaching my sample package. Please help me to look into right direction.

Re: Basiclti.xml authentication approach

by Shail Jai - Tuesday, May 16, 2017, 12:55 PM

Interesting, it seems no one has clue.

Average of ratings: -

Re: Basiclti.xml authentication approach

by John Okely - Tuesday, May 16, 2017, 1:40 PM

I'm not sure what you used to create it, but it does not look like an XML file to me.

Perhaps copy paste the xml here.

Average of ratings: -

Re: Basiclti.xml authentication approach

by Shail Jai - Tuesday, May 16, 2017, 2:30 PM

Hi John,

sorry, I just realise that attachment is not in xml format.

Here is the sample code.

<?xml version="1.0" encoding="UTF-8"?>

<cartridge_basiclti_link xmlns="http://www.imsglobal.org/xsd/imslticc_v1p0"

xmlns:blti = "http://www.imsglobal.org/xsd/imsbasiclti_v1p0"

xmlns:lticm ="http://www.imsglobal.org/xsd/imslticm_v1p0"

xmlns:lticp ="http://www.imsglobal.org/xsd/imslticp_v1p0"

xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation = "http://www.imsglobal.org/xsd/imslticc_v1p0 http://www.imsglobal.org/xsd/lti/ltiv1p0/imslticc_v1p0.xsd

http://www.imsglobal.org/xsd/imsbasiclti_v1p0 http://www.imsglobal.org/xsd/lti/ltiv1p0/imsbasiclti_v1p0.xsd

http://www.imsglobal.org/xsd/imslticm_v1p0 http://www.imsglobal.org/xsd/lti/ltiv1p0/imslticm_v1p0.xsd

http://www.imsglobal.org/xsd/imslticp_v1p0 http://www.imsglobal.org/xsd/lti/ltiv1p0/imslticp_v1p0.xsd">

<blti:title>LMS</blti:title>

<blti:description>moodle test</blti:description>

<blti:icon></blti:icon>

<blti:launch_url>http://example.com/test</blti:launch_url>;

<blti:custom>

<lticm:property name="guid">12345</lticm:property>

<lticm:property name="secret">abc123456</lticm:property>

</blti:custom>

<cartridge_bundle identifierref="BLTI001_Bundle"/>

<cartridge_icon identifierref="BLTI001_Icon"/>

</cartridge_basiclti_link>

Average of ratings: -

Re: Basiclti.xml authentication approach

by John Okely - Tuesday, May 16, 2017, 3:41 PM

Basic LTI is designed to allow you to configure a tool, but the consumer key and secret should be kept private.

This is because the cartridge should be public. If your key is also public, it defeats the purpose of the key.

https://www.imsglobal.org/specs/ltiv1p0/implementation-guide#toc-5

This should explain why moodle and canvas both ignore it when you include it.

But I'm interested to know if there's somewhere in the ims documentation that says it should be included in the cartridge.

Average of ratings: -