[JS2-872] PermissionSecurityHandler for LDAP

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Later
• Affects Version/s: 2.2.0
• Component/s: Security
• Assignee: Ate Douma
• Reporter: Ate Douma
• Created: 03/Jun/08 12:33
• Updated: 02/May/13 02:29
• Resolved: 07/Oct/08 23:31

Description

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.

Issue Links

• depends upon: JS2-869 New Preferences backend implementation for Registry, Entity and Security components
• depends upon: JS2-870 Replace User/Group/Role (Java) Preferences with simplified attributes Map