[
https://issues.apache.org/jira/browse/FC-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney resolved FC-239.
-------------------------------
Resolution: Fixed
Added:
AccessMgr
Session createSession( User user, List<RoleConstraint> constraints, boolean
isTrusted )
throws SecurityException;
Updated:
AdminMgr
RoleConstraint addRoleConstraint( UserRole uRole, RoleConstraint roleConstraint
)
throws SecurityException;
void removeRoleConstraint( UserRole uRole, RoleConstraint roleConstraint )
throws SecurityException;
ReviewMgr
List<User> assignedUsers( Role role, RoleConstraint roleConstraint )
throws SecurityException;
> Some additional methods to manage role constraints.
> ---------------------------------------------------
>
> Key: FC-239
> URL: https://issues.apache.org/jira/browse/FC-239
> Project: FORTRESS
> Issue Type: Improvement
> Affects Versions: 2.0.1
> Reporter: Shawn McKinney
> Assignee: Shawn McKinney
> Priority: Major
> Fix For: 2.0.2
>
>
> Now that Fortress supports attributes within the activation phase,
> convenience methods are needed to reduce complexity managing the attributes.
>
> Reuse these:
> AdminMgr
> 1. addRoleConstraint ( UserRole , RoleConstraint )
> 2. removeRoleConstraint ( UserRole , RoleConstraint )
>
> Add these:
> ReviewMgr
> 3. List<UserRole> getRoleConstraints( UserRole, RoleConstraint )
> AccessMgr
> 4. applyConstraint ( Session, RoleConstraint )
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
