-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
7.1.0.DR14
In case when some permission mapper (tried with constant-permission-mapper and simple-permission-mapper) includes permission with non-existent class-name then it seems that no exception is thrown during runtime.
- is cloned by
-
WFCORE-2565 Incorrect permission class-name should throw exception at runtime
- Resolved
- is incorporated by
-
JBEAP-12932 Upgrade WildFly Core to 4.0.1.Final
- Closed
- is related to
-
WFCORE-3796 Incorrect Elytron permission class-name or module should throw exception
- Resolved
-
WFCORE-3596 further improve the permissions mapping configuration model to be manageable to by a tool
- Resolved