[Building Sakai] LTI Producer

[Adrian Fish]

Hi Steve,

> Hi Adrian,
>
> First up, do you have the same users in both Moodle and Sakai? If so, activate the highly trusted consumers option. This will allow the user and site details to pass through without being namespaced and then you can re-use existing sites, data and config. This is what we do to embed Sakai tools inside uPortal. So a user can get the wiki from one of their sites that they have been working on in Sakai.

Same users but not the same course modules; some will be run on Moodle, 
some on Sakai.
> Without this, the userid will be prefixed (they get a new account, but they can't login to it via Sakai, only via Basic LTI. A new site and new tool is also created. Not ideal if you want to reuse data.
>
> For roles, if you are using the trusted consumer option, then the roles are ignored and it proceeds based on what role you have in the site. If not, then it gets it from the "roles" request param. Of course, that role needs to exist in the Sakai site (though there is some allowance for the instructor or student roles). I am just about to do some work so that you can map IMS roles to Sakai roles, via sakai.props, so it isn't as rigid:https://jira.sakaiproject.org/browse/BLTI-151
I was thinking along just those lines, so great. I think we want the 
auto generation of sites in Sakai to happen for the reason above, so a 
way of mapping lti roles to Sakai ones would be a piece of the puzzle. 
If I setup the project site template with the permissions I need it 
should all just work once the roles are mapped. Is that correct?


Thanks for getting back, that's priceless info.

Cheers,
Adrian.
>
> On 15/02/2012, at 2:49 AM, Adrian Fish wrote:
>
>> Does anybody know how the LTI producer works?
>>
>> I'm trying to get the signup tool working in Moodle and it gives me
>> this: 'Not allowed to access tool'. When I actually think about what is
>> happening this makes sense in the case of site dependent tools. How does
>> the producer portlet interpret the roles passed in the launch request,
>> before it passes the request onto the tool? How does the portlet make
>> use of the context_id param? How is the target tool supposed to apply
>> permissions without prior configuration?
>>
>> Is there anything special that needs doing before a tool is 'exportable'
>> through the LTI producer?
>>
>> Any pointers well appreciated!
>>
>> Cheers,
>> Adrian.
>>
>> -- 
>> ==================================
>> Adrian Fish
>> Software Engineer
>> B66 Management School
>> Lancaster University
>> Lancaster
>> LA1 4YW
>>
>> http://www.sakaiproject.org
>> http://confluence.sakaiproject.org/display/YAFT/Yaft
>> http://confluence.sakaiproject.org/display/CLOG/Home
>> http://confluence.sakaiproject.org/display/BBB/Home
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email tosakai-dev-unsubscribe at collab.sakaiproject.org  with a subject of "unsubscribe"

-- 
==================================
Adrian Fish
Software Engineer
B66 Management School
Lancaster University
Lancaster
LA1 4YW

http://www.sakaiproject.org
http://confluence.sakaiproject.org/display/YAFT/Yaft
http://confluence.sakaiproject.org/display/CLOG/Home
http://confluence.sakaiproject.org/display/BBB/Home