directory-fortress mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shawn McKinney <>
Subject Re: [Bulk] RBAC Constraints
Date Mon, 24 Aug 2015 15:14:46 GMT

Yes it can be done but it requires a little work on your end.  There are three steps to the

1. Implement the interface.  The existing
temporal evaluators all reside inside the same package. You may use one of those as an example.

2. Register the new component with fortress.  That is done by dropping a new property in the file.  For example here are the temporal validator settings:

# these properties will enable temporal constraint checks on role activations:

3. Your new validator impl class will need to be made available to the fortress runtime classpath.


Your use case requires a new validator, e.g.:

That would be called during the lifecycle of any AccessMgr method - during role the constraint

Depending on your requirements, you may need to store new data attributes in ldap to support
the new validator.  The easiest way to do this would to make it a property.  If it needs to
be part of the fortress constraint data storage, i.e. need to store within ftRC attribute,
it would require work done to the core API to support.


> On Aug 24, 2015, at 9:42 AM, Chris Pike <> wrote:
> The Fortress Commander UI and Java API provide mechanisms to set and retrieve temporal
constraints on a role. Is there any way to add additional arbitrary constraints that are not
time related? For example, a bank teller can only work with a certain set of accounts.
> Thanks,
> ~Chris Pike

View raw message