Hi Pete, You're not at all off base. This is the #1 use case we see.
Matterhorn uses a traditional role based access control system to determine who can see what. In Matterhorn 1.2, you can define which roles (e.g. "Student in Physics 101, Fall 2011") may view the recordings associated with each specific series using the web-based admin UI. Matterhorn includes pluggable authentication and authorization, so you can allow students access via CAS, for example, and use Moodle to determine what roles that user has. The roles would presumably come from the list of Moodle courses for which the current user is a member. A "MoodleRoleProvider" would need to be written, in Java, and plugged in to Matterhorn (via an xml file), but it should not be too difficult. Josh On Sep 9, 2011, at 11:27 AM, Mentzer, Peter wrote: > (I might be off-base here because I'm a newbie to Matterhorn, so apologies if > this is not relevant to your question exactly:) > > What we would really like is integration with another system's > authentication. For example: > A capture device records lecture and matterhorn processes it so it's in > Engage. > Nobody can browse freely to it, though, unless they authenticate into Engage > (videos are not public) > A faculty member logs into a learning management system (we use Moodle) > Faculty adds a "matterhorn video" as an activity/resource in the learning > management system > Because of their role/identity in moodle, they are able to browse available > videos in Engage that match their role/identity > Once the video is placed in moodle, students who are enrolled in the course > can view it > I realize this model requires the development of a moodle plugin (or > Blackboard building block) etc, but it would be great, and involves > authentication so I figured I'd mention it. In other words, some sort of API > web service access to whatever authentication systems you build would be > great. > > -Pete > > > On Thu, Sep 8, 2011 at 8:51 PM, Hank Magnuski <[email protected]> wrote: > Thank you, that's exactly the right idea. +1 for adding it to the Admin > interface. > > Hank > > > On Thu, Sep 8, 2011 at 7:32 PM, Josh Holtzman <[email protected]> wrote: > I figured someone would want to use the default database-backed user > directory for more than just testing, so I added a (very preliminary) UI for > managing users and roles (see attached). It's mostly a proof of concept, and > needs design and development work. But the skeleton is in trunk already. > > Josh > > > > > _______________________________________________ > Matterhorn-users mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn-users > > > > > -- > Peter Mentzer MS Ed > Director of Online Technology > Dominican University of California > _______________________________________________ > Matterhorn-users mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
_______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
