This action doPerforms an Access Control List and places it into
the RunData object, so it is easily available to modules. The ACL
is also placed into the session. Modules can null out the ACL to
force it to be rebuilt based on more information.
Turbine uses a User-Role-Permission arrangement for access control.
Users are assigned Roles. Roles are assigned Permissions. Turbine
modules then check the Permission required for an action or
information with the set of Permissions currently associated with
the session (which are dependent on the user associated with the
session.)
The criteria for assigning Roles/Permissions is application
dependent, in some cases an application may change a User's Roles
during the session. To achieve flexibility, the ACL takes an
Object parameter, which the application can use to doPerform the
ACL.
This action is special in that it should only be executed by the
Turbine servlet.
author: John D. McNally author: Brett McLaughlin author: Quinton McCombs version: $Id: AccessController.java 534527 2007-05-02 16:10:59Z tv $ |