We’re using sakai 2.9.3 with BasicLTI 2.1.2. I don’t know how to get the XML returned to webpa, but I’ve add this to sakai.properties: log.config.count = 1 log.config.1 = DEBUG.org.sakaiproject.blti I can’t see much about groups in the output I get when I sync the users: 2015-05-12 14:23:46,634 DEBUG http-bio-8080-exec-6 org.sakaiproject.blti.ServiceServlet - Basic LTI Service request from IP=150.237.170.02 2015-05-12 14:23:46,634 DEBUG http-bio-8080-exec-6 org.sakaiproject.blti.ServiceServlet - oauth_version:1.0 2015-05-12 14:23:46,634 DEBUG http-bio-8080-exec-6 org.sakaiproject.blti.ServiceServlet - oauth_nonce:99425c36aa845236a7b5e13a9f311c6f 2015-05-12 14:23:46,634 DEBUG http-bio-8080-exec-6 org.sakaiproject.blti.ServiceServlet - oauth_timestamp:1431437016 2015-05-12 14:23:46,634 DEBUG http-bio-8080-exec-6 org.sakaiproject.blti.ServiceServlet - oauth_consumer_key:having_a_giraff 2015-05-12 14:23:46,634 DEBUG http-bio-8080-exec-6 org.sakaiproject.blti.ServiceServlet - id:33c2efb9931f3c3c6b30221239d0af8dbcf235ca07a983e76332dbf9945a85af:::admin:::d3c2a452-5cfa-4ca3-bf05-271e2ffea1d7 2015-05-12 14:23:46,652 DEBUG http-bio-8080-exec-6 org.sakaiproject.blti.ServiceServlet - lti_version:LTI-1p0 2015-05-12 14:23:46,652 DEBUG http-bio-8080-exec-6 org.sakaiproject.blti.ServiceServlet - lti_message_type:basic-lis-readmembershipsforcontextwithgroups 2015-05-12 14:23:46,652 DEBUG http-bio-8080-exec-6 org.sakaiproject.blti.ServiceServlet - oauth_signature_method:HMAC-SHA1 2015-05-12 14:23:46,652 DEBUG http-bio-8080-exec-6 org.sakaiproject.blti.ServiceServlet - oauth_signature:0BsJQf+fFgbPCMwNnMfA+/ZfBEY= 2015-05-12 14:23:46,668 INFO http-bio-8080-exec-6 org.sakaiproject.blti.ServiceServlet - Not a valid outcomes request: lti_message_type=basic-lis-readmembershipsforcontextwithgroups 2015-05-12 14:23:46,700 DEBUG http-bio-8080-exec-1 org.sakaiproject.blti.ServiceServlet - Basic LTI Service request from IP=150.237.170.02 2015-05-12 14:23:46,700 DEBUG http-bio-8080-exec-1 org.sakaiproject.blti.ServiceServlet - oauth_version:1.0 2015-05-12 14:23:46,700 DEBUG http-bio-8080-exec-1 org.sakaiproject.blti.ServiceServlet - oauth_nonce:2822f6834479b7166c60f070c224aaba 2015-05-12 14:23:46,700 DEBUG http-bio-8080-exec-1 org.sakaiproject.blti.ServiceServlet - oauth_timestamp:1431437016 2015-05-12 14:23:46,700 DEBUG http-bio-8080-exec-1 org.sakaiproject.blti.ServiceServlet - oauth_consumer_key:having_a_giraff 2015-05-12 14:23:46,700 DEBUG http-bio-8080-exec-1 org.sakaiproject.blti.ServiceServlet - id:33c2efb9931f3c3c6b30221239d0af8dbcf235ca07a983e76332dbf9945a85af:::admin:::d3c2a452-5cfa-4ca3-bf05-271e2ffea1d7 2015-05-12 14:23:46,700 DEBUG http-bio-8080-exec-1 org.sakaiproject.blti.ServiceServlet - lti_version:LTI-1p0 2015-05-12 14:23:46,700 DEBUG http-bio-8080-exec-1 org.sakaiproject.blti.ServiceServlet - lti_message_type:basic-lis-readmembershipsforcontext 2015-05-12 14:23:46,700 DEBUG http-bio-8080-exec-1 org.sakaiproject.blti.ServiceServlet - oauth_signature_method:HMAC-SHA1 2015-05-12 14:23:46,700 DEBUG http-bio-8080-exec-1 org.sakaiproject.blti.ServiceServlet - oauth_signature:RcPUR0LIALH26PdvmPsDJ6VNHEg= 2015-05-12 14:23:46,700 DEBUG http-bio-8080-exec-1 org.sakaiproject.blti.ServiceServlet - signature=33c2efb9931f3c3c6b30221239d0af8dbcf235ca07a983e76332dbf9945a85af 2015-05-12 14:23:46,700 DEBUG http-bio-8080-exec-1 org.sakaiproject.blti.ServiceServlet - user_id=admin 2015-05-12 14:23:46,700 DEBUG http-bio-8080-exec-1 org.sakaiproject.blti.ServiceServlet - placement_id=d3c2a452-5cfa-4ca3-bf05-271e2ffea1d7 2015-05-12 14:23:46,715 DEBUG http-bio-8080-exec-1 org.sakaiproject.blti.ServiceServlet - oauth_secret: k0LAgJ9Xp5KLxl2N9wC1UguSbpfMXU 2015-05-12 14:23:46,715 DEBUG http-bio-8080-exec-1 org.sakaiproject.blti.ServiceServlet - oauth_secret (decrypted): k0LAgJ9Xp5KLxl2N9wC1UguSbpfMXUz7 2015-05-12 14:23:46,715 DEBUG http-bio-8080-exec-1 org.sakaiproject.blti.ServiceServlet - Received signature=33c2efb9931f3c3c6b30221239d0af8dbcf235ca07a983e76332dbf9945a85af received=33c2efb9931f3c3c6b30221239d0af8dbcf235ca07a983e76332dbf9945a85af From: Adrian Fish [mailto:[log in to unmask]] Sent: 12 May 2015 13:00 To: [log in to unmask] Subject: Re: LTI with Sakai Groups do get returned - I just checked the Sakai code. Turn on debug logging for 'org.sakaiproject.blti' in your Sakai instance. The xml gets dumped to the log in debug mode, so you'll be able to see it in catalina.out. Does that make sense? Cheers, Adrian. On 12 May 2015 at 12:49, Adrian Fish <[log in to unmask]<mailto:[log in to unmask]>> wrote: Hi Jon, Have you tried dumping the returned XML to the page? The end result of a memberships request is a chunk of XML being returned to WebPA. If you can dump that in the webpa lti plugin code, it should become apparent if groups are being returned. I'll check the Sakai consumer code in the meantime. What version of Sakai are you testing on? Cheers, Adrian. On 12 May 2015 at 11:35, Jon Higham <[log in to unmask]<mailto:[log in to unmask]>> wrote: Hi all I’ve a few queries with the LTI integration with Sakai. I’ve had to make some changes to webpa so that it will sync sakai site members with the correct role. It now seems to work well and I can transfer grades from webpa to sakai. However, does the integration provide group membership? With my limited knowledge of php and LTI I can’t see that sakai is passing any group membership information. I’d be grateful of any pointers on where to check this. Also, is there a session timeout and how does the LTI session logout work? If I login to sakai, use the LTI tool to open a webpa tab, I can logout of sakai and the webpa tab is left logged in and never times out. Jon Higham Application Support and Development Analyst University of Hull Hull, HU6 7RX, UK http://www.hull.ac.uk/ 01482 465734 ************************************************** To view the terms under which this email is distributed, please go to http://www2.hull.ac.uk/legal/disclaimer.aspx **************************************************