Matterhorn offers fairly flexible authentication (determining who is logged in) via spring security. See [1] for more details. For authorization (what can the current user *do*, now that they have authenticated), we support setting access control lists on series and using these ACLs to determine who can read what. When a mediapackage in processed, we look at which series the mediapackage is associated with, and we apply the access control defined by the series to the mediapackage.
In this first iteration of the 1.2 cycle, we support only one type of access control entry, read, and we only apply the access control entry based on roles, not on individual users. This area is under active development, so please feel free to check out the trunk and follow the progress. Changes to the administrative user interfaces should be coming next iteration. [1] http://static.springsource.org/spring-security/site/docs/3.0.x/reference/springsecurity.html Josh On Mon, Mar 28, 2011 at 2:58 PM, Otto J Wittner <[email protected]>wrote: > Dear all, > > What is the current status for authentication in Matterhorn? > > Any recommendations to how federated access should be implemented? > > What about differentiating between users and groups within Matterhorn? > Ref. > > http://opencast.jira.com/browse/MH-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25125#comment-25125 > > Regards > O2 > > -- > Otto J Wittner Tel 73557945 > UNINETT AS Mob 99550566 > _______________________________________________ > 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
