Page History

...

This is a proposal to make it possible to externalize user permissions so that Roller can pull user-weblog permissions from a separate user permissions system.

1.0 Abstract

For ease of installation and management, Roller is able to manage it's own users permissions without relying on any external system other than its RDBMS. We definitely don't want to lose that easiness, but we do want to make it possible to plug Roller into existing sites and applications that have their own permissions management systems.

This proposal outlines a plan to make it easy to hook Roller up to an external user permissions system. The general approach is to define a User Permissions API, provide a default implementation for Roller, and change UserManager to use that API. Developer could then provide alternative implementations of that API to plug in their own user permissions systems.

3.0 Requirements

• Enable Roller to optionally read/write user-weblog permission information in an external system

...

• instead of it's relational database.
• Define a User Permissions API and make it possible to plugin User Permissions API implementations without having to extend a UserManager implementation.

4.0 Issues

Issues raised and addressed during review process. TBD

5

...

.0 Background

...

and Design

To understand this proposal you need to understand how Roller's existing user management system works. So hereHere's an explanation of Roller's current user permissions managementsystem, the perceived problems and proposed solutions.

...

5.1 Roller manages user-weblog permissions

In addition to roles, which are global across a Roller site, Roller also manages each user's permissions to access weblogs. There is a many-to-many relationship between users and weblogs and it's stored in a database table:

...

public boolean hasWritePermissions(User user)

...

5.1.1 Problem

Permissions cannot be managed by external system because the User to Permissions to Weblog relationship is managed by the ORM, the information must be stored in Roller database tables and cannot be externalized and managed by another system.

...

5.1.2 Solution: User Permissions API

First, we remove the dependence on ORM for permissions. Insead calling ORM supported methods on the Weblog and User classes, the Roller front-end will call the Roller UserManager to access permissions information. We'll add these new methods to accommodate that:

New methods in UserManager

public Set<WeblogPermission> getWeblogPermissions(Weblog weblog)
public Set<WeblogPermission> getUserPermissions(User user)
public void grantPermissions(WeblogPermissionString permusername, StringWeblogPermission usernameperm)
public void removePermissionsremovePermission(String username, WeblogPermission perm)
public int getUserCount(Weblog weblog)
public int getAdminCount(Weblog weblog)

To Second, to allow us to plugin alternate user permissions systems Roller's default UserManager implementation will call a User Permissions API interface to store and retrieve permissions:. This could be done in a generic way by allowing user permissions to be granted on any object of any class.

For example, this API allows you to grant permissions on specific objects and uses a mask for permissions as we do now in Roller.

User Permissions API

UserPermissions interface methods

public void grantPermission(
   String username, String objClass, String objectId, int mask)

public Set<Permissions>void getObjectPermissionsremovePermissions(
   String objectClassusername, String objClass, String objectId, int mask) 
   
public Set<Permission> getUserPermissions()
public Set<Permissions>Set<Permission> getUserPermissions(String usernameobjClass)
public voidSet<Permission> grantPermissionsgetUserPermissions(PermissionsString permsobjClass, String usernameobjectId)
public voidSet<Permission> removePermissions(Permissions getObjectPermissions(String objClass, String objectId)

Permissions bean

int    mask
String objectClass
String obectId    

Roller will include a User Permissions API that stores data in the Roller database. Other implementations can be plugged in via DI.You can stop reading here... the rest is TBD

3.0 Requirements

Requirements satisfied by this proposal

4.0 Issues

Issues to be considered

5.0 Design

5.2 Specific changes to Managers, POJOS, Actions and JSPs

TBDList and describe new manager methods, Struts actions, JSP pages, macros, etc.

6.0 Comments

Other can leave commments herePlease comment on the dev mailing list.