[ https://issues.apache.org/jira/browse/FC-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shawn McKinney updated FC-328: ------------------------------ Description: 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). was:Does not properly validate whether a role constraint has been enabled globally. Does not verify that user has only one constraint setup per global > 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-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org