RulePoint includes twenty system-defined privileges, which form the basis of authorization.
You can create roles in RulePoint that can contain one or more privileges. You can then assign the roles to users, irrespective of the type of authentication provider that is responsible for the user authentication. After a user successfully logs in to RulePoint, spring creates a security context for the user. The security context contains an authentication object that corresponds to the user, and includes a list of privileges assigned to the user through the associated role.
You can map LDAP groups to a role created within RulePoint. All users who belong to the LDAP group will have this role. Privileges determine the actions you can perform for a RulePoint object. For example, a user can have create or view privileges. Permissions determine user access to actions for a particular instance of an object.
RulePoint has an ACL system that is implemented by the spring ACL system, where you can include both users and roles in the object ACLs. You can perform all the required authorization-related actions in RulePoint. The authorization module is ApplicationProvider agnostic and does not require extension or customization.