-
Task
-
Resolution: Done
-
Critical
-
4.0.0.Alpha10
-
None
The current configuration model for mapping permissions does not appear to be manageable by a tool that is trying to add/remove permissions based on the presence/absence of a specific subsystem.
This is a critical issue for the provisioning mechanism which is not only producing the default configuration that could be simple enough but also allows the user to customize the default configuration and then preserve the user changes after applying a version update or a patch.
- is duplicated by
-
WFWIP-9 Elytron permission-set should throw exception for non-existent permission
- Closed
- relates to
-
JBEAP-9726 Incorrect permission class-name should throw exception at runtime
- Resolved
-
WFCORE-2565 Incorrect permission class-name should throw exception at runtime
- Resolved
-
WFCORE-3796 Incorrect Elytron permission class-name or module should throw exception
- Resolved
-
WFWIP-9 Elytron permission-set should throw exception for non-existent permission
- Closed