[jira] Resolved: (JS2-872) PermissionSecurityHandler for LDAP

["Ate Douma (JIRA)" <je...@portals.apache.org>]

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

Ate Douma resolved JS2-872.
---------------------------

       Resolution: Later
    Fix Version/s:     (was: 2.2)

The brand new portal trunk (copied over from the security-refactoring branch) now provides a new pure database based solution,
together with an optional (auto) synchronizing and replicating external store (LDAP only for now).
For the PermissionManager, there is no LDAP synchronization and replication build yet, but the all the interfaces enabling doing so are already in place.
As there is no pressing requirement right now, I'm resolving this issue (for now) to be fixed "Later"

> PermissionSecurityHandler for LDAP
> ----------------------------------
>
>                 Key: JS2-872
>                 URL: https://issues.apache.org/jira/browse/JS2-872
>             Project: Jetspeed 2
>          Issue Type: New Feature
>          Components: Security
>    Affects Versions: 2.2
>            Reporter: Ate Douma
>            Assignee: Ate Douma
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> Right now, Jetspeed only has a database based PermissionManagerImpl.
> In contrast to the other security components for User,Role,Group there is no corresponding PermissionSecurityHandler for abstracting the backend implementation.
> Adding a PermissionSecurityHandler and corresponding DefaultPermissionSecurityHandler (for the database) and a LdapPermissionSecurityHandler
> also requires extending the SecurityMappingHandler interface and delegating the current db access in PermissionManagerImpl to the PermissionSecurityHandler.
> Related to this is the RdbmsPolicy class (name) which really hooks the PermissionManager into the Java security system.
> Although this class is call RdbmsPolicy, actually it has no ties to the database at all, only to the PermissionManager.
> By providing an LDAP backend for the permissions, we can still use the RdbmsPolicy, nevermind its name  :) 
> But maybe we should rename it to JetspeedPolicy in the future for clarity. 

-- 
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