[
https://issues.apache.org/jira/browse/CAUSEWAY-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17802729#comment-17802729
]
Daniel Keir Haywood commented on CAUSEWAY-3081:
-----------------------------------------------
have added a new config property to support this, but checking is disabled by
default.
causeway.extensions.secman.fixture-scripts.abstract-role-and-permissions-fixture-script.unknown-feature-id-checking-policy
> Check for existence of feature in fixturescript
> -----------------------------------------------
>
> Key: CAUSEWAY-3081
> URL: https://issues.apache.org/jira/browse/CAUSEWAY-3081
> Project: Causeway
> Issue Type: Improvement
> Components: Ext Sec Secman
> Affects Versions: 2.0.0-M8
> Reporter: Patrick Deenen
> Assignee: Daniel Keir Haywood
> Priority: Major
> Fix For: 2.0.0-RC5
>
>
> When one defines a fixture based on AbstractRoleAndPermissionsFixtureScript
> using newPermissions NO check is done if the new permission is actually
> referring to an actual valid feature. Hence it is possible to define
> permissions that have no effect or have no effect. So it would be better to
> at least check is the member exist.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
