You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "David Sean Taylor (JIRA)" <je...@portals.apache.org> on 2014/05/16 12:59:59 UTC

[jira] [Updated] (JS2-1233) security domains

     [ https://issues.apache.org/jira/browse/JS2-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Sean Taylor updated JS2-1233:
-----------------------------------

    Fix Version/s:     (was: 2.3.0)
                   2.3.1

> security domains
> ----------------
>
>                 Key: JS2-1233
>                 URL: https://issues.apache.org/jira/browse/JS2-1233
>             Project: Jetspeed 2
>          Issue Type: New Feature
>          Components: Security
>    Affects Versions: 2.2.3
>            Reporter: David Sean Taylor
>            Assignee: David Sean Taylor
>             Fix For: 2.3.1
>
>
> Implement multiple security/authentication spaces within a portal,  each with a different set of principals. Integrate with spaces to provide multi-hosted domains on a single portal deployment.
> High level view of work:
> * add domains system folder
> * administer users by domain (j2-admin)
> * domain valve to map request to domain (jetspeed-portal)
> * environments (j2-admin)
> * delegated security by domain (j2-admin)
> * security policy per domain (jetspeed-security, j2-admin)
> Additional requirements from Ron Wheeler:
> - portlet visibility by Domain. For each domain, the system admin should be able to specify which portlets are available for selection by the user. The definition of portlets can be at the system level and make a portlet available for addition to each domain's list of allowed portlets.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org