If you've been following this list recently, you probably already know that
I've been working on multi tenancy and authorization features in preparation
for the Matterhorn 1.3 release.
One of these features, as described in the wiki page [1] detailing the 1.3
authz work scope, is defining which organization and which users within that
organization "own" a capture agent.
Limiting agents by organization was simple: I just modified the database tables
and JPA queries to take the current user's organization into account when
dealing with the capture admin service. In order to implement the role-based
authorization, I registered the CaptureAgentStateService as a
ManagedServiceFactory [2], which allows us to define which user roles are
allowed to schedule which capture agents via the system console [3].
Any agent that comes online that matches one of the server side agent
configurations will be available for scheduling only for users with one of the
specified roles. Agents with no server-side configuration are available to
anyone with access to the administrative tools. In this way, we can enforce
both coarse grained authorization (e.g. only instructors and administrators may
use the admin tools) and fine grained authorization (only administrators may
modify the schedule for capture agent X).
Please see r10746 for all of the details, and please feel free to open a review
or comment here.
[1]
http://opencast.jira.com/wiki/display/MH/Authorization+Work+For+Matterhorn+1.3+%28DRAFT%29
[2]
http://www.osgi.org/javadoc/r4v42/org/osgi/service/cm/ManagedServiceFactory.html
[3] http://opencast.jira.com/secure/attachment/12396/ca_config.png
Thanks,
Josh
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________