<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Hi Simon<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>thanks for the screenshots - very useful. All working well now! :-)<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I had added the /lti/ when configuring via admin > plugins > activity modules > external tool but I hadn't added a url or a url with /lti/ in the end when adding an external tool activity to a course. Now that I've done that it works great. It seems a shame that the Moodle settings can't automatically pick up the correct url by selecting the name of the external tool. e.g. If I select XOT as shown in the screenshot (the name I gave to the external tool via admin) I still have to add the url with /lti/ appended for the selection of an LO to work otherwise it just takes me to the standard login screen. Not a problem for me but I can see it being a problem where users just put what they know to be the installation url, or no url at all, rather than knowing or remembering to add /lti/. I know this is more a moodle limitation rather than any kind of limitation of what you've developed which is great! <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I guess once users know what to do via a guide or something then they should remember and I guess in an institution it would be worth customising the help for the external resource activity to show what url to add.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I can see awareness of LTI growing quickly over the next couple of years especially where Moodle is used as the VLE. Does the functionality exist in what you have developed to automatically create accounts from the consumer e.g. if the XOT db was used to store accounts? I'm guessing not at the moment but I could see that being very useful for OER collaborative projects etc.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Great stuff!<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>In my new features slot on the 10th ok if I mention this and suggest delegates speak to you if they have any questions?<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Cheers<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Ron<o:p></o:p></span></p><p class=MsoNormal><a name="_MailEndCompose"><span style='color:#1F497D'><o:p> </o:p></span></a></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> xerte-dev-bounces@lists.nottingham.ac.uk [mailto:xerte-dev-bounces@lists.nottingham.ac.uk] <b>On Behalf Of </b>Simon Atack<br><b>Sent:</b> 03 October 2012 11:08<br><b>To:</b> For Xerte technical developers<br><b>Subject:</b> [Xerte-dev] Re: LTI Provider<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'>Ron,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Sorry about not mentioning to run upgrade.php I assumed (wrongly!) that standard practice would be to run each time when upgrading code.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>It should work with all the authentication methods, I had only used it against LDAP. I have just switched to static as authentication and gone through it and it appears to work as Id expect. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>The steps will be (I have attached screen grabs to compare to)<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>1<sup>st</sup> you should get a login asking for username/password ( this will only appear once) [Xerte-lti-1.png]<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>2<sup>nd</sup> you should get a screen with instructions on the left and list of projects in the right with a select button at the bottom [Xerte-lti-2.png] an empty workspace & [Xerte-lti-3.png] for workspace with some content.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>The obvious thing I can think of is you didn’t put the correct url into the Tool Base URL, it should be the usual Xerte url with the addition of /LTI/ on the end as only this URL is configured to accept the LTI link <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Simon<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a href="mailto:xerte-dev-bounces@lists.nottingham.ac.uk">xerte-dev-bounces@lists.nottingham.ac.uk</a> [<a href="mailto:xerte-dev-bounces@lists.nottingham.ac.uk">mailto:xerte-dev-bounces@lists.nottingham.ac.uk</a>] <b>On Behalf Of </b>Ron Mitchell<br><b>Sent:</b> 03 October 2012 10:10<br><b>To:</b> 'For Xerte technical developers'<br><b>Subject:</b> [Xerte-dev] Re: LTI Provider<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'>Hi Simon<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>thought I'd have a go at testing this for you but may be misunderstanding how it works. Firstly will it only work with XOT configured for LDAP or should it also work if XOT is set to static authentication?<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Results of tests so far:<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>1. Realised I had to run upgrade.php to create the lti table - this worked fine.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>2. Adding a key and secret via management.php also worked fine.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>3. Configuring the Moodle external tool via admin > manage plugins etc also worked fine <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>4. Adding an external tool activity to a course and selecting save and display simply launches the XOT login page and upon login shows the workspace e.g. there isn't an option to select a specific LO for the link. Is this because it won't work with static authentication or am I missing something?<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>HTH<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Ron<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a href="mailto:xerte-dev-bounces@lists.nottingham.ac.uk">xerte-dev-bounces@lists.nottingham.ac.uk</a> [<a href="mailto:xerte-dev-bounces@lists.nottingham.ac.uk">mailto:xerte-dev-bounces@lists.nottingham.ac.uk</a>] <b>On Behalf Of </b>Simon Atack<br><b>Sent:</b> 02 October 2012 17:14<br><b>To:</b> <a href="mailto:xerte-dev@lists.nottingham.ac.uk">xerte-dev@lists.nottingham.ac.uk</a><br><b>Subject:</b> [Xerte-dev] LTI Provider<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>First thank you all for the welcome.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Yesterday I submitted to svn the LTI Provider integration function I have been working on. This allow you to have launch Xerte from within a VLE giving single sign on etc (In moodle this is the External Tool activity plugin). <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It handles the association between the LTI userid & the Xerte username (and allows regular re-authentication) and then if staff lets you select the project you want to associate the link with, and then displays the project for subsequent launches of the link. It also includes LTI Key/Secret Management in the main Xerte management interface.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have tested it myself on my local box with a fresh install of Xerte (configured for LDAP authentication) and Moodle 2.2.2+. I have tried to keep the changes as few as possible to integrate it in (I have extended a couple of functions to support extra parameters as well as factoring some repeated lines into functions so there is only 1 copy doing anything). It would be really useful if others could download it, test it out and give feedback. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>There is a very brief documentation file LTI Documentation.txt included with a brief note of what you need to do, anyone having problems/or trouble understanding how to get it working please get it touch.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The LTI library is based off the IMS sample code for LTI in php and extended by UoN and has been used in the Rogo OSS project.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Simon<o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p> </o:p></span></p><p>This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. <o:p></o:p></p><p>This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. <o:p></o:p></p></div></body></html>