[
http://opencast.jira.com/browse/MH-6829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25687#comment-25687
]
Josh Holtzman commented on MH-6829:
-----------------------------------
There are at least three levels of control that we can (more or less) easily
add to the workflow service and, hence, the administrative UI.
1) Securing access to individual workflow instances. This requires that we
provide some kind of built in rule or UI choice (or both) to set access control
on workflow instances. Once the access control list has been set, we can limit
who can access particular workflow instances.
2) Securing access to individual workflow definitions. This can be handled by
including an access control list in the workflow definition itself so
authorization rules can be set on registration.
3) Securing access to individual workflow operations. By securing an
individual operation, we can allow users to run workflows with, for instance, a
publish step that requires another user to approve the publication. The
workflow instance ACL must either be a superset of all contained operation
ACLs, or the queries used to obtain workflow instances must take the current
operation and its ACL into account.
> Define the granularity of authorization
> ---------------------------------------
>
> Key: MH-6829
> URL: http://opencast.jira.com/browse/MH-6829
> Project: Matterhorn Project
> Issue Type: Sub-Task
> Components: Architecture & Services
> Affects Versions: 1.2
> Reporter: Josh Holtzman
> Assignee: Josh Holtzman
> Fix For: 1.2
>
>
> Is it sufficient to limit access based on series membership, or is there some
> other grouping or role association that determines access to recordings in
> the administrative UIs?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
