You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@directory.apache.org by "Shawn McKinney (Jira)" <ji...@apache.org> on 2023/11/29 17:22:00 UTC

[jira] [Resolved] (FC-328) Role Constraint validations broken

     [ https://issues.apache.org/jira/browse/FC-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shawn McKinney resolved FC-328.
-------------------------------
    Resolution: Fixed

added check to AdminMgr.addRoleConstraint

> Role Constraint validations broken
> ----------------------------------
>
>                 Key: FC-328
>                 URL: https://issues.apache.org/jira/browse/FC-328
>             Project: FORTRESS
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: Shawn McKinney
>            Priority: Major
>             Fix For: 3.0.1
>
>
> Does not properly validate whether a role constraint has been enabled globally. 
> For example, for a constraint placed on Role 'Foo', enableRoleConstraint must be called which adds a property to fortress:
> RC$HOME$foo:local
> This enables checking 'locale' (some dynamic constraint) anytime the role 'foo' is activated into a user's session.  When trying to add this corresponding role contraint to a user's assignment, this check will ensure that the contraint has been defined globally first (via enableRoleConstraint api).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org