[Building Sakai] Basic LTI tool registration settings being lost

Joshua Swink joshua.swink at gmail.com
Fri Aug 17 12:19:55 PDT 2012


Thanks for the help. I changed the settings accordingly, but it didn't have
any effect.

My best guess now is that after the registration is first read, no changes
to the file will be picked up. I tested this as follows:

* Change change imsti.pagetitle to "SomeOtherName" in IMSBLTIPortlet.xml
* Restart Sakai
* Add the tool to a new site

result: The page title used is the old one, from before I changed
IMSBLTIPortlet.xml.

Then I changed the tool ID instead. After restarting Sakai, I added the
tool and this time the changed values were in effect.

Then I changed the tool ID back to the original one yet again
("sakai.piazza"). I restarted Sakai and added this tool to another site,
and again the values it used were from the very first time that the tool
had been read from IMSBLTIPortlet.xml.

Josh

On Fri, Aug 17, 2012 at 5:32 AM, Savitha Prakash <savithap at umich.edu> wrote:

> Hi Joshua,
>
> Some of the things that stands out from your settings are for releaseemail
> and releasename. The value for it should be on/off and not true/false.
> Below are the settings we have for Piazza, that works for us. We are
> running Sakai-2.7.2.
>
> - Savitha
>
>
> <tool
> 235              id="sakai.piazza"
> 236              title="Piazza"
> 237              description="For students to ask and answer questions
> under the guidance of their instructor ">
> 238
> 239              <configuration name="sakai:portlet-pre-render"
> value="true" />
> 240
> 241              <category name="course" />
> 242              <category name="project" />
> 243              <category name="portfolio" />
> 244
> 245              <configuration name="functions.require" />
> 246
> 247              <configuration name="imsti.launch" value="*****" />
> 248              <configuration name="imsti.secret" value="*****" />
> 249              <configuration name="imsti.key" value="*****" />
> 250              <configuration name="imsti.pagetitle" value="Piazza"/>
> 251              <configuration name="imsti.tooltitle" value="Piazza"/>
> 252              <configuration name="imsti.releaseemail" value="on" />
> 253              <configuration name="imsti.releasename" value="on" />
> 254              <configuration name="imsti.custom"/>
> 255              <configuration name="imsti.xml"/>
> 256              <configuration name="imsti.debug"/>
> 257
> 258              <configuration name="final.launch" value="true"/>
> 259              <configuration name="final.secret" value="true"/>
> 260              <configuration name="final.key" value="true"/>
> 261              <configuration name="final.pagetitle" value="false"/>
> 262              <configuration name="final.tooltitle" value="false"/>
> 263              <configuration name="final.releaseemail" value="true" />
> 264              <configuration name="final.releasename" value="true" />
> 265              <configuration name="final.custom" value="true"/>
> 266              <configuration name="final.xml" value="true"/>
> 267              <configuration name="final.debug" value="true"/>
> 268
> 269            </tool>
>
>
> On Thu, Aug 16, 2012 at 8:30 PM, Joshua Swink <joshua.swink at gmail.com>wrote:
>
>> I'm defining a 'virtual tool' using Basic LTI. Its purpose is to access
>> Piazza (https://piazza.com/).
>>
>> I am seeing a problem in that some of the configuration values do not
>> make it to the tool that gets placed in a site. I see the following
>> sequence of events:
>>
>> * I added a new <tool> section to
>> ${sakai.home}/portlets/imsblti/IMSBLTIPortlet.xml with values that define
>> the virtual Piazza tool
>> * An instructor goes to Site Editor, Edit Tools, and adds this Piazza
>> tool to a course site
>> * The instantiated Piazza tool has enough info to connect to Piazza (such
>> as imsti.secret and imsti.key) but several other settings are missing (such
>> as imsti.pagetitle and imsti.releasename)
>>
>> Should these values make it to the final, instantiated tool? If so, is
>> there another way to get them there or is this a bug?
>>
>> I am using Sakai 2.7.1.
>>
>> The tool registration is:
>>
>>     <tool id="sakai.piazza" title="Piazza" description="Piazza
>> Collaboration Tool">
>>         <configuration name="sakai:portlet-pre-render" value="true" />
>>         <category name="course" />
>>         <category name="project" />
>>         <category name="portfolio" />
>>         <configuration name="functions.require" />
>>         <configuration name="imsti.launch" value="
>> https://piazza.com/basic_lti" />
>>         <configuration name="imsti.xml" />
>>         <configuration name="imsti.secret" value="XXXXXXXXXXXXXX" />
>>         <configuration name="imsti.key" value="ucmerced.edu" />
>>         <configuration name="imsti.pagetitle" value="ThePageTitle" />
>>         <configuration name="imsti.tooltitle" value="TheToolTitle" />
>>         <configuration name="imsti.newwindow"/>
>>         <configuration name="imsti.frameheight" />
>>         <configuration name="imsti.debug" value="true" />
>>         <configuration name="imsti.releasename" value="true" />
>>         <configuration name="imsti.releaseemail" value="true" />
>>         <configuration name="imsti.custom"/>
>>         <configuration name="allowMultipleInstances" value="false"/>
>>         <configuration name="final.launch" value="true"/>
>>         <configuration name="final.xml" value="true"/>
>>         <configuration name="final.secret" value="true"/>
>>         <configuration name="final.key" value="true"/>
>>         <configuration name="final.pagetitle" value="false"/>
>>         <configuration name="final.tooltitle" value="false"/>
>>         <configuration name="final.newwindow" value="false"/>
>>         <configuration name="final.frameheight" value="false"/>
>>         <configuration name="final.debug" value="false"/>
>>         <configuration name="final.releasename" value="true"/>
>>         <configuration name="final.releaseemail" value="true"/>
>>         <configuration name="final.custom" value="false"/>
>>     </tool>
>>
>>
>> The debug values are:
>>
>> *BasicLTI Endpoint*https://piazza.com/basic_lti
>> *BasicLTI Parameters:*
>> user_id=ccain
>> lis_course_offering_sourced_id=201220-20010-BIO-110-01
>> context_id=201220-20010-BIO-110-01
>> context_title=SU12-BIO 110 01
>> oauth_signature=+611U2BjRo0CuQ4oJ9Xy4iee7JU=
>> oauth_nonce=5542927403601402
>> lti_message_type=basic-lti-launch-request
>> resource_link_id=30b09f95-a85f-4a6b-aa04-bab7e4b361f0
>> ext_sakai_serverid=ucmcropst2
>> roles=Instructor
>> oauth_signature_method=HMAC-SHA1
>> oauth_callback=about:blank
>> context_label=SU12-BIO 110 01
>> basiclti_submit=Press to continue to external tool.
>> launch_presentation_locale=en_US
>> ext_sakai_server=http://cropstest.ucmerced.edu
>> ext_sakai_session=0dfbfa37fc38d9978e443aa599c6b543b223a5d91ae231f7426cb6a0468f8e31e4d0ea8c092a0e9e
>> oauth_timestamp=1345163011
>> context_type=CourseOffering
>> lti_version=LTI-1p0
>> oauth_version=1.0
>> oauth_consumer_key=ucmerced.edu
>>
>> Josh
>>
>>
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> "unsubscribe"
>>
>
>
>
> --
> *Savitha Prakash  *
> Application Analyst
> ITS Teaching & Learning
> University of Michigan
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20120817/32865135/attachment.html 


More information about the sakai-dev mailing list