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 "Ate Douma (JIRA)" <je...@portals.apache.org> on 2008/10/08 01:28:44 UTC

[jira] Resolved: (JS2-870) Replace User/Group/Role (Java) Preferences with simplified attributes Map

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

Ate Douma resolved JS2-870.
---------------------------

    Resolution: Fixed

The brand new portal trunk (copied over from the security-refactoring branch) now provides a new pure database based (NO more Java Preferences!) solution,
together with an optional (auto) synchronizing and replicating external store (LDAP only for now). 

> Replace User/Group/Role (Java) Preferences with simplified attributes Map
> -------------------------------------------------------------------------
>
>                 Key: JS2-870
>                 URL: https://issues.apache.org/jira/browse/JS2-870
>             Project: Jetspeed 2
>          Issue Type: New Feature
>          Components: Admin Portlets, Persistence and DAO, Security
>    Affects Versions: 2.2
>            Reporter: Ate Douma
>            Assignee: Ate Douma
>            Priority: Critical
>             Fix For: 2.2
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> The current User/Group/Role Preferences are tied to the Java Preferences API.
> JS2-869 will provde a new, simplified and more efficient preferences model doing away with the Java Preferences.
> For the User/Group/Role security principal elements this will require a drastic API change but also allow for better and improved integration with the backend systems.
> The Portlet API USER_INFO attributes need to be mapped (filtered per portlet application) to the User attributes.
> Furthermore, full backend integration needs to be provided so for instance LDAP can be used for storage/retrieval as well. This will require large enhancements to the LDAP api (which currently doesn't support mapping custom attributes yet). 
> Finally, the admin portlets need to be enhanced to provide retrieval and (optionally, if the backend supports/allows is) modification of attributes per User/Role/Group.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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