LTI users are not persisted, preventing operations such as scheduling a recording from succeeding

Description

In the absence of a UserProvider, users who authenticate via LTI are not visible beyond the LTI session.

This prevents users from taking operations such as scheduling, as workflow operations subsequently fail when the user cannot be resolved.

Opencast should optionally persist LTI users into the mh_user_ref table.

Similar to:

https://bitbucket.org/opencast-community/matterhorn/pull-requests/1348/mh-12029-as-a-user-i-want-to-use-my/diff

Activity

Show:
Greg Logan
October 28, 2019, 8:25 PM
Stephen Marquard
October 24, 2019, 8:26 AM

AFAIK if you run Opencast using LTI but without a userprovider, workflows started by LTI users fail because the resolution of those usernames on worker nodes fails.

 

Greg Logan
October 22, 2019, 10:38 PM

is this one done? If so please resolve.

Stephen Marquard
January 28, 2014, 7:26 AM
Edited

An alternate approach to use is to use the "trusted user" mode of LTI implemented in and implement a UserProvider so that any Matterhorn node can always resolve users supplied by LTI (from an external source).

UCT's Sakai UserProvider is here, as an example:

https://bitbucket.org/opencast-community/matterhorn-cape-town-fork/src/7fe0f0171921d531ee6fd0bea16a9b75dd12aa53/modules/matterhorn-userdirectory-sakai/src/main/java/org/opencastproject/userdirectory/sakai/?at=1.6.x

Tobias Wunden
February 14, 2013, 3:32 PM

Hi Edmore,

we did related work at UNINETT in order to persist the users that log via Shibboleth. There as well, the user is not available once processing of the recordings start. The work is ready to be merged for 1.5.

Tobias

Done

Assignee

Stephen Marquard

Reporter

Stephen Marquard