[Building Sakai] Looking for tutorial/example of using LTI in Sakai for login to separate website

[Paul Dickson]

Steve, Charles, I'm going to try to answer your questions together so that
you guys don't have to worry about answering something the other already
has.

I believe the total questions are these three:
(a) What software is the web server running and what language?  Is it just
flat files in Apache?  Is there some PHP/Java glue?
The app is written in node.js/javascript. Node.js has several robust OAuth
libraries (passport is the most notable) which can be used to authenticate
using OAuth (v1 or v2) which I think is what you were talking about Steve.

(b) Do you limit viewing to any class any student or do you maintain
per-class access control lists?
Any student in a class can view any recording from that class and that
class only. (So if a student is in section 1 of intro programming they can
only view the videos of section 1 of intro programming.)

(c) Do you control the software that uploads the recordings (i.e. like
which directory things are put in?)
We have complete control of where all files go. All software was written in
house and runs on Ubuntu 14.

Thanks for responding so quickly to my queries, it's taken me a little
while to get back with details as this part of the lecture recording
process is being developed at another institution. They have the web side
of development but since they don't use Sakai I'm trying to figure out how
to integrate the web server they have developed into our campus (and my
server side web background is limited). So again thanks and any pointers to
the right places to start finding examples or tutorials to look at would be
much appreciated.

pd



On Tue, Jul 15, 2014 at 2:44 AM, Steve Swinsburg <steve.swinsburg at gmail.com>
wrote:

> Hi Paul,
>
> Basically you are going to need to create an LTI provider on the
> recordings site that can accept an LTI request (which will come from Sakai)
> and process it accordingly. This can be as simple as a servlet that does
> the work in checking the request is valid (using the OAuth libraries),
> extracting the bits you need (username, siteid, that could be it), setting
> up the session for the user, then redirecting to the appropriate page. What
> is the external app written in?
>
> On the Sakai side you would then take those details and setup an external
> tool to launch to your site. That is the simple part :)
>
> Let me know the above info and I can point you in the right direction.
>
> cheers,
> Steve
>
>
> On Tue, Jul 15, 2014 at 9:45 AM, Paul Dickson <pdickson at ithaca.edu> wrote:
>
>> Sorry, I was trying to not overwhelm with details, obviously I went to
>> far.
>>
>> We have an in house lecture recording system that currently runs in one
>> of our classrooms. Every lecture given during the semester is automatically
>> uploaded to a web server. Our legal departments interpretation of FERPA
>> requires that only students enrolled in a course may view the recorded
>> lectures from that course. (the recordings include index material, videos,
>> stills of whiteboard and computer material, etc which would be to hard to
>> automate putting into Sakai).
>>
>> Our current solution (running at the one of our collaborators
>> universities) has been to have roster information sent to the web server
>> once a day and the access privileges of all student updated so that they
>> only have access to the presentation of the courses they are in but this
>> requires students to set up yet another account. I am hoping to have our
>> students log into Sakai and be able to follow a link from there that brings
>> them to our website and allows them to watch recorded class material for
>> only classes they are in. The web server would be configured to only allow
>> logins from Sakai. My hope is to be able to set this up in such a way that
>> the faculty members who are setting up their Sakai sites only need to add
>> something simple to their sites to enable them to link to our lecture
>> presentation server.
>>
>> So basically, I am hoping to get pointed in the right direction to learn
>> how to write the LTI bridge that would securely log students from Sakai to
>> our website from a single link press and sent over the class that they are
>> linking from so that our web server knows which lecture recordings they
>> have access to.
>>
>> I hope this is enough of a description and thanks.
>> pd
>>
>>
>> On Mon, Jul 14, 2014 at 6:13 PM, Charles Severance <csev at umich.edu>
>> wrote:
>>
>>> Paul,
>>>
>>> There is no off-the shelf software to do this.
>>>
>>> But it would not be hard to build.  Are you talking about a site that is
>>> wide open to anyone on campus or carefully constrained to a class?   Is
>>> this for one classes, many classes looking at all the same material, or
>>> many classes each looking at their own material?  Is this things like HTML
>>> and CSS, PDF, Video, Audio?  Who would build the site?   faculty members or
>>> technical staff?
>>>
>>> Will this be an uploaded static site or active content like PHP scripts?
>>>
>>> Sorry for so many questions - your description isa little too wide-open.
>>>
>>> /Chuck
>>>
>>> On Jul 14, 2014, at 2:01 PM, Paul Dickson <pdickson at ithaca.edu> wrote:
>>>
>>>  I was hoping to get direction to any existing information about using
>>> LTI within Sakai for login to a separate website. The problem I am trying
>>> to solve is that we have some web content that should only be accessible to
>>> students within a given class but that cannot be directly put into Sakai. I
>>> would like to essentially use Sakai as the login method for this separate
>>> site. I have seen that it is possible to do this by adding the LTI bridge
>>> as a tool and putting the 3 basic pieces of information (secret etc). What
>>> I cannot seem to find is any explanation of how to do this which is up to
>>> date. Every site related to this looks to be from 2012 and none of the
>>> examples work.
>>>
>>> So is there any chance that someone who is helping to develop Sakai
>>> might know of where I can find information for configuring this? I'd seen
>>> that it is easy to drop the Sakai portion in but can't find any examples of
>>> what goes into the other website to make the hand shake.
>>>
>>> Thanks a lot in advance.
>>> pd
>>> _______________________________________________
>>> 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"
>>>
>>>
>>>
>>
>> _______________________________________________
>> 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"
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140717/7007f19e/attachment.html